3 # These are definitions from the North American Directory Forum
4 # They were taken from ftp://ftp.gte.com/pub/nadf/nadf-docs/sd-04.ps
5 # Our thanks to Harald T. Alvestrand that provided the pointer.
7 # This is a preliminary version and is likely to be incorrect in
10 # The root for OIDs is joint-iso-ccitt mhs-motis(6) group(6) grimstad(5)
11 # nadf(2). In othor words, barring any error, 2.6.6.5.2. Then,
12 # nadfOink ::= 2.6.6.5.2.0
13 # nadfModule ::= 2.6.6.5.2.1
14 # nadfAttributeType ::= 2.6.6.5.2.4
15 # nadfObjectClass ::= 2.6.6.5.2.6
17 # Attribute Type Definition
19 # The spec says "leading zero is significant". Is this really a
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 # The spec says "leading zeros are significant". Is this really a
36 attributetype ( 2.6.6.5.2.4.3 NAME 'fipsCountyNumericCode'
37 EQUALITY numericStringMatch
38 SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{5} )
40 # It seems that fips55 is fipsPlaceNumericCode, is this so?
42 # The spec says "leading zeros are significant". Is this really a
45 attributetype ( 2.6.6.5.2.4.4 NAME ( 'fipsPlaceNumericCode' 'fips55' )
46 EQUALITY numericStringMatch
47 SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{5} )
49 attributetype ( 2.6.6.5.2.4.5 NAME 'ansiOrgNumericCode'
51 SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 )
53 # Apparently, 'ad' is an alias for 'addmdName'
55 attributetype ( 2.6.6.5.2.4.6 NAME ( 'addmdName' 'ad' )
56 EQUALITY caseIgnoreMatch
57 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
59 # I don't know what syntax to give this. I will use binary for the
62 attributetype ( 2.6.6.5.2.4.7 NAME 'nadfSearchGuide'
63 SYNTAX 1.3.6.1.4.1.1466.115.121.1.5 )
65 attributetype ( 2.6.6.5.2.4.8 NAME 'supplementaryInformation'
66 EQUALITY caseIgnoreMatch
67 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{76} )
69 attributetype ( 2.6.6.5.2.4.9 NAME 'namingLink'
70 SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
72 attributetype ( 2.6.6.5.2.4.10 NAME 'reciprocalNamingLink'
73 SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
76 # Numbers 11 to 14 are obsolete
78 # Next one is unused. BTW, this attribute is supposed to be
79 # case-exact match, but we cannot make that match unless we
80 # define the string with IA5 syntax and we don't have a
81 # clear base for this.
83 attributetype ( 2.6.6.5.2.4.15 NAME 'logicalDSAReference'
84 EQUALITY caseIgnoreMatch
85 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
87 attributetype ( 2.6.6.5.2.4.16 NAME 'multiMediaInformation'
88 SYNTAX 1.3.6.1.4.1.1466.115.121.1.5 )
90 # Number 17, 18 and 19 are EDI-related attributes for the nadfEDIUser
91 # class that we did not have and has been left out below.
95 # According to the intended use described in section 3.3.1 in the spec,
96 # this can only be ABSTRACT.
97 # We had lastModifiedTime as 'allows', but sd-04 has it as MUST.
98 # We did not have multiMediaInformation neither on this class nor
99 # on any of its derived classes.
101 objectclass ( 2.6.6.5.2.6.7 NAME 'nadfObject' SUP top ABSTRACT
102 MUST lastModifiedTime
103 MAY ( multiMediaInformation $ nadfSearchGuide $
104 supplementaryInformation ) )
106 # I think all classes derived from locality should be considered
107 # STRUCTURAL, since locality is.
109 objectclass ( 2.6.6.5.2.6.1 NAME 'usStateOrEquivalent'
110 SUP ( locality $ nadfObject ) STRUCTURAL
111 MUST ( l $ fipsStateNumericCode $ fipsStateAlphaCode $ st ) )
113 objectclass ( 2.6.6.5.2.6.2 NAME 'usPlace'
114 SUP ( locality $ nadfObject ) STRUCTURAL
115 MUST ( l $ fipsPlaceNumericCode ) )
117 objectclass ( 2.6.6.5.2.6.3 NAME 'usCountyOrEquivalent' SUP usPlace STRUCTURAL
118 MUST fipsCountyNumericCode )
120 # applicationEntity is STRUCTURAL, so we will declare this one the same
122 objectclass ( 2.6.6.5.2.6.5 NAME 'nadfApplicationEntity'
123 SUP applicationEntity STRUCTURAL
124 MUST supportedApplicationContext )
126 # Following our heuristic, this one will be STRUCTURAL since organization
127 # is too. We did not have 'o' as 'requires', but if this is really a
128 # subclass of organization, then 'o' becomes MUST by inheritance
130 objectclass ( 2.6.6.5.2.6.6 NAME 'nadfADDMD'
131 SUP ( organization $ nadfObject ) STRUCTURAL
134 # Number 7 is nadfObject described above.
136 # This one quacks like an AUXILIARY object class
138 objectclass ( 2.6.6.5.2.6.8 NAME 'publicObject' SUP top AUXILIARY
141 # And so does this one
143 objectclass ( 2.6.6.5.2.6.9 NAME 'providerObject' SUP top AUXILIARY
144 MUST reciprocalNamingLink )
146 # The spec says number 10 is obsolete
148 # This one also strongly smells like AUXILIARY
150 objectclass ( 2.6.6.5.2.6.11 NAME 'fips55Object' SUP top AUXILIARY
151 MUST fipsPlaceNumericCode
154 # The spec says numbers 12 to 18 are obsolete
156 # Another obviously AUXILIARY class
158 objectclass ( 2.6.6.5.2.6.19 NAME 'nationalObject' SUP top AUXILIARY
163 objectclass ( 2.6.6.5.2.6.20 NAME 'ansiOrgObject' SUP top AUXILIARY
164 MUST ansiOrgNumericCode )
166 # We did not have the next one, but it is innocuous
168 objectclass ( 2.6.6.5.2.6.21 NAME 'caProvinceOrTerritory'
169 SUP ( locality $ nadfObject ) STRUCTURAL
172 # According to the spec, numbers 22, 23 and 24 are obsolete
174 # Number 25 was nadfEDIuser as a subclass of edi-user. Sorry we cannot
175 # deal with this one and we did not have it anyway.