RE: I-D ACTION:draft-ietf-ldapbis-protocol-06.txt

["Ramsay, Ron" <Ron.Ramsay@ca.com>]

Your wordnet is very brief. My (Oxford) dictionary starts with

1. Belonging to a person or thing by nature, innate, inherent, natural to.
2. Unadorned, simple, artless.
3. Of one's birth, where one was born; belonging to one by right of birth.
etc.

I guess you are using 'native' to mean 'natural'. Wordnet prefers
'original'. 'Normal' and 'usual' seem to characterise the LDAP encoding more
than original, natural, native. 'Homespun' would be too rustic.

Well, you've challenged me but I do not feel equal to the task. Does someone
have a thesaurus with some more suitable words?

(I've tried to think of a composer starting with 'R' but I can't un-ravel
the problem. You wrack your brains, I've Rachmaninov.)

Ron.

-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
Sent: Tuesday, 5 March 2002 17:58
To: Ramsay, Ron
Cc: steven.legg@adacel.com.au; ietf-ldapbis@OpenLDAP.org
Subject: RE: I-D ACTION:draft-ietf-ldapbis-protocol-06.txt


At 10:11 PM 2002-03-04, Ramsay, Ron wrote:
>So let's just say there are two encodings. I am not saying the ASN.1 form
is
>'native', I am simply saying that, as the ASN.1 form came first, and, as
you
>say below, the string encoding is based on the ASN.1, one can hardly call
>the LDAP form 'native'.

Again, you imply that ASN.1 data type is an encoding.

Both LDAP encodings (string and binary) are based on the ASN.1
data type definitions, but the string representations were
not only the first encodings of the ASN.1 data type definitions
used in LDAP but are the encodings which originated in LDAP.
The binary transfer encodings were introduced subsequently
and are based on encodings used in DAP.

So, in the dictionary sense:
   native: adj 1: being such by origin.  [WordNet]

the term makes reasonable sense. 

> I would prefer a different adjective.

Such as?

Kurt