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

Felix Sasaki <fsasaki@w3.org> Wed, 05 December 2007 17:56 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 1IzyUD-00059I-IP; Wed, 05 Dec 2007 12:56:41 -0500
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1IzyUC-0004v9-9O for ltru-confirm+ok@megatron.ietf.org; Wed, 05 Dec 2007 12:56:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzyUB-0004qt-R3 for ltru@lists.ietf.org; Wed, 05 Dec 2007 12:56:39 -0500
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IzyUB-0002KK-64 for ltru@lists.ietf.org; Wed, 05 Dec 2007 12:56:39 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP id 327492BC28; Thu, 6 Dec 2007 02:56:38 +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 wuIxgnEbyAeF; Thu, 6 Dec 2007 02:56:38 +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 014462BC1E; Thu, 6 Dec 2007 02:56:37 +0900 (JST)
Message-ID: <4756E651.5010804@w3.org>
Date: Thu, 06 Dec 2007 02:56:33 +0900
From: Felix Sasaki <fsasaki@w3.org>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Peter Constable <petercon@microsoft.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> <20071205033042.GA10807@mercury.ccil.org> <30b660a20712041936w4a472416ibdbeeda192629c9e@mail.gmail.com> <30b660a20712041949k4cb44ed1m9065459707a2872d@mail.gmail.com> <DDB6DE6E9D27DD478AE6D1BBBB83579561E4CB3EF3@NA-EXMSG-C117.redmond.corp.microsoft.com>
In-Reply-To: <DDB6DE6E9D27DD478AE6D1BBBB83579561E4CB3EF3@NA-EXMSG-C117.redmond.corp.microsoft.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: "ltru@lists.ietf.org" <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

Peter Constable wrote:
>
> I think #3 would be more than just slightly sub-optimal. Many people 
> would look just at the statement of the ABNF and go away and do things 
> on that basis. The statement of the ABNF should somehow indicate 
> clearly that extlang is DEAD, never to be resurrected.
>
>  
>
> We need to be clear about the decision we’re making: we are deciding 
> to abandon extlang **permanently**. Removing extlang from the ABNF 
> will leave something that is more-certainly stable in that particular 
> regard. Of course, it doesn’t make the ABNF as a whole stable
>

I went through the draft looking for "stabl", and found it only in 
relation to validity (including the registry in general) and 
grandfathered sub tags. I found nothing about the ABNF. Secion 8 of RFC 
4646 says:

"... in no case is the syntax more permissive and processors based on 
the ABNF and other provisions of RFC 3066 (such as those described in 
[XMLSchema]) will be able to process the tags described by this document."

I think it would be very helpful (again esp. for outreach to other 
technologies) to have a statement in the main text about the stability 
and backwards compatibility of the ABNF. Of course one cannot predict 
the future of the ABNF, but expressing the intention might help already.

Felix



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