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

Felix Sasaki <fsasaki@w3.org> Tue, 11 December 2007 12:32 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 1J24Hg-00053a-HQ; Tue, 11 Dec 2007 07:32:24 -0500
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1J24Hf-00053U-0A for ltru-confirm+ok@megatron.ietf.org; Tue, 11 Dec 2007 07:32:23 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J24He-00053M-LI for ltru@ietf.org; Tue, 11 Dec 2007 07:32:22 -0500
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J24Hd-0004Nh-Ai for ltru@ietf.org; Tue, 11 Dec 2007 07:32:22 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP id 4EF402BBF8; Tue, 11 Dec 2007 21:32:08 +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 ErVnga6VBeSG; Tue, 11 Dec 2007 21:32:08 +0900 (JST)
Received: from [127.0.0.1] (p5011-ipad402marunouchi.tokyo.ocn.ne.jp [222.146.117.11]) by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP id 18C3D2BBE6; Tue, 11 Dec 2007 21:32:08 +0900 (JST)
Message-ID: <475E8342.1080206@w3.org>
Date: Tue, 11 Dec 2007 21:32:02 +0900
From: Felix Sasaki <fsasaki@w3.org>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Martin Duerst <duerst@it.aoyama.ac.jp>
Subject: Re: [Ltru] Re: Remove extlang from ABNF?
References: <E1J01vI-0003cW-Rd@megatron.ietf.org> <019601c83818$b06c3070$6601a8c0@DGBP7M81> <DDB6DE6E9D27DD478AE6D1BBBB83579561E51429AA@NA-EXMSG-C117.redmond.corp.microsoft.com> <6.0.0.20.2.20071211163740.0a090850@localhost>
In-Reply-To: <6.0.0.20.2.20071211163740.0a090850@localhost>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: LTRU Working Group <ltru@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

Martin Duerst wrote:
> At 01:16 07/12/07, Peter Constable wrote:
>   
>> Content-Language: en-US
>> Content-Type: text/plain; charset="utf-8"
>>
>>     
>>> From: Doug Ewell [mailto:dewell@roadrunner.com]
>>>       
>>>>> 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".
>>>>>           
>>>> But this is a key: we are *not* dropping any features. We are
>>>>         
>>> dropping
>>>       
>>>> the possibility of a future feature. The change to the ABNF (whether
>>>> by removing the extlang subtag entirely or by renaming and/or
>>>> comments) is to clean it up so that implementers do not implement for
>>>> non-and-never-to-be-features.
>>>>         
>>> I think what Felix meant was not that we are dropping features, but
>>> that
>>> it may appear to the outside observer that we are dropping features.
>>>       
>> I understood that. But I think it's significant that we are *not* removing 
>> any features, and it seems to me that could be explained easily enough.
>>     
>
> [chairs hat OFF]
>
> It looks like this could be explained easily enough, but I'm quite
> sure that this won't be the case. XML, and XML Schema, are very
> strictly defined languages. Fortunately, we managed to get XML
> away from including a grammar for language tags in an early erratum/
> corrigendum. But if XML Schema has indeed used RFC 4646 for defining
> the syntactic range of language tags, then we should not remove
> some productions. 
This is a repetition, but maybe useful in this long thread.

The W3C i18n core Working Group asked the XML Schema Working Group to 
use the RFC 4646 syntactic range of language tags for XML Schema 1.1 
(datatypes), see
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3079#c2 (search for "here 
RFC 4646 grammar")
We assumed that the RFC 4646 ABNF will be stable, and since XML Schema 
1.0 (datatypes) uses the ABNF from RFC 3066
http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#language
it seems natural to propose for XML Schema 1..1 to have the RFC 4646 
ABNF for XML Schema 1.1.

Felix









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