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

Line 23: <name>printer-aliases</name>
Line 24: <desc>Names in addition to the printer-name</desc>
Line 25: <equality>caseIgnoreMatch</equality>
Line 26: <substr>caseIgnoreSubstringsMatch</substr>
Line 27: <syntax>1.3.6.1.4.1.1466.115.121.1.15</syntax>
Line 28: <length>127<length>
Line 29: </attributeTypeDefinition>
Line 30:
inee 31: <objectClassDefinition>
LINe 32: <oid>1.3.18.0.2.6.253</oid>
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>
NOTE: Line 1–2 are required in every schema definition file. Attribute type and object class
definitions closely follow the format specified in RFC 2252. Values specified for all XML tags except
the <dsSpecific> tag must not be quoted. Only the description field (enclosed by
<desc>...</desc> tags) can contain spaces.
9.5.4.2 Defining attribute types
Each attribute type definition, enclosed by <attributeTypeDefinition> 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 attribute type 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 may be specified. This tag
specifies a display name of the attribute type 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 description may be specified. Do not use
quotes around the description 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 may be specified.
<subTypeOf> Optional, use if an attribute type has a super-type. At most one
super-type may 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 may be specified.
<ordering> Optional. At most one ordering rule may be specified.
<substr> Optional. At most one substring matching rule may be specified.
<syntax> Required if an attribute type has no super-type. At most one LDAP
syntax value may be specified.
<length> Optional indication of 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, "1.3.6.4.1.1466.0{64}”
can be expressed using the following tags:
366 Command and tool reference