LDAP-UX Client Services B.05.01 Administrator Guide for HP directory servers and Windows ADS

<syntax>1.3.6.4.1.1466.0</syntax>
<length>64</length>
At most one syntax length value may be specified. <length>
must contain a positive integer value.
<singleValued> Optional, use if the SINGLE-VALUE flag is set. At most one
singleValued flag may be specified.
<collective> Optional, use if the COLLECTIVE-VALUE flag is set. At most one
collective flag may be specified.
<noUserModification> Optional, use if NO-USER-MODIFICATION flag is set. At most
one noUserModification flag may be specified.
<usage> Optional, must contain one of the following possible values:
• userApplications
• directoryOperation
• distributedOperation
• dSAOperation
At most one usage value may be specified..
<indexed> Optional, use if an attribute type requires indexing. At most one
indexed flag may be specified.
<dsSpecific> Optional, use to specify any directory-specific information about
the attribute type. For more information, see Section 9.5.5
(page 369).
9.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. For more information, see Section 9.5.7 (page 373).
• 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.
9.5 Schema extension utility 367