LDAP-UX Client Services B.05.00 Administrator's Guide
<indexed>
Optional, use if an attribute type requires indexing. At most one
indexed flag can be specified.
<dsSpecific>
Optional, use to specify any directory-specific information about
the attribute type. See Section 7.5.5 (page 311) for details.
7.5.4.3 Attribute type definition requirements
To add the new schema to the LDAP directory server, each attribute type definition must meet
the following requirements:
• The attribute type has a <oid> tag with one numeric id value which adheres to RFC 2252
format specification.
• The attribute type has at least one <name> tag with the attribute type name. Each name
must adhere to RFC 2252 format specification.
• No other attribute types in the schema definition file or on the LDAP directory server have
the same OID value.
• No other attribute types in the schema definition file or on the LDAP directory server have
the same name values.
• The specified super-type used by the attribute type must already exit on the LDAP directory
server or its definition must be specified in the same schema definition file.
• The attribute type specifies either an LDAP syntax value or a super-type. Some directory
servers, for example ADS, do not support attribute type inheritance. For such directory
servers, the LDAP syntax for the sub-type attribute is obtained from the super-type definition
and the super-type/sub-type relationship is ignored
• The matching rules and syntaxes used by this attribute type are supported by the LDAP
directory server. See the “Mapping Unsupported Matching Rules and LDAP Syntaxes”
section for details.
• The inheritance hierarchy has no cycles (no circular dependencies exist in the
super-class/sub-class relationships).
• If the attribute type has a super-type, they both have the same value defined in the <usage>
tag.
308 Command and tool reference