|
On 04/18/15 03:24, Michael Ströder
wrote:
dE
wrote:
On 04/15/15 19:31, Howard Chu wrote:
dE wrote:
According to RFC 4512
An entry can belong to any subset of the set of auxiliary
object
classes allowed by the DIT content rule associated with
the
structural object class of the entry.
From what I understand, this means auxiliary classes do not
'augment';
the no. of attributes which are possible in an entry must be
a subset of
the structural object class the entry belongs to.
You have completely ignored "DIT content rule" in the quoted
sentence.
But it says "DIT content rule associated with the
structural object class of the entry"
A DIT content rule is always associated with exactly one
structural object class (by having the same OID). This does not
say anything about the use of auxiliary object classes within the
same entry.
Could you please come up with a concrete example to better explain
your question.
Ciao, Michael.
Ok, I'll assume that as the right thing. So an Auxiliary object
class which an entry belongs to (apart from a structural one) can be
a subset of any other structural object class. Thanks for
clarifying.
What I understand from the RFC text is that for e.g. there's a
structural object class B and an auxiliary object class A for an
object O; then O can only belong to A only if A is a subset of B,
that's why we have
"allowed by the DIT content rule associated with the
structural object class of the entry"
|