Re: [Ltru] Re: Remove extlang from ABNF?

"Felix Sasaki" <fsasaki@w3.org> Wed, 05 December 2007 02:38 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 1Izk9u-0005CE-A7; Tue, 04 Dec 2007 21:38:46 -0500
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1Izk9t-0005Bx-29 for ltru-confirm+ok@megatron.ietf.org; Tue, 04 Dec 2007 21:38:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Izk9s-0005Bh-OU for ltru@lists.ietf.org; Tue, 04 Dec 2007 21:38:44 -0500
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Izk9o-00013D-Vq for ltru@lists.ietf.org; Tue, 04 Dec 2007 21:38:44 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP id 1DF372BC25; Wed, 5 Dec 2007 11:38:39 +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 30qGbVj0MgLO; Wed, 5 Dec 2007 11:38:39 +0900 (JST)
Received: by toro.w3.mag.keio.ac.jp (Postfix, from userid 33) id 0584C2BC1C; Wed, 5 Dec 2007 11:38:38 +0900 (JST)
Received: from 218.110.62.217 (SquirrelMail authenticated user fsasaki) by webmail.w3.mag.keio.ac.jp with HTTP; Wed, 5 Dec 2007 11:38:38 +0900 (JST)
Message-ID: <3151.218.110.62.217.1196822318.squirrel@webmail.w3.mag.keio.ac.jp>
In-Reply-To: <fj50ej$dpo$1@ger.gmane.org>
References: <20071204112939.GA13475@nic.fr> <fj3lel$isq$1@ger.gmane.org><20071204164508.GA24641@nic.fr><C9BF0238EED3634BA1866AEF14C7A9E55DFC390EC2@NA-EXMSG-C116.redmond.corp.microsoft.com> <2996.218.110.62.217.1196815930.squirrel@webmail.w3.mag.keio.ac.jp> <fj50ej$dpo$1@ger.gmane.org>
Date: Wed, 05 Dec 2007 11:38:38 +0900
Subject: Re: [Ltru] Re: Remove extlang from ABNF?
From: Felix Sasaki <fsasaki@w3.org>
To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
User-Agent: SquirrelMail/1.4.9a
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-2022-jp"
X-Priority: 3 (Normal)
Importance: Normal
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: ltru@lists.ietf.org
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: fsasaki@w3.org
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

> Felix Sasaki wrote:
>
>> We spend a fair amount of time to evangelize BCP 47 with RFC 4646
>> syntax this year within W3C (not only XML Schema WG)
>
> That the WG claiming that IRI is just a modern name for URI, or do I
> confuse this with XHTML modularization ?
>
>> always saying "The ABNF is stable". I don't plan to go back to
>> these people to say now "stable, but ..."
>
> It's stable in the sense that it won't match any existing tag, and
> it will continue to not match any existing tag.

you are discussing in terms of data. I argued to working groups in terms
of an ABNF and asking them "please implement this ABNF in your spec, it is
stable *as an ABNF*".

This argument of stability of the ABNF (not data) was (and is) is a very
strong means for BCP 47 outreach to emerging technologies. Changing the
ABNF now means potentially loosing this argument.

Felix


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