Maykel Moya <[EMAIL PROTECTED]> writes: > I've seen some cases where an entry has only top and inetOrgPerson > object classes, in other cases similar entries have also person and > organizationalPerson. > > In particular, GQ, the client I used to use, forces that all clases from > top to current should be added. > > Another doubt is respect to AUXILIARY classes inheritance from top, I've > seen both AUX classes inheriting and not inheriting from top. > > Do the standard mandate something related to these issues? If not so, > what could be pros and cons of every option?
The standard requires the definition of a structural object class. As, like inetorgperson, some structural object classes are part of a object class chain some directories require all members of this object class chain. OpenLDAP only requires the last object class of a chain, so for OpenLDAP ist would be sufficiant to declare only inetorgperson not even top but it does no harm to declare the full chain. -Dieter -- Dieter Klünter | Systemberatung http://www.dkluenter.de GPG Key ID:8EF7B6C6 --- You are currently subscribed to [EMAIL PROTECTED] as: [EMAIL PROTECTED] To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the SUBJECT of the message.
