LDAP-UX Client Services B.04.15 with Microsoft Windows Active Directory Server Administrator's Guide (edition 8)

Defining Object Classes
Each object class definition, enclosed by the <objectClassDefinition> tags, can contain the
following case-sensitive tags, in the order specified:
<oid>
Required. Exactly one numeric id must be specified. The <oid>
value must adhere to RFC 2252 format specification.
<name>
Required. At least one object class name must be specified.
Do not use quotes around the name values. The <name> value
must adhere to RFC 2252 format specification.
<displayName>
Optional. At most one display name can be specified. This
tag specifies a display name of the object class used by LDAP
clients and administrative tools. Currently, <displayName>
applies only to Active Directory Server (ADS) to specify
lDAPDisplayName and adminDisplayName if different from
the <name> value.
<desc>
Optional. At most one object class description can be specified.
Do not use quotes around the description.
<obsolete>
Optional, use only if applicable. Obsolete object class cannot
be used in definitions of any other object classes. At most one
obsolete flag can be specified.
<subClassOf>
Optional, use if an object class has super-classes. The specified
super class must already exist on the LDAP directory server,
or its definition must be specified in the same schema
definition file. If the LDAP directory server allows only one
super-class, then only the first <subClassOf> value will be
used.
<type>
Optional, must contain one of the following possible values:
STRUCTURAL, AUXILIARY, ABSTRACT. At most one type
value can be specified. If the LDAP directory server allows
only one super-class, then only the first <subClassOf> value
will be used.
<must>
Optional, use if an object class has mandatory attributes. The
specified attributes must already exist on the LDAP directory,
or its definition must be specified in the same schema
definition file.
<may>
Optional, use if an object class has optional attributes. The
specified attributes must already exist on the LDAP directory
server, or its definition must be specified in the same schema
definition file.
<rdn>
Optional, defines the recommended attribute to use for the
relative distinguished name for new entries created with this
object class. Currently, <rdn> applies only to Active Directory
Server (ADS). At most one RDN can be specified.
<extendAuxiliaryClass> Optional, applies only to AUXILIARY object classes. This tag
is used to extend an object class already defined in the LDAP
server schema with this new AUXILIARY object class.
Currently, <extendAuxiliaryClass> applies only to
Active Directory Server (ADS) to include the new AUXILIARY
class as an “auxiliaryClass” in the definition of another object
class already defined in the LDAP server schema.
<dsSpecific>
Optional, use to specify any directory-specific information
about the object type. See “Defining Directory Specific
Information” (page 242) section for details.
240 Command, Tool, Schema Extension Utility, and Migration Script Reference