Novell LINUX ENTERPRISE DESKTOP 10 SP2 - DEPLOYMENT GUIDE 08-05-2008 Deployment Manual page 692

Example 35.1 Excerpt from schema.core
#1 attributetype (2.5.4.11 NAME ( 'ou' 'organizationalUnitName')
#2
#3
...
#4 objectclass ( 2.5.6.5 NAME 'organizationalUnit'
#5
#6
#7
#8 MAY (userPassword $ searchGuide $ seeAlso $ businessCategory
$ x121Address $ registeredAddress $ destinationIndicator
$ preferredDeliveryMethod $ telexNumber
$ teletexTerminalIdentifier $ telephoneNumber
$ internationaliSDNNumber $ facsimileTelephoneNumber
$ street $ postOfficeBox $ postalCode $ postalAddress
$ physicalDeliveryOfficeName
$ st $ l $ description) )
...
The attribute type organizationalUnitName and the corresponding object class
organizationalUnit serve as an example here. Line 1 features the name of the
attribute, its unique OID (object identifier) (numerical), and the abbreviation of the at-
tribute.
Line 2 gives a brief description of the attribute with DESC. The corresponding RFC on
which the definition is based is also mentioned here. SUP in line 3 indicates a superor-
dinate attribute type to which this attribute belongs.
The definition of the object class organizationalUnit begins in line 4, like in
the definition of the attribute, with an OID and the name of the object class. Line 5
features a brief description of the object class. Line 6, with its entry SUP top, indicates
that this object class is not subordinate to another object class. Line 7, starting with
MUST, lists all attribute types that must be used in conjunction with an object of the
type organizationalUnit. Line 8, starting with MAY, lists all attribute types that
are permitted in conjunction with this object class.
A very good introduction to the use of schemes can be found in the documentation of
OpenLDAP. When installed, find it in /usr/share/doc/packages/openldap2/
admin-guide/index.html.
676 Deployment Guide
DESC 'RFC2256: organizational unit this object belongs to'
SUP name )
DESC 'RFC2256: an organizational unit'
SUP top STRUCTURAL
MUST ou