Now understand with Hallvard was commenting on in ITS#1669.

Removed "leading" comments and added a general caution statement.
This schema will be pulled from 2.1.

diff --git a/servers/slapd/schema/nadf.schema b/servers/slapd/schema/nadf.schema
index 98fe9a41e5f8290306e191a75ba2f095b03b29ce..1da0e5396f2f330c11e5ed02cae7dc8ba8a357b9 100644 (file)
--- a/servers/slapd/schema/nadf.schema
+++ b/servers/slapd/schema/nadf.schema
@@ -8,7 +8,7 @@
 # Our thanks to Harald T. Alvestrand that provided the pointer.
 
 # This is a preliminary version and is likely to be incorrect in
-# a number of areas
+# a number of areas.  Use with exterme caution.
 
 # The root for OIDs is joint-iso-ccitt mhs-motis(6) group(6) grimstad(5)
 # nadf(2).  In othor words, barring any error, 2.6.6.5.2.  Then,
@@ -19,9 +19,6 @@
 
 # Attribute Type Definition
 
-# The spec says "leading zero is significant".  Is this really a
-# numeric string?
-
 attributetype ( 2.6.6.5.2.4.1 NAME 'fipsStateNumericCode'
        EQUALITY numericStringMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{2} )
@@ -33,18 +30,12 @@ attributetype ( 2.6.6.5.2.4.2 NAME 'fipsStateAlphaCode'
        EQUALITY caseIgnoreMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.44{2} )
 
-# The spec says "leading zeros are significant".  Is this really a
-# numeric string?
-
 attributetype ( 2.6.6.5.2.4.3 NAME 'fipsCountyNumericCode'
        EQUALITY numericStringMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{5} )
 
 # It seems that fips55 is fipsPlaceNumericCode, is this so?
 
-# The spec says "leading zeros are significant".  Is this really a
-# numeric string?
-
 attributetype ( 2.6.6.5.2.4.4 NAME ( 'fipsPlaceNumericCode' 'fips55' )
        EQUALITY numericStringMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{5} )