3 # These are definitions from the North American Directory Forum
4 # They are intended to be used with QUIPU/X.500 not LDAPv3.
5 # Your mileage may vary.
7 # They were acquired from ftp://ftp.gte.com/pub/nadf/nadf-docs/sd-04.ps
8 # Our thanks to Harald T. Alvestrand that provided the pointer.
10 # This is a preliminary version and is likely to be incorrect in
11 # a number of areas. Use with exterme caution.
13 # The root for OIDs is joint-iso-ccitt mhs-motis(6) group(6) grimstad(5)
14 # nadf(2). In othor words, barring any error, 2.6.6.5.2. Then,
15 # nadfOink ::= 2.6.6.5.2.0
16 # nadfModule ::= 2.6.6.5.2.1
17 # nadfAttributeType ::= 2.6.6.5.2.4
18 # nadfObjectClass ::= 2.6.6.5.2.6
20 # Attribute Type Definition
22 attributetype ( 2.6.6.5.2.4.1 NAME 'fipsStateNumericCode'
23 EQUALITY numericStringMatch
24 SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{2} )
26 # It is probably inconvenient to give this attribute that syntax
27 # (Printable String) instead of Directory String.
29 attributetype ( 2.6.6.5.2.4.2 NAME 'fipsStateAlphaCode'
30 EQUALITY caseIgnoreMatch
31 SYNTAX 1.3.6.1.4.1.1466.115.121.1.44{2} )
33 attributetype ( 2.6.6.5.2.4.3 NAME 'fipsCountyNumericCode'
34 EQUALITY numericStringMatch
35 SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{5} )
37 # It seems that fips55 is fipsPlaceNumericCode, is this so?
39 attributetype ( 2.6.6.5.2.4.4 NAME ( 'fipsPlaceNumericCode' 'fips55' )
40 EQUALITY numericStringMatch
41 SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{5} )
43 attributetype ( 2.6.6.5.2.4.5 NAME 'ansiOrgNumericCode'
45 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 )
47 # Apparently, 'ad' is an alias for 'addmdName'
49 attributetype ( 2.6.6.5.2.4.6 NAME ( 'addmdName' 'ad' )
50 EQUALITY caseIgnoreMatch
51 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
53 # I don't know what syntax to give this. I will use binary for the
56 attributetype ( 2.6.6.5.2.4.7 NAME 'nadfSearchGuide'
57 SYNTAX 1.3.6.1.4.1.1466.115.121.1.5 )
59 attributetype ( 2.6.6.5.2.4.8 NAME 'supplementaryInformation'
60 EQUALITY caseIgnoreMatch
61 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{76} )
63 attributetype ( 2.6.6.5.2.4.9 NAME 'namingLink'
64 SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
66 attributetype ( 2.6.6.5.2.4.10 NAME 'reciprocalNamingLink'
67 SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
70 # Numbers 11 to 14 are obsolete
72 # Next one is unused. BTW, this attribute is supposed to be
73 # case-exact match, but we cannot make that match unless we
74 # define the string with IA5 syntax and we don't have a
75 # clear base for this.
77 attributetype ( 2.6.6.5.2.4.15 NAME 'logicalDSAReference'
78 EQUALITY caseIgnoreMatch
79 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
81 attributetype ( 2.6.6.5.2.4.16 NAME 'multiMediaInformation'
82 SYNTAX 1.3.6.1.4.1.1466.115.121.1.5 )
84 # Number 17, 18 and 19 are EDI-related attributes for the nadfEDIUser
85 # class that we did not have and has been left out below.
89 # According to the intended use described in section 3.3.1 in the spec,
90 # this can only be ABSTRACT.
91 # We had lastModifiedTime as 'allows', but sd-04 has it as MUST.
92 # We did not have multiMediaInformation neither on this class nor
93 # on any of its derived classes.
95 objectclass ( 2.6.6.5.2.6.7 NAME 'nadfObject' SUP top ABSTRACT
97 MAY ( multiMediaInformation $ nadfSearchGuide $
98 supplementaryInformation ) )
100 # I think all classes derived from locality should be considered
101 # STRUCTURAL, since locality is.
103 objectclass ( 2.6.6.5.2.6.1 NAME 'usStateOrEquivalent'
104 SUP ( locality $ nadfObject ) STRUCTURAL
105 MUST ( l $ fipsStateNumericCode $ fipsStateAlphaCode $ st ) )
107 objectclass ( 2.6.6.5.2.6.2 NAME 'usPlace'
108 SUP ( locality $ nadfObject ) STRUCTURAL
109 MUST ( l $ fipsPlaceNumericCode ) )
111 objectclass ( 2.6.6.5.2.6.3 NAME 'usCountyOrEquivalent' SUP usPlace STRUCTURAL
112 MUST fipsCountyNumericCode )
114 # applicationEntity is STRUCTURAL, so we will declare this one the same
116 objectclass ( 2.6.6.5.2.6.5 NAME 'nadfApplicationEntity'
117 SUP applicationEntity STRUCTURAL
118 MUST supportedApplicationContext )
120 # Following our heuristic, this one will be STRUCTURAL since organization
121 # is too. We did not have 'o' as 'requires', but if this is really a
122 # subclass of organization, then 'o' becomes MUST by inheritance
124 objectclass ( 2.6.6.5.2.6.6 NAME 'nadfADDMD'
125 SUP ( organization $ nadfObject ) STRUCTURAL
128 # Number 7 is nadfObject described above.
130 # This one quacks like an AUXILIARY object class
132 objectclass ( 2.6.6.5.2.6.8 NAME 'publicObject' SUP top AUXILIARY
135 # And so does this one
137 objectclass ( 2.6.6.5.2.6.9 NAME 'providerObject' SUP top AUXILIARY
138 MUST reciprocalNamingLink )
140 # The spec says number 10 is obsolete
142 # This one also strongly smells like AUXILIARY
144 objectclass ( 2.6.6.5.2.6.11 NAME 'fips55Object' SUP top AUXILIARY
145 MUST fipsPlaceNumericCode
148 # The spec says numbers 12 to 18 are obsolete
150 # Another obviously AUXILIARY class
152 objectclass ( 2.6.6.5.2.6.19 NAME 'nationalObject' SUP top AUXILIARY
157 objectclass ( 2.6.6.5.2.6.20 NAME 'ansiOrgObject' SUP top AUXILIARY
158 MUST ansiOrgNumericCode )
160 # We did not have the next one, but it is innocuous
162 objectclass ( 2.6.6.5.2.6.21 NAME 'caProvinceOrTerritory'
163 SUP ( locality $ nadfObject ) STRUCTURAL
166 # According to the spec, numbers 22, 23 and 24 are obsolete
168 # Number 25 was nadfEDIuser as a subclass of edi-user. Sorry we cannot
169 # deal with this one and we did not have it anyway.