Work in progress
This site is in the process of being reviewed and updated.
h2. system
ObjectClass top
RFC 4512
objectclass ( 2.5.6.0 NAME 'top' DESC 'top of the superclass chain' ABSTRACT MUST objectClass )
Using MetaSchema
top is a very special ObjectClass, as it is the only one which can't be described with the MetaSchema, because top can't depend on itself because it can't exist before being created ! top will be hard wired in the server. Here is the LDIF file which could be used if we were to include it into the server :
dn: name=top,cn=metaSchema objectclass: metaObjectClass name: top desc: top of the superclass chain type: ABSTRACT must: objectClass
ObjectClass alias
RFC 4512
objectclass ( 2.5.6.1 NAME 'alias' DESC 'RFC2256: an alias' SUP top STRUCTURAL MUST aliasedObjectName )
Using MetaSchema
dn: name=alias,cn=schema objectclass: top name: alias desc: RFC2256: an alias sup: top type: STRUCTURAL must: aliasedObjectName