Schema Extensions

[Tony Thompson]

I am creating a new object class in the LDAP schema. I would like for
my object class to be a container. I assume that one way to accomplish
this is to specify organizationalUnit as the super class. Doing it this
way, I would inherit all of the ou optional attributes, which I don't
need (not sure this is really a big deal).

Is there any other way to define a new object class as a container?
Along those same lines, when you create a new object class, can you
specify its containment rules (i.e. that it can be contained in an
organization but not an organizationalUnit)?

Thanks.

[Mark Wilcox]

In the current LDAP specification, ANY entry can be a 'container', simply by
adding the RDN of the new entry to the DN of the parent.

for example lets say you want to store preferences for an application under
a user's entry. all you have to do is
cn=Email App,uid=mewilcox,ou=people,dc=unt,dc=edu

The directory server doesn't maintain any type of heirarchical relationship
of the data, that's only for human use :).

Mark