[Ltru] Re: Is 639-3 bogus ?

Frank Ellermann <nobody@xyzzy.claranet.de> Tue, 10 October 2006 16:37 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXKbo-0001CI-T0; Tue, 10 Oct 2006 12:37:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXKbn-0001CC-C6 for ltru@lists.ietf.org; Tue, 10 Oct 2006 12:37:35 -0400
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXKbl-0004g8-1T for ltru@lists.ietf.org; Tue, 10 Oct 2006 12:37:35 -0400
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GXKbE-0006Sq-2w for ltru@lists.ietf.org; Tue, 10 Oct 2006 18:37:00 +0200
Received: from d252018.dialin.hansenet.de ([80.171.252.18]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ltru@lists.ietf.org>; Tue, 10 Oct 2006 18:37:00 +0200
Received: from nobody by d252018.dialin.hansenet.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ltru@lists.ietf.org>; Tue, 10 Oct 2006 18:37:00 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: ltru@lists.ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Tue, 10 Oct 2006 18:35:53 +0200
Organization: <URL:http://purl.net/xyzzy>
Lines: 23
Message-ID: <452BCBE9.56D0@xyzzy.claranet.de>
References: <452B995B.92F@xyzzy.claranet.de> <F8ACB1B494D9734783AAB114D0CE68FE0B1B1999@RED-MSG-52.redmond.corp.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: d252018.dialin.hansenet.de
X-Mailer: Mozilla 3.0 (OS/2; U)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc:
Subject: [Ltru] Re: Is 639-3 bogus ?
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Errors-To: ltru-bounces@ietf.org

Peter Constable wrote:

> One can read all my thoughts on this that have been published
> elsewhere (see http://www.sil.org/silewp/2000/001/).

That doesn't explain "orq".  And the ethnologue site claims that
"orq" is no SIL code.  So how did it get added to a 639-3 draft ?

There must be some procedure, and if that procedure is broken it
needs to be fixed before nonsense is added to a registry designed
for stability.  There's no way to get rid of "orq" later, at best
it could be deprecated.

Of course one "orq" is harmless and not worse than say "tlh", but
if that's only the tip of an iceberg spammers and criminals will
abuse it as fast as 1-2-3 to create their virtual "Cesidian root"
or "Dominion of Melchizedek" realities.

We can't have IANA servers confiscated in criminal investigations
about DOM.  

Frank



_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www1.ietf.org/mailman/listinfo/ltru