RE: [Ltru] RE: ISO 639-2 decision: "mis"
Peter Constable <petercon@microsoft.com> Fri, 15 June 2007 22:33 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 1HzKMU-0001mR-V9; Fri, 15 Jun 2007 18:33:46 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1HzKMT-0001mM-UY for ltru-confirm+ok@megatron.ietf.org; Fri, 15 Jun 2007 18:33:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HzKMT-0001mE-Kz for ltru@ietf.org; Fri, 15 Jun 2007 18:33:45 -0400
Received: from mail2.microsoft.com ([131.107.115.215] helo=smtp.microsoft.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzKMT-0004M4-Bw for ltru@ietf.org; Fri, 15 Jun 2007 18:33:45 -0400
Received: from TK5-EXHUB-C101.redmond.corp.microsoft.com (157.54.70.76) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.0.700.0; Fri, 15 Jun 2007 15:32:30 -0700
Received: from NA-EXMSG-C117.redmond.corp.microsoft.com ([157.54.62.44]) by TK5-EXHUB-C101.redmond.corp.microsoft.com ([157.54.70.76]) with mapi; Fri, 15 Jun 2007 15:33:44 -0700
From: Peter Constable <petercon@microsoft.com>
To: LTRU Working Group <ltru@ietf.org>
Date: Fri, 15 Jun 2007 15:33:43 -0700
Subject: RE: [Ltru] RE: ISO 639-2 decision: "mis"
Thread-Topic: [Ltru] RE: ISO 639-2 decision: "mis"
Thread-Index: Acevl3QWNd6tBjvOQYy4cjmcVEK6UAAAn43w
Message-ID: <DDB6DE6E9D27DD478AE6D1BBBB8357955FB4CEC767@NA-EXMSG-C117.redmond.corp.microsoft.com>
References: <DDB6DE6E9D27DD478AE6D1BBBB8357955FB4CEC608@NA-EXMSG-C117.redmond.corp.microsoft.com><OF0F37EB59.81386F56-ON882572FB.0068B363-882572FB.006941AD@spe.sony.com><DDB6DE6E9D27DD478AE6D1BBBB8357955FB4CEC68A@NA-EXMSG-C117.redmond.corp.microsoft.com> <001401c7af92$89fb9200$6601a8c0@oemcomputer> <DDB6DE6E9D27DD478AE6D1BBBB8357955FB4CEC70B@NA-EXMSG-C117.redmond.corp.microsoft.com> <002e01c7af98$03683800$6601a8c0@oemcomputer>
In-Reply-To: <002e01c7af98$03683800$6601a8c0@oemcomputer>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
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
From: Randy Presuhn [mailto:randy_presuhn@mindspring.com] >> but that is part of the documented contract around 'mis' > > Which "documented contract"? I expect the ISO 639 RAs will be providing a usage note wrt 'mis' explaining that its extensional semantic must be defined in relation to an application context. This was one of the action items listed if the proposal to change the name were approved. I will follow up with the RAs on getting that done. >> -- and why users need to understand its shortcomings, so also why users >> would probably be warned against exporting data. > > This is making the case for using "MUST NOT" rather than "SHOULD NOT". IMO, this is in the same line as people using a tag like "en-Latn": we say "the script subtag SHOULD be omitted" in such cases, but not that they MUST NOT include it in such cases. We expect users to make informed choices; we're not going to police them on certain things they *could* do but that wouldn't be wise to do in general. >> The only issue here is the inherent instability and shortcomings of 'mis'. >> I don't see any abuse of BCP 47. There is nothing whatsoever like using >> "sw" to mean 'Swiss German'. > > Yes, it is in that permitting the tag to be used for languages for which tags > already exist is in direct contradiction to its description. The issue here is evaluating "languages for which tags already exist". You're assuming that every application of BCP 47 must determine that based on the complete inventory of the LSTR. I'm assuming that a higher-level protocol can restrict the contents of the LSTR it permits and that it can also determine the extension of 'mis' on the basis of its restricted set. I see these as two options we can permit; I don't see one of these excluded a priori. It's a choice we should discuss and probably clarify in documenting 'mis' (unless we decide to deprecate it). Peter _______________________________________________ Ltru mailing list Ltru@ietf.org https://www1.ietf.org/mailman/listinfo/ltru
- [Ltru] Fw: ISO 639-2 decision: "mis" Randy Presuhn
- Re: [Ltru] Fw: ISO 639-2 decision: "mis" Karen_Broome
- [Ltru] Re: ISO 639-2 decision: "mis" Addison Phillips
- [Ltru] Re: ISO 639-2 decision: "mis" Doug Ewell
- Re: [Ltru] Re: ISO 639-2 decision: "mis" Randy Presuhn
- [Ltru] RE: RE: ISO 639-2 decision: "mis" Peter Constable
- [Ltru] RE: ISO 639-2 decision: "mis" Debbie Garside
- Re: [Ltru] RE: ISO 639-2 decision: "mis" Randy Presuhn
- Re: [Ltru] RE: ISO 639-2 decision: "mis" GerardM
- Re: [Ltru] RE: ISO 639-2 decision: "mis" Randy Presuhn
- RE: [Ltru] RE: ISO 639-2 decision: "mis" Peter Constable
- RE: [Ltru] RE: ISO 639-2 decision: "mis" Peter Constable
- Re: [Ltru] RE: ISO 639-2 decision: "mis" Randy Presuhn
- Re: [Ltru] RE: ISO 639-2 decision: "mis" Addison Phillips
- Re: [Ltru] RE: ISO 639-2 decision: "mis" Randy Presuhn
- RE: [Ltru] RE: ISO 639-2 decision: "mis" Peter Constable
- RE: [Ltru] RE: ISO 639-2 decision: "mis" Karen_Broome
- RE: [Ltru] RE: ISO 639-2 decision: "mis" Peter Constable
- RE: [Ltru] RE: ISO 639-2 decision: "mis" Karen_Broome
- Re: [Ltru] RE: ISO 639-2 decision: "mis" Randy Presuhn
- RE: [Ltru] RE: ISO 639-2 decision: "mis" Peter Constable
- RE: [Ltru] RE: ISO 639-2 decision: "mis" Kent Karlsson
- Re: [Ltru] RE: ISO 639-2 decision: "mis" Randy Presuhn
- RE: [Ltru] RE: ISO 639-2 decision: "mis" Debbie Garside
- RE: [Ltru] RE: ISO 639-2 decision: "mis" Jukka K. Korpela
- RE: [Ltru] RE: ISO 639-2 decision: "mis" Peter Constable
- Re: [Ltru] RE: ISO 639-2 decision: "mis" Randy Presuhn
- RE: [Ltru] RE: ISO 639-2 decision: "mis" Peter Constable
- Re: [Ltru] RE: ISO 639-2 decision: "mis" Karen_Broome
- Re: [Ltru] RE: ISO 639-2 decision: "mis" Randy Presuhn
- Re: [Ltru] RE: ISO 639-2 decision: "mis" Mark Davis
- [Ltru] Re: ISO 639-2 decision: "mis" Doug Ewell
- [Ltru] Re: ISO 639-2 decision: "mis" Doug Ewell
- [Ltru] Re: ISO 639-2 decision: "mis" Doug Ewell
- [Ltru] Re: ISO 639-2 decision: "mis" Doug Ewell
- [Ltru] Re: Fw: ISO 639-2 decision: "mis" Frank Ellermann
- RE: [Ltru] RE: ISO 639-2 decision: "mis" Martin Duerst
- RE: [Ltru] RE: ISO 639-2 decision: "mis" Kent Karlsson
- [Ltru] RE: (iso639.2708) RE: ISO 639-2 decision: … Peter Constable
- [Ltru] Re: (iso639.2708) RE: ISO 639-2 decision: … Frank Ellermann
- [Ltru] Fwd: (iso639.2708) RE: ISO 639-2 decision:… Mark Davis
- [Ltru] RE: (iso639.2708) RE: ISO 639-2 decision: … Peter Constable
- [Ltru] Re: (iso639.2708) RE: ISO 639-2 decision: … Mark Davis
- Re: [Ltru] RE: (iso639.2708) RE: ISO 639-2 decisi… Mark Davis
- Re: [Ltru] RE: (iso639.2708) RE: ISO 639-2 decisi… John Cowan
- [Ltru] Re: (iso639.2708) RE: ISO 639-2 decision: … Frank Ellermann
- Re: [Ltru] RE: (iso639.2708) RE: ISO 639-2 decisi… Mark Davis
- Fwd: [Ltru] RE: (iso639.2708) RE: ISO 639-2 decis… Mark Davis
- RE: [Ltru] RE: (iso639.2708) RE: ISO 639-2 decisi… Peter Constable
- RE: [Ltru] RE: (iso639.2708) RE: ISO 639-2 decisi… Peter Constable
- RE: [Ltru] RE: (iso639.2708) RE: ISO 639-2 decisi… Martin Duerst
- [Ltru] RE: (iso639.2708) RE: ISO 639-2 decision: … Debbie Garside
- Re: (iso639.2732) RE: [Ltru] RE: RE: ISO 639-2 de… Keld Jørn Simonsen
- Re: [Ltru] RE: (iso639.2708) RE: ISO 639-2 decisi… Mark Davis
- [Ltru] Cross-posting Randy Presuhn
- Re: [Ltru] RE: (iso639.2708) RE: ISO 639-2 decisi… Martin Duerst