Return-Path: Received: from murder ([unix socket]) by eikenes.alvestrand.no (Cyrus v2.2.8-Mandrake-RPM-2.2.8-4.2.101mdk) with LMTPA; Sat, 16 Jul 2005 21:25:13 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 5BB2B61B05 for ; Sat, 16 Jul 2005 21:25:13 +0200 (CEST) Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09359-08 for ; Sat, 16 Jul 2005 21:25:09 +0200 (CEST) X-Greylist: domain auto-whitelisted by SQLgrey-1.4.8 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by eikenes.alvestrand.no (Postfix) with ESMTP id 11BCE61B03 for ; Sat, 16 Jul 2005 21:25:09 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtsHS-0008Rl-Gl; Sat, 16 Jul 2005 15:24:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtrCW-0006Iv-3X for ltru@megatron.ietf.org; Sat, 16 Jul 2005 14:15:48 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18839 for ; Sat, 16 Jul 2005 14:15:44 -0400 (EDT) Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dtpz7-00059P-PD for ltru@ietf.org; Sat, 16 Jul 2005 12:57:54 -0400 Received: from ver78-2-82-241-91-24.fbx.proxad.net ([82.241.91.24] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1DtpVu-0006nx-9B for ltru@ietf.org; Sat, 16 Jul 2005 09:27:42 -0700 Message-Id: <6.2.1.2.2.20050716140428.03aaeeb0@pop.online.fr> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Sat, 16 Jul 2005 14:05:53 +0200 To: ltru@ietf.org From: Jefsey Morfin Subject: Re: [Ltru] [psg.com #1067] Last call: clarification between language tags and locales Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - montage.altserver.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - online.fr X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 X-Mailman-Approved-At: Sat, 16 Jul 2005 15:24:57 -0400 Cc: X-BeenThere: ltru@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Language Tag Registry Update working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ltru-bounces@lists.ietf.org Errors-To: ltru-bounces@lists.ietf.org X-Virus-Scanned: amavisd-new at alvestrand.no OK, I will feed the troll ... On 04:23 16/07/2005, Randy Presuhn said: > > Proposed text - as insert for relation with IESG pending an IESG decision: > > > > "[Charter has explicitly said that langtags apply to HTML, XML, CLDR, etc. > > This WG has identified that this point of the Charter is to be requalified. > > In the case of CLDR, locales can certainly be described in using Langtags > > as many other language and country related objects and processes, such as > > publishing, reading, filtering, censoring, exchanging, communicating, > > classifying text, book, records, identifying expertise in a language, > > copyrights, etc. etc. However they also have the capacity to document non > > language related issues such as colors on a display, sound of a > > loudspeaker, process speed depending on a process pattern, default network > > addresses, etc.. They also can be partly patented to support patented > > processes. As such they may have to be identified in refering to patent > > references the "x-" escape sequence could support woud it not be limited to > > 8-alpha/num for retro-compatibility with the never used before patent > > referencing. The WG hesitates to documents langtags for the CLDR and wishes > > to exclude langtags considerations from its charter, reserving to locale > > compilers the decision to use langtags as a part of, or an equivalent to, > > localtag or not. Should localtags be confirmed as directly belonging the > > Charter, a locale oriented "l-" final extension will be used where all the > > subsequent dashes would not be part of the Draft ABNF, in order to accept > > sequences of the form "-c-" included in some of the references to > include.]" >... > >As co-chair: >(1) For patent-related disclosure requirements, see >http://www.ietf.org/rfc/rfc3979.txt >(2) Specifying locales is clearly beyond our scope. Difficult to understand in which context these two quotes are made. They seem totally out of scope? >As a technical contributor, I think Jefsey's proposed addition would be >counterproductive. reducing rather than improving the document's >intellegibility. Consequently, I strongly oppose its inclusion. Your priviledge. There must be a clearly expressed consensus, one way or another. From what I understand you want to be able to use langtags to name locales, without expressing any consideration on their structure, nor permitting competitors to differentiate their propositions through the reference of their IPRs? This is at least what I understand after reading this many times. Difficult to get understand what you may oppose since I say the same but leaving the IESG to say otherwise. Thx to tell where I would be wrong reading you? An IPR lawyer suggests me: "he wants to keep CLDR in the loop, but does not want to see it discussed. If the target is to be able to say 'IANA langtag inside' there is a long long long way to go, all the more if there are any directly or indirectly claimed right through the locale". A civil right fighter says so bad things about all this, that I hesitate between quoting him and being expelled, and giving him the way to subscribe and to see him setting the WG afire. Not easy to just stay a network architect. But even then, look at what Vint Cerf just said .... http://news.yahoo.com/s/ap/20050715/ap_on_hi_te/internet_languages;_ylt=ArzU5bsfXU3xIjN3xHeQIE6s0NUE;_ylu=X3oDMTA3cjE0b2MwBHNlYwM3Mzg putting the blame on us because it does not work. jfc _______________________________________________ Ltru mailing list Ltru@lists.ietf.org https://www1.ietf.org/mailman/listinfo/ltru