Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section
Column
width50%

RFC 4512

Code Block
objectclass ( 2.5.6.0 
    NAME 'top' 
    DESC 'top of the superclass chain' 
    ABSTRACT 
    MUST objectClass 
)
Column
width50%

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 :

Code Block
dn: Namename=top,cn=schemametaSchema
objectclass=: metaObjectClass
name: top
desc: top of the superclass chain
type: ABSTRACT
must: objectClass

...

Section
Column
width50%

RFC 4512

Code Block
objectclass ( 2.5.6.1 
    NAME 'alias' 
    DESC 'RFC2256: an alias' 
    SUP top 
    STRUCTURAL 
    MUST aliasedObjectName 
)
Column
width50%

Using MetaSchema

Code Block
dn: Namename=alias,cn=schema
objectclass=: top
name: alias
desc: RFC2256: an alias
sup: top
type: STRUCTURAL
must: aliasedObjectName

...

Section
Column
width50%

RFC 4512

Code Block
objectclass ( 2.5.6.2 
    NAME 'country' 
    DESC 'RFC2256: a country' 
    SUP top 
    STRUCTURAL 
    MUST c 
    MAY ( searchGuide $ description ) 
 )
Column
width50%

Using MetaSchema

Code Block
dn: name=country,dc=core,cn=schema
objectclass=: top
name: country
desc: RFC2256: a country
sup: top
type: STRUCTURAL
must: c
may: searchGuide
may: description

...

ObjectClass locality

Section
Column
width50%

RFC 4512

Code Block

objectclass ( 2.5.6.3 
    NAME 'locality' 
    DESC 'RFC2256: a locality' 
    SUP top 
    STRUCTURAL 
    MAY ( street $ seeAlso $ searchGuide $ st $ l $ description ) 
)
Column
width50%

Using MetaSchema

Code Block

dn: name=locality,dc=core,cn=schema
objectclass: top
name: locality
desc: RFC2256: a locality
sup: top
type: STRUCTURAL
may: street
may: seeAlso
may: searchGuide
may: st
may: l
may: description

...