Re: [Ltru] rechartering to handle 639-6

"Phillips, Addison" <addison@amazon.com> Thu, 16 July 2009 05:09 UTC

Return-Path: <addison@amazon.com>
X-Original-To: ltru@core3.amsl.com
Delivered-To: ltru@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 97ECE3A6A5D for <ltru@core3.amsl.com>; Wed, 15 Jul 2009 22:09:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.513
X-Spam-Level:
X-Spam-Status: No, score=-106.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g7tfA02OYL99 for <ltru@core3.amsl.com>; Wed, 15 Jul 2009 22:09:17 -0700 (PDT)
Received: from smtp-fw-9101.amazon.com (smtp-fw-9101.amazon.com [207.171.184.25]) by core3.amsl.com (Postfix) with ESMTP id 3AD733A68B7 for <ltru@ietf.org>; Wed, 15 Jul 2009 22:09:11 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,409,1243814400"; d="scan'208";a="244103136"
Received: from smtp-in-1104.vdc.amazon.com ([10.140.10.25]) by smtp-border-fw-out-9101.sea19.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 16 Jul 2009 05:07:00 +0000
Received: from ex-hub-4104.ant.amazon.com (ex-hub-4104.sea5.amazon.com [10.248.163.25]) by smtp-in-1104.vdc.amazon.com (8.12.11/8.12.11) with ESMTP id n6G56xEZ017004 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL); Thu, 16 Jul 2009 05:06:59 GMT
Received: from EX-SEA5-D.ant.amazon.com ([10.248.163.30]) by ex-hub-4104.ant.amazon.com ([10.248.163.25]) with mapi; Wed, 15 Jul 2009 22:06:59 -0700
From: "Phillips, Addison" <addison@amazon.com>
To: John Cowan <cowan@ccil.org>, Doug Ewell <doug@ewellic.org>
Date: Wed, 15 Jul 2009 22:06:55 -0700
Thread-Topic: [Ltru] rechartering to handle 639-6
Thread-Index: AcoF0OLMWHk3csaGRAOp4cXxjmJ+yQAAdtfA
Message-ID: <4D25F22093241741BC1D0EEBC2DBB1DA01AB76493A@EX-SEA5-D.ant.amazon.com>
References: <mailman.14390.1247692636.4936.ltru@ietf.org> <2C301BED90C8444795F972900C5C6E24@DGBP7M81> <20090716042905.GK27069@mercury.ccil.org>
In-Reply-To: <20090716042905.GK27069@mercury.ccil.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: LTRU Working Group <ltru@ietf.org>
Subject: Re: [Ltru] rechartering to handle 639-6
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jul 2009 05:09:18 -0000

> 
> > Any proposal to assign variants on a systematic, formulaic basis
> -- not
> > three or four, but dozens or hundreds or thousands -- ought to
> make us
> > stop and wonder why we don't establish an extension for the
> purpose
> > instead:
> 
> The point of creating an extension is to provide additional
> orthogonal
> information that is packaged up with the language tag.  (IMHO this
> is
> rather silly, as few databases allow only one field, but who knows.)
> They aren't meant to be used for specification that of language
> variant
> information; that is semantically part of the language tag and
> belongs
> in the variant field.
> 

Well, that isn't necessarily so. I know that the RFC-to-be says that extensions are "orthogonal". But an extension could be created that wasn’t entirely orthogonal to language identification. It might provide finer-grained identification (such as 639-6 is purported to provide) than variants might provide. I think that having an extension proposal would actually be the test of whether it were an appropriate use or not. Just as having 639-6 in a relatively mature state is an important pre-condition to its potential incorporation into the corpus of BCP 47.

Addison