Re: uppercase attribute names

["Kurt D. Zeilenga" <Kurt@OpenLDAP.org>]

Hallvard,

The documents follow a well-established (before LDAP), widely accepted
practice in uppercasing very short attribute type descriptors appearing
in AVAs.  I don't see your view that this usage is "ugly" as being
technically relevant and certainly is quite subjective.  I believe
the choice of case here should be left to the editors on the grounds
that, to the protocol/models, case doesn't matter.

As far as the case in the examples being different than the case in
the name field of their descriptions, I note that case used in the
examples is generally consistent with their official IANA registrations
and other definitive tables of attribute type descriptors.  One could
(I won't) argue that it is the name fields which should be changed.

As far as guidance (to schema designers), that's a topic for future
documents (considerations for schema designers).

Kurt

At 09:23 AM 12/15/2003, Hallvard B Furuseth wrote:
>I dislike the uppercased attribute names used particularly in examples
>of DNs (including LDAP URIs) and RDNs.  People copy usage from examples.
>Uppercase is ugly, it's different from the attribute names in [Schema],
>and it gives no guidance to how to upper/lowercase attribute names that
>consist of several words.
>
>This occurs in [Models], [Protocol], [DN] (including the table of
>attributes to recognize in DNs) and [Syntaxes].
>Also draft-zeilenga-ldap-rfc2596-04.txt.
>
>There are some uppercase names outside DNs too, and it would be nice to
>get at them as well.  However, that's less important because it doesn't
>set an example of how to spell them in the same way as DN examples do
>(because they are spelled with lowercase in [schema]):
>
>[Models], [Authmeth], [DN], draft-zeilenga-ldap-rfc2596-04.txt.
>
>-- 
>Hallvard