+# $OpenLDAP$
# These come from RFC1274 and are in ASN.1 syntax. They have been
# translated with some imagination. Only attributes and classes we
# seems that Netscape does not know either. Searches on Altavista
# have not shed any light, so we will have to ask for help.
-# This file uses definitions from slapd.std.schema
+# This file uses definitions from core.schema
# ccitt.data.pss.ucl.pilot ( 0.9.2342.19200300.100 )
# 1 pilotAttributeType
# Believe it or not, this is case-insensitive
-attribute ( 0.9.2342.19200300.100.1.1 NAME ( 'uid' 'userid' )
+attributetype ( 0.9.2342.19200300.100.1.2 NAME 'textEncodedORAddress'
EQUALITY caseIgnoreMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attribute ( 0.9.2342.19200300.100.1.2 NAME 'textEncodedORAddress'
- EQUALITY caseIgnoreMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
-
-attribute ( 0.9.2342.19200300.100.1.3 NAME ( 'mail' 'rfc822Mailbox' )
+attributetype ( 0.9.2342.19200300.100.1.3 NAME ( 'mail' 'rfc822Mailbox' )
EQUALITY caseIgnoreIA5Match
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{256} )
-attribute ( 0.9.2342.19200300.100.1.4 NAME 'info' EQUALITY caseIgnoreMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+attributetype ( 0.9.2342.19200300.100.1.4 NAME 'info' EQUALITY caseIgnoreMatch
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attribute ( 0.9.2342.19200300.100.1.5 NAME ( 'drink' 'favouriteDrink' )
+attributetype ( 0.9.2342.19200300.100.1.5 NAME ( 'drink' 'favouriteDrink' )
EQUALITY caseIgnoreMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attribute ( 0.9.2342.19200300.100.1.6 NAME 'roomNumber'
+attributetype ( 0.9.2342.19200300.100.1.6 NAME 'roomNumber'
EQUALITY caseIgnoreMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attribute ( 0.9.2342.19200300.100.1.7 NAME 'photo'
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.5' )
+attributetype ( 0.9.2342.19200300.100.1.7 NAME 'photo'
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.5 )
-attribute ( 0.9.2342.19200300.100.1.8 NAME 'userClass'
+attributetype ( 0.9.2342.19200300.100.1.8 NAME 'userClass'
EQUALITY caseIgnoreMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attribute ( 0.9.2342.19200300.100.1.9 NAME 'host'
+attributetype ( 0.9.2342.19200300.100.1.9 NAME 'host'
EQUALITY caseIgnoreMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attribute ( 0.9.2342.19200300.100.1.10 NAME 'manager'
+attributetype ( 0.9.2342.19200300.100.1.10 NAME 'manager'
EQUALITY distinguishedNameMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.12' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
-attribute ( 0.9.2342.19200300.100.1.11 NAME 'documentIdentifier'
+attributetype ( 0.9.2342.19200300.100.1.11 NAME 'documentIdentifier'
EQUALITY caseIgnoreMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attribute ( 0.9.2342.19200300.100.1.12 NAME 'documentTitle'
+attributetype ( 0.9.2342.19200300.100.1.12 NAME 'documentTitle'
EQUALITY caseIgnoreMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attributes ( 0.9.2342.19200300.100.1.13 NAME 'documentVersion'
+attributetype ( 0.9.2342.19200300.100.1.13 NAME 'documentVersion'
EQUALITY caseIgnoreMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attributes ( 0.9.2342.19200300.100.1.14 NAME 'documentAuthor'
+attributetype ( 0.9.2342.19200300.100.1.14 NAME 'documentAuthor'
EQUALITY distinguishedNameMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.12' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
-attributes ( 0.9.2342.19200300.100.1.15 NAME 'documentLocation'
+attributetype ( 0.9.2342.19200300.100.1.15 NAME 'documentLocation'
EQUALITY caseIgnoreMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attribute ( 0.9.2342.19200300.100.1.20 NAME ( 'homeTelephoneNumber' 'homePhone' )
+attributetype ( 0.9.2342.19200300.100.1.20 NAME ( 'homeTelephoneNumber' 'homePhone' )
EQUALITY telephoneNumberMatch
SUBSTR telephoneNumberSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.50 )
-attribute ( 0.9.2342.19200300.100.1.21 NAME 'secretary'
+attributetype ( 0.9.2342.19200300.100.1.21 NAME 'secretary'
EQUALITY distinguishedNameMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.12' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
# Netscape defines this with syntax 1.15 TBC
-attribute ( 0.9.2342.19200300.100.1.22 NAME 'otherMailbox'
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.39' )
+attributetype ( 0.9.2342.19200300.100.1.22 NAME 'otherMailbox'
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.39 )
# Netscape defines this with syntax 1.15 TBC
+# Mathcing rules for this are unknown
-attribute ( 0.9.2342.19200300.100.1.23 NAME 'lastModifiedTime'
- EQUALITY ??
+attributetype ( 0.9.2342.19200300.100.1.23 NAME 'lastModifiedTime'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.53 )
-attribute ( 0.9.2342.19200300.100.1.24 NAME 'lastModifiedBy'
+attributetype ( 0.9.2342.19200300.100.1.24 NAME 'lastModifiedBy'
EQUALITY distinguishedNameMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.12' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
# This is the definition as defined in RFC2247
+# Terrific, we don't know about caseIgnoreIA5SubstringsMatch
-attribute ( 0.9.2342.19200300.100.1.25 NAME 'dc'
- EQUALITY caseIgnoreIA5Match
- SUBSTR caseIgnoreIA5SubstringsMatch
- SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE )
+# See RFC2247 define in core.schema
+#attributetype ( 0.9.2342.19200300.100.1.25 NAME 'dc'
+# EQUALITY caseIgnoreIA5Match
+# SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE )
# This is aRecord in RFC1274. However, objectclass dNSDomain as we
# and Netscape use it is very different.
-attribute ( 0.9.2342.19200300.100.1.26 NAME 'dNSRecord'
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+attributetype ( 0.9.2342.19200300.100.1.26 NAME 'dNSRecord'
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
# 0.9.2342.19200300.100.1.27 was probably intended to be mDRecord in
# RFC1274, but they got it wrong and did not define it, thought it
# 0.9.2342.19200300.100.1.30 was sOARecord in RFC1274
# 0.9.2342.19200300.100.1.31 was cNAMERecord in RFC1274
-attribute ( 0.9.2342.19200300.100.1.37 NAME 'associatedDomain'
- EQUALITY caseIgnoreIA5Match
- SUBSTR caseIgnoreIA5SubstringsMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+#attribute ( 0.9.2342.19200300.100.1.37 NAME 'associatedDomain'
+# EQUALITY caseIgnoreIA5Match
+# SUBSTR caseIgnoreIA5SubstringsMatch
+# SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attribute ( 0.9.2342.19200300.100.1.38 NAME 'associatedName' DESC
+attributetype ( 0.9.2342.19200300.100.1.38 NAME 'associatedName'
EQUALITY distinguishedNameMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.12' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
# Netscape gives syntax 1.15 to this. TBC
+# We take the matching rules from postalAddress in RFC2256
+# Show stopper: we don't have the definition of caseIgnoreListSubstringsMatch
-attribute ( 0.9.2342.19200300.100.1.39 NAME 'homePostalAddress'
- EQUALITY ??
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.41' )
+attributetype ( 0.9.2342.19200300.100.1.39 NAME 'homePostalAddress'
+ EQUALITY caseIgnoreListMatch
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.41 )
-attribute ( 0.9.2342.19200300.100.1.40 NAME 'personalTitle'
+attributetype ( 0.9.2342.19200300.100.1.40 NAME 'personalTitle'
EQUALITY caseIgnoreMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attribute ( 0.9.2342.19200300.100.1.41 NAME ( 'mobileTelephoneNumber' 'mobile' )
+attributetype ( 0.9.2342.19200300.100.1.41 NAME ( 'mobileTelephoneNumber' 'mobile' )
EQUALITY telephoneNumberMatch
SUBSTR telephoneNumberSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.50 )
-attribute ( 0.9.2342.19200300.100.1.42 NAME ( 'pagerTelephoneNumber' 'pager' )
+attributetype ( 0.9.2342.19200300.100.1.42 NAME ( 'pagerTelephoneNumber' 'pager' )
EQUALITY telephoneNumberMatch
SUBSTR telephoneNumberSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.50 )
-attribute ( 0.9.2342.19200300.100.1.43 NAME ( 'co' 'friendlyCountryName' )
+attributetype ( 0.9.2342.19200300.100.1.43 NAME ( 'co' 'friendlyCountryName' )
EQUALITY caseIgnoreMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attribute ( 0.9.2342.19200300.100.1.44 NAME 'uniqueIdentifier'
+attributetype ( 0.9.2342.19200300.100.1.44 NAME 'uniqueIdentifier'
EQUALITY caseIgnoreMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attribute ( 0.9.2342.19200300.100.1.45 NAME 'organizationalStatus'
+attributetype ( 0.9.2342.19200300.100.1.45 NAME 'organizationalStatus'
EQUALITY caseIgnoreMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attribute ( 0.9.2342.19200300.100.1.46 NAME 'janetMailbox'
+attributetype ( 0.9.2342.19200300.100.1.46 NAME 'janetMailbox'
EQUALITY caseIgnoreIA5Match
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
# Netscape gives syntax 1.27 (integer). However, 1.32 is only listed
# in RFC2252 without explanation. The SINGLE-VALUE thing comes from
# Netscape and is not backed by RFC1274.
-attribute ( 0.9.2342.19200300.100.1.47 NAME 'mailPreferenceOption'
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.32' SINGLE-VALUE )
+attributetype ( 0.9.2342.19200300.100.1.47 NAME 'mailPreferenceOption'
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.32 SINGLE-VALUE )
+
+attributetype ( 0.9.2342.19200300.100.1.48 NAME 'buildingName'
+ EQUALITY caseIgnoreMatch
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
-# 0.9.2342.19200300.100.1.48 was buildingName in RFC1274
# 0.9.2342.19200300.100.1.49 was dSAQuality in RFC1274
# 0.9.2342.19200300.100.1.50 was singleLevelQuality in RFC1274
# 0.9.2342.19200300.100.1.51 was subtreeMinimumQuality in RFC1274
# about this but RFC2252 does not seem to list a specific syntax.
# We had this as 'bin'
-attribute ( 0.9.2342.19200300.100.1.53 NAME 'personalSignature'
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.5' )
+attributetype ( 0.9.2342.19200300.100.1.53 NAME 'personalSignature'
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.5 )
-attribute ( 0.9.2342.19200300.100.1.54 NAME 'dITRedirect'
+attributetype ( 0.9.2342.19200300.100.1.54 NAME 'dITRedirect'
EQUALITY distinguishedNameMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.12' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
# Netscape gives syntax 1.5 to this. We had it as 'bin'.
-attribute ( 0.9.2342.19200300.100.1.55 NAME 'audio'
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.4' )
+attributetype ( 0.9.2342.19200300.100.1.55 NAME 'audio'
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.4 )
-attribute ( 0.9.2342.19200300.100.1.56 NAME 'documentPublisher'
+attributetype ( 0.9.2342.19200300.100.1.56 NAME 'documentPublisher'
EQUALITY caseIgnoreMatch
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-# This one is ripped from Netscape and is a pilot object. It is not
-# in RFC1274, but we had it as 'bin'.
-
-attribute ( 0.9.2342.19200300.100.1.60 NAME 'jpegPhoto'
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.5' )
+# From RFC 2798 (inetOrgPerson)
+attributetype ( 0.9.2342.19200300.100.1.60
+ NAME 'jpegPhoto'
+ DESC 'a JPEG image'
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.28 )
# These attributes are pilot-related attributes that we had and Netscape
# has too, however, the OID is unknown for them and Netscape uses a
# string in place of the missing OID. We will do the same until we
# can make head or tails of this.
-attribute ( abstract-oid NAME 'abstract'
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+attributetype ( abstract-oid NAME 'abstract'
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attribute ( authorcn-oid NAME ( 'documentAuthorCommonName' 'authorCn' )
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+attributetype ( authorcn-oid NAME ( 'documentAuthorCommonName' 'authorCn' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attribute ( authorsn-oid NAME ( 'documentAuthorSurname' 'authorSn' )
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+attributetype ( authorsn-oid NAME ( 'documentAuthorSurname' 'authorSn' )
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attribute ( documentStore-oid NAME 'documentStore'
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+attributetype ( documentStore-oid NAME 'documentStore'
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attribute ( keyWords-oid NAME 'keyWords'
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+attributetype ( keyWords-oid NAME 'keyWords'
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attribute ( obsoletedByDocument-oid NAME 'obsoletedByDocument'
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.12' )
+attributetype ( obsoletedByDocument-oid NAME 'obsoletedByDocument'
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
-attributes ( obsoletesDocument-oid NAME 'obsoletesDocument'
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.12' )
+attributetype ( obsoletesDocument-oid NAME 'obsoletesDocument'
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
-attributes ( subject-oid NAME 'subject'
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
+attributetype ( subject-oid NAME 'subject'
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
-attributes ( updatedByDocument-oid NAME 'updatedByDocument'
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.12' )
+attributetype ( updatedByDocument-oid NAME 'updatedByDocument'
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
-attributes ( updatesDocument-oid NAME 'updatesDocument'
- SYNTAX '1.3.6.1.4.1.1466.115.121.1.12' )
+attributetype ( updatesDocument-oid NAME 'updatesDocument'
+ SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
# In classes, STRUCTURAL or AUXILIARY is chosen depending on the
# textual description that accompanies the class in RFC1274
l $ o $ ou ) )
# This definition is much longer than that in RFC1274 and is taken from RFC2247
-
objectclass ( 0.9.2342.19200300.100.4.13 NAME 'domain' SUP top STRUCTURAL
MUST dc
MAY ( userPassword $ searchGuide $ seeAlso $ businessCategory $