Re: [Ltru] Last open item

John Cowan <cowan@ccil.org> Tue, 15 April 2008 19:09 UTC

Return-Path: <ltru-bounces@ietf.org>
X-Original-To: ltru-archive@megatron.ietf.org
Delivered-To: ietfarch-ltru-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6DBF428C0EC; Tue, 15 Apr 2008 12:09:52 -0700 (PDT)
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 08EF73A6E55 for <ltru@core3.amsl.com>; Tue, 15 Apr 2008 12:09:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.475
X-Spam-Level:
X-Spam-Status: No, score=-2.475 tagged_above=-999 required=5 tests=[AWL=0.124, BAYES_00=-2.599]
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 K1glHgGKSyY6 for <ltru@core3.amsl.com>; Tue, 15 Apr 2008 12:09:50 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by core3.amsl.com (Postfix) with ESMTP id B711A3A6D5D for <ltru@ietf.org>; Tue, 15 Apr 2008 12:09:49 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.63) (envelope-from <cowan@ccil.org>) id 1JlqXu-00011D-QZ; Tue, 15 Apr 2008 15:10:22 -0400
Date: Tue, 15 Apr 2008 15:10:22 -0400
To: Randy Presuhn <randy_presuhn@mindspring.com>
Message-ID: <20080415191022.GA15414@mercury.ccil.org>
References: <30b660a20804101252p37e22884g6dfbec6dd17e5ea1@mail.gmail.com> <006101c89daa$323fc3e0$6801a8c0@oemcomputer> <30b660a20804140815w5d56933auefbdccdcbdfe034b@mail.gmail.com> <001e01c89e4b$897c0000$6801a8c0@oemcomputer> <20080414193212.GI28132@mercury.ccil.org> <002601c89e94$80c98ce0$6801a8c0@oemcomputer> <20080415021154.GK19045@mercury.ccil.org> <001001c89ea2$29a61560$6801a8c0@oemcomputer> <20080415170448.GJ28132@mercury.ccil.org> <002601c89f17$aff089a0$6801a8c0@oemcomputer>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <002601c89f17$aff089a0$6801a8c0@oemcomputer>
User-Agent: Mutt/1.5.13 (2006-08-11)
From: John Cowan <cowan@ccil.org>
Cc: LTRU Working Group <ltru@ietf.org>
Subject: Re: [Ltru] Last open item
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ltru-bounces@ietf.org
Errors-To: ltru-bounces@ietf.org

Randy Presuhn scripsit:

> One of the motivations for the formation of this working group was
> to provide a way to insulate language tags from what was perceived as
> excessive instability in some of the code sources.

That is to say, we couldn't at the time trust ISO 3166/MA not to reassign
code elements to new meanings; in addition, there was no one-stop shop
for subtags (see below).

> After all, if we're just going to blindly track the ISO code du jour
> for every little piece of dirt, there's really little point to even
> bothering to put these things in our registry.

I would be slow to call a sovereign nation a "little piece of dirt".

> If consistency with other uses of those source specifications trumps
> stability as a consideration, then we should throw out our current
> procedures and registry, just say "see ISO registry mumble for these
> codes", and limit our registry and procedures exclusively to codes
> for things that ISO hasn't coded.

I disagree entirely: even if it weren't stable (in my sense), the
convenience of having a single registry to look at in a machine-readable
format, instead of four registries in random prose formats, is
considerable.

> Otherwise, we will find ourselves in the situation that a tag found
> to be OK be a validating processor will suddenly become not OK.
> That's simply not acceptable.

Are you under the impression that either RFC 4646 or the current draft
requires a validating processor to reject deprecated subtags?  That is not
so.  There is language in 3.1.5 (of either version) that says validating
processors SHOULD NOT *generate* them, but that's a different story.

-- 
A poetical purist named Cowan           [that's me: cowan@ccil.org]
Once put the rest of us dowan.          [on xml-dev]
    "Your verse would be sweeter        http://www.ccil.org/~cowan
    If it only had metre
And rhymes that didn't force me to frowan."     [overpacked line!] --Michael Kay
_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www.ietf.org/mailman/listinfo/ltru