Subject: LDAPsubentry

From: "Kurt D. Zeilenga" <[email-masked]>
Date: Thu, 18 Nov 1999 09:36:39 -0800

I would like to see LDAP subentry be an abstract object class
to which is then subclassed as necessary to provide structure
(including naming attributes).

As defined, LDAP subentry requires cn.  This may not be appropriate
for LDAP subentries.   I suggest:

( ldapSubEntryOID NAME 'ldapSubEntry'
   DESC 'LDAP Subentry abstract class, version 1'
     SUP top ABSTRACT )

( cnSubEntryOID NAME 'cnSubEntry'
   DESC 'CN LDAP Subentry class, version 1'
     SUP ldapSubEntry STRUCTURAL
     MUST ( cn ) )

Your schema definition would then be split as appropriate between
the abstract class and the structural class.

Regards, Kurt