Re: All entries belong to the top object class?

[dE <de.techno@gmail.com>]

On 04/26/15 15:27, Michael Ströder wrote:
> dE wrote:
> > On 04/20/15 22:56, Michael Ströder wrote:
> > > dE wrote:
> > > > Does adding of the top object class (or
> > > > person) add all attributes to the entry?
> > >
> > > Nope. Which text in RFC 4512 leads to your presumption?
> >
> > Sorry for the late response. I was out of town.
> >
> >  From the responses, it appears the question has not been understood
> > correctly,
>
> Yes, very likely. But maybe you also did not understand the responses?
>
> > Does adding of the top object class (implicitly) make it possible to 
> > add all
> > attributes in the DIT to the entry?
>
> No.
>
> Please read RFC 4512 more closely.
>
> You could also read some source code, e.g. method 
> SubSchema.attribute_types() herein:
>
> http://python-ldap.cvs.sourceforge.net/viewvc/python-ldap/python-ldap/Lib/ldap/schema/subentry.py?revision=1.34&view=markup 
>
>
> Ciao, Michael.

Ok, then that makes it clear. Thank you for clearing that.

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.