Re: [Ltru] Re: Remove extlang from ABNF?
Felix Sasaki <fsasaki@w3.org> Wed, 05 December 2007 17:48 UTC
Return-path: <ltru-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzyMJ-0004u0-Pz; Wed, 05 Dec 2007 12:48:31 -0500
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1IzyMI-0004tn-QX for ltru-confirm+ok@megatron.ietf.org; Wed, 05 Dec 2007 12:48:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzyMI-0004td-Gz for ltru@lists.ietf.org; Wed, 05 Dec 2007 12:48:30 -0500
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IzyMG-0001Qp-ET for ltru@lists.ietf.org; Wed, 05 Dec 2007 12:48:30 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP id ABBD52BC28; Thu, 6 Dec 2007 02:48:24 +0900 (JST)
Received: from toro.w3.mag.keio.ac.jp ([127.0.0.1]) by localhost (toro.w3.mag.keio.ac.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ldJC8u1yBGf; Thu, 6 Dec 2007 02:48:24 +0900 (JST)
Received: from [127.0.0.1] (p3080-ipad508marunouchi.tokyo.ocn.ne.jp [222.148.90.80]) by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP id 7569A2BC1E; Thu, 6 Dec 2007 02:48:24 +0900 (JST)
Message-ID: <4756E463.9070809@w3.org>
Date: Thu, 06 Dec 2007 02:48:19 +0900
From: Felix Sasaki <fsasaki@w3.org>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Subject: Re: [Ltru] Re: Remove extlang from ABNF?
References: <20071204112939.GA13475@nic.fr><fj3lel$isq$1@ger.gmane.org> <20071204164508.GA24641@nic.fr> <e395be80712041022o21b41464g3999c322d93d43a2@mail.gmail.com> <20071204190505.GF15972@mercury.ccil.org><30b660a20712041852g629e904n588738e8373cea26@mail.gmail.com> <47561C1C.9040307@w3.org><fj57k5$tcq$1@ger.gmane.org> <47562F2D.4050000@w3.org> <fj6i5e$use$1@ger.gmane.org>
In-Reply-To: <fj6i5e$use$1@ger.gmane.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: ltru@lists.ietf.org
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
Frank Ellermann wrote: > Felix Sasaki wrote: > > >> Maybe you are not aware of the situation that language tags are nearly >> the only IETF spec where W3C uses a BCP reference, or before that an >> "RFC XXX or its successor" reference - in difference to IRI, btw . >> > > Yes, some including me proposed standards track for 4646, but the > rough consensus was BCP :-( You use 2119 (BCP 14) quite often in W3C > spec.s, but that's no moving target. Unlike RFC 4646, were "moving > target" was predictable at least for extlang: > > | reserved for future standardization, anticipating work that is > | currently under way on ISO 639. > [...] > | Their syntax is described here so that implementations can be > | compatible with any future revision of this document that does > | provide for their registration. > [...] > | "zh-gan" (registered under RFC 3066) might become a valid non- > | grandfathered (that is, redundant) tag in which the subtag > | 'gan' might represent the Chinese dialect 'Gan'. > > Note "might", it's not "shall". We weren't sure, and the reasons > to drop "extlang" are rather complex (e.g. 639-3 is more volatile > than expected with its macrolanguages at the moment, not good for > a "stable forver" registry). > > I still don't see the harm if an implementation based on RFC 4646 > identifies a bogus (non-existing) tag as "well-formed", where a > 4646bis implementation would see "not well-formed" with the clean > ABNF proposal. And both editors would apparently prefer "clean". > > >> You might say you don't care about this status >> > > And I did, see above, 4646bis could be a nice "draft standard" > soon. Dropping unused features in a DS is perfectly okay. It's > also okay in a BCP, but apparently you tjink it's not. > exactly - or rather specs citing BCP 47. That's my whole point - the danger that specs writers might look at the dropped extlang and say "they are dropping features between versions of BCP 47, so we better refer to an RFC *only* and even leave 'or its successor' out". If they would have done that already, we would have many "dead references" to RFC 4646 . Felix _______________________________________________ Ltru mailing list Ltru@ietf.org https://www1.ietf.org/mailman/listinfo/ltru
- [Ltru] summary of recommendations coming out of t… Peter Constable
- Re: [Ltru] summary of recommendations coming out … Addison Phillips
- [Ltru] Remove extlang from ABNF? (Was: summary of… Stephane Bortzmeyer
- [Ltru] RE: Remove extlang from ABNF? (Was: summar… Peter Constable
- Re: [Ltru] RE: Remove extlang from ABNF? (Was: su… Felix Sasaki
- RE: [Ltru] RE: Remove extlang from ABNF? Kent Karlsson
- [Ltru] Re: Remove extlang from ABNF? Stephane Bortzmeyer
- [Ltru] Re: Remove extlang from ABNF? Frank Ellermann
- [Ltru] Re: Remove extlang from ABNF? Stephane Bortzmeyer
- Re: [Ltru] Re: Remove extlang from ABNF? Ira McDonald
- Re: [Ltru] Re: Remove extlang from ABNF? John Cowan
- RE: [Ltru] Re: Remove extlang from ABNF? Shawn Steele
- Re: [Ltru] Re: Remove extlang from ABNF? John Cowan
- Re: [Ltru] Re: Remove extlang from ABNF? Addison Phillips
- RE: [Ltru] Re: Remove extlang from ABNF? Shawn Steele
- [Ltru] Re: Remove extlang from ABNF? Frank Ellermann
- [Ltru] Re: Remove extlang from ABNF? Frank Ellermann
- RE: [Ltru] Re: Remove extlang from ABNF? Felix Sasaki
- Re: [Ltru] Re: Remove extlang from ABNF? Ira McDonald
- [Ltru] Re: Remove extlang from ABNF? Frank Ellermann
- Re: [Ltru] Re: Remove extlang from ABNF? Felix Sasaki
- Re: [Ltru] Re: Remove extlang from ABNF? Mark Davis
- Re: [Ltru] Re: Remove extlang from ABNF? John Cowan
- Re: [Ltru] Re: Remove extlang from ABNF? Felix Sasaki
- Re: [Ltru] Re: Remove extlang from ABNF? Mark Davis
- Re: [Ltru] Re: Remove extlang from ABNF? Mark Davis
- [Ltru] Re: Remove extlang from ABNF? Frank Ellermann
- Re: [Ltru] Re: Remove extlang from ABNF? John Cowan
- [Ltru] Re: Remove extlang from ABNF? Frank Ellermann
- Re: [Ltru] Re: Remove extlang from ABNF? Felix Sasaki
- Re: [Ltru] Re: Remove extlang from ABNF? Felix Sasaki
- Re: [Ltru] Re: Remove extlang from ABNF? Addison Phillips
- Re: [Ltru] Re: Remove extlang from ABNF? Mark Davis
- RE: [Ltru] Re: Remove extlang from ABNF? Peter Constable
- RE: [Ltru] Re: Remove extlang from ABNF? Peter Constable
- [Ltru] Re: Remove extlang from ABNF? Frank Ellermann
- RE: [Ltru] Re: Remove extlang from ABNF? Peter Constable
- Re: [Ltru] Re: Remove extlang from ABNF? Felix Sasaki
- Re: [Ltru] Re: Remove extlang from ABNF? Felix Sasaki
- RE: [Ltru] Re: Remove extlang from ABNF? Peter Constable
- Re: [Ltru] Re: Remove extlang from ABNF? Felix Sasaki
- RE: [Ltru] Re: Remove extlang from ABNF? Shawn Steele
- Re: [Ltru] Re: Remove extlang from ABNF? Ira McDonald
- RE: [Ltru] Re: Remove extlang from ABNF? Peter Constable
- Re: [Ltru] Re: Remove extlang from ABNF? Addison Phillips
- Re: [Ltru] Re: Remove extlang from ABNF? Mark Davis
- [Ltru] Re: Remove extlang from ABNF? Frank Ellermann
- Re: [Ltru] Re: Remove extlang from ABNF? Martin Duerst
- Re: [Ltru] RE: Remove extlang from ABNF? (Was: su… Martin Duerst
- RE: [Ltru] Re: Remove extlang from ABNF? Shawn Steele
- RE: [Ltru] Re: Remove extlang from ABNF? Peter Constable
- RE: [Ltru] Re: Remove extlang from ABNF? Peter Constable
- [Ltru] Re: Remove extlang from ABNF? Frank Ellermann
- Re: [Ltru] Re: Remove extlang from ABNF? Marion Gunn