IETF Logo Mail Archive

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

Peter Constable <petercon@microsoft.com> Wed, 05 December 2007 17:59 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 1IzyX9-000838-3E; Wed, 05 Dec 2007 12:59:43 -0500
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1IzyX7-00082z-UT for ltru-confirm+ok@megatron.ietf.org; Wed, 05 Dec 2007 12:59:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzyX7-00082q-Kp for ltru@lists.ietf.org; Wed, 05 Dec 2007 12:59:41 -0500
Received: from smtp.microsoft.com ([131.107.115.212]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IzyX7-0002bh-BR for ltru@lists.ietf.org; Wed, 05 Dec 2007 12:59:41 -0500
Received: from TK5-EXHUB-C102.redmond.corp.microsoft.com (157.54.70.72) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.1.222.3; Wed, 5 Dec 2007 09:59:02 -0800
Received: from NA-EXMSG-C117.redmond.corp.microsoft.com ([157.54.62.44]) by TK5-EXHUB-C102.redmond.corp.microsoft.com ([157.54.70.72]) with mapi; Wed, 5 Dec 2007 09:59:39 -0800
From: Peter Constable <petercon@microsoft.com>
To: "ltru@lists.ietf.org" <ltru@lists.ietf.org>
Date: Wed, 05 Dec 2007 09:59:32 -0800
Subject: RE: [Ltru] Re: Remove extlang from ABNF?
Thread-Topic: [Ltru] Re: Remove extlang from ABNF?
Thread-Index: Acg3ZxEJbhfwWp77T8iNdl5plZ6lSwAAOwWg
Message-ID: <DDB6DE6E9D27DD478AE6D1BBBB83579561E4CB3F39@NA-EXMSG-C117.redmond.corp.microsoft.com>
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> <4756E463.9070809@w3.org>
In-Reply-To: <4756E463.9070809@w3.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-Spam-Score: -8.0 (--------)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc:
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>
Content-Type: multipart/mixed; boundary="===============1132935470=="
Errors-To: ltru-bounces@ietf.org

> From: Felix Sasaki [mailto:fsasaki@w3.org]


> 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".

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.


Peter

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

v2.23.0 | Report a Bug | By Email