HP-UX Directory Server 8.1 schema reference

As in Example 1-1 “Object class schema entry for person”, the person object class requires the
cn, sn, and objectClass attributes and allows the description, seeAlso,
telephoneNumber, and userPassword attributes.
NOTE:
All entries require the objectClass attribute, which lists the object classes assigned to the
entry.
1.1.1.2 Object class inheritance
An entry can have more than one object class. For example, the entry for a person is defined by
the person object class, but the same person may also be described by attributes in the
inetOrgPerson and organizationalPerson object classes.
Additionally, object classes can be hierarchical. An object class can inherit attributes from another
class, in addition to its own required and allowed attributes. The second object class is the superior
object class of the first.
The server's object class structure determines the list of required and allowed attributes for a
particular entry. For example, a user's entry has to have the inetOrgPerson object class. In
that case, the entry must also include the superior object class for inetOrgPerson,
organizationalPerson, and the superior object class for organizationalPerson, which
is person:
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgperson
When the inetOrgPerson object class is assigned to an entry, the entry automatically inherits
the required and allowed attributes from the superior object classes.
1.1.2 Attributes
Directory entries are composed of attributes and their values. These pairs are called attribute-value
assertions or AVAs. Any piece of information in the directory is associated with a descriptive
attribute. For instance, the cn attribute is used to store a person's full name, such as cn: John
Smith.
Additional attributes can supply additional information about John Smith:
givenName: John
surname: Smith
mail: [e-mail]
In a schema file, an attribute is identified by the attributetypes line, then followed by its
OID, name, a description, syntax (allowed format for its value), optionally whether the attribute
is single-valued or multivalued, and where the attribute is defined.
This is shown in Example 1-2 “Attribute schema entry for description”.
Example 1-2 Attribute schema entry for description
attributeTypes: ( 2.5.4.13 NAME 'description' DESC 'Standard LDAP \
attribute type' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 X-ORIGIN 'RFC 2256' )
Some attributes can be abbreviated. These abbreviations are listed as part of the attribute definition:
attributeTypes: ( 2.5.4.3 NAME ( 'cn' 'commonName' ) ...
10 About Directory Server schema