dE wrote:
On 04/26/15 17:13, Michael Ströder wrote:dE wrote:Super this is the superclass chain -- A->B A is defined by MUST ObjectClass MAY ( cn abc xyz cxy ) B is defined by MUST ObjectClass MAY ( cn cxy ) Then an entry belonging to B (explicit) and A (implicit, automatically added) cannot have attributes abc and xyz.No! B would have MAY ( cn abc xyz cxy ). Example for A: objectclass ( <some-oid-for-A> NAME 'A' MAY ( cn $ abc $ xyz $ cxy ) ) These three variants have the same MAY attribute set ( cn $ abc $ xyz $ cxy ): objectclass ( <some-oid-for-B> NAME 'B' SUP A MAY ( cn $ cxy ) ) objectclass ( <some-oid-for-B> NAME 'B' SUP A MAY ( cn $ abc $ xyz $ cxy ) ) objectclass ( <some-oid-for-B> NAME 'B' SUP A )Ok. So the significance of subordinate classes is to add a MUST attributes only.
No! Which text in RFC 4512 says that?Also I don't understand what the term "significance of subordinate classes" means to you in this context.
The possible attributes that any object can have is defined in the TOP object class;
No!
regardless of what object class the entry belongs to, any attribute listed in the TOP object class can be added to it.
You should really read RFC 4512 more carefully and look at existing subschema. I give up now to explain.
Ciao, Michael.
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature