[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
draft-ietf-ldapbis-syntaxes-02: oid = descr / numericoid
- Subject: draft-ietf-ldapbis-syntaxes-02: oid = descr / numericoid
- From: Michael Ströder <michael@stroeder.com>
- Date: Sun, 01 Sep 2002 15:44:33 +0200
- Cc: ietf-ldapbis@OpenLDAP.org
- References: <OF9F885FFF.9C1F3D54-ON85256C23.005FDF84@pok.ibm.com>
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
HI!
I'd like to propose a change to draft-ietf-ldapbis-syntaxes-02 since I
noticed some problems with same OID textual descriptions being used for
object classes and attribute types.
Current text:
------------------------------ snip ----------------------------
When 'oid' elements occur in a value, the 'descr' notation option
SHOULD be used in preference to the 'numericoid'. An object
descriptor is more readable than a numeric OBJECT IDENTIFIER, and a
descriptor (where assigned and known by the implementation) SHOULD
be used in preference to numeric oids to the greatest extent
possible. Examples of object descriptors in LDAP are attribute
type, object class, and matching rule names.
oid = descr / numericoid
------------------------------ snip ----------------------------
IMHO the other way round is better since it causes less grief on side of
a schema-aware application:
When 'oid' elements occur in a value, the 'numericoid' notation
option SHOULD be used in preference to the 'descr'. An object
descriptor might be ambigously used
to specify an attribute type, an object class or a matching rule
name.
Please excuse my poor English.
Ciao, Michael.