HP-UX Reference (11i v2 07/12) - 1 User Commands A-M (vol 1)

l
ldapschema(1) ldapschema(1)
Line 33: <name>printerLPR</name>
Line 34: <desc>LPR information</desc>
Line 35: <type>AUXILIARY</type>
Line 36: <must>printer-name</must>
Line 37: <may>printer-aliases</may>
Line 38: </objectClassDefinition>
Line 39:
Line 40: </schemaDefinition>
Lines 1-2 are required in every schema definition file. Attribute type and object class definitions closely fol-
low the format specified in RFC 2252. Values specified for all XML tags, except the
<dsSpecific>
fields
must not be quoted. Only the description field (enclosed by
<desc>...</desc> tags) can contain spaces.
Defining Attribute Types
Each
<attributeTypeDefinition>
can contain the following case-sensitive tags, in the order
specified:
<oid> Required. Exactly one numeric id must be specified.
<oid> value must adhere to RFC
2252 format specification.
<name> Required. At least one attribute type name must be specified. Do not use quotes around
the name values.
<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 attribute type used by LDAP clients and administrative tools. Currently,
<display-
Name>
applies only to Active Directory Server (ADS) to specify lDAPDisplayName and
adminDisplayName if different from the
<name> value.
<desc> Optional. At most one description can be specified. Do not use quotes around the descrip-
tion value.
<obsolete> Optional, use only if applicable. Obsolete attribute types cannot be used in definitions of
any other attribute types or object classes. At most one obsolete flag can be specified.
<subTypeOf>
Optional, use if an attribute type has a super-type. At most one super-type can be
specified. The specified super-type must already exist on the LDAP directory server, or its
definition must be specified in the same schema definition file.
<equality> Optional. At most one equality rule can be specified.
<ordering> Optional. At most one ordering rule can be specified.
<substr> Optional. At most one substrings rule can be specified.
<syntax> Required if an attribute type has no super-type. At most one LDAP syntax can be specified.
<length> Optional. Indicates the maximum length of a value of this attribute. RFC 2252 specifies
this value in curly braces following the attribute type’s syntax. For instance,
SYNTAX
1.3.6.4.1.1466.0{64}
can be expressed using the following tags:
<syntax>1.3.6.4.1.1466.0</syntax>
<length>64</length>
At most one attribute length can be specified.
<length> must contain a positive integer
value.
<singleValued>
Optional, use if the SINGLE-VALUE flag is set. At most one singleValued flag can be
specified.
<collective>
Optional, use if the COLLECTIVE-VALUE flag is set. At most one collective flag can be
specified.
<noUserModification>
Optional, use if the NO-USER-MODIFICATION flag is set. At most one noUserMo-
dification
flag can be specified.
HP-UX 11i Version 2: December 2007 Update − 5 − Hewlett-Packard Company 549