Re: [Ltru] Re: Is 639-3 bogus ?
Martin Duerst <duerst@it.aoyama.ac.jp> Wed, 11 October 2006 10:41 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXbWw-0003px-4K; Wed, 11 Oct 2006 06:41:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXbWt-0003lr-H8 for ltru@lists.ietf.org; Wed, 11 Oct 2006 06:41:39 -0400
Received: from scmailgw1.scop.aoyama.ac.jp ([133.2.251.194]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXbWp-0001Xq-KG for ltru@lists.ietf.org; Wed, 11 Oct 2006 06:41:39 -0400
Received: from scmse2.scbb.aoyama.ac.jp (scmse2 [133.2.253.17]) by scmailgw1.scop.aoyama.ac.jp (secret/secret) with SMTP id k9BAfYf4018393 for <ltru@lists.ietf.org>; Wed, 11 Oct 2006 19:41:34 +0900 (JST)
Received: from (133.2.206.133) by scmse2.scbb.aoyama.ac.jp via smtp id 1df5_10733628_5915_11db_820f_0014221f2a2d; Wed, 11 Oct 2006 19:41:33 +0900
X-AuthUser: duerst@it.aoyama.ac.jp
Received: from Tanzawa.it.aoyama.ac.jp ([133.2.210.1]:35844) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S3434A> for <ltru@lists.ietf.org> from <duerst@it.aoyama.ac.jp>; Wed, 11 Oct 2006 19:41:21 +0900
Message-Id: <6.0.0.20.2.20061011193946.075c9ec0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Version 6J
Date: Wed, 11 Oct 2006 19:41:17 +0900
To: Frank Ellermann <nobody@xyzzy.claranet.de>, ltru@lists.ietf.org
From: Martin Duerst <duerst@it.aoyama.ac.jp>
Subject: Re: [Ltru] Re: Is 639-3 bogus ?
In-Reply-To: <452C69E9.58B2@xyzzy.claranet.de>
References: <452B995B.92F@xyzzy.claranet.de> <F8ACB1B494D9734783AAB114D0CE68FE0B1B1999@RED-MSG-52.redmond.corp.microsoft.com> <452BCBE9.56D0@xyzzy.claranet.de> <F8ACB1B494D9734783AAB114D0CE68FE0B1B1A82@RED-MSG-52.redmond.corp.microsoft.com> <452BF0C1.731E@xyzzy.claranet.de> <F8ACB1B494D9734783AAB114D0CE68FE0B1B1AED@RED-MSG-52.redmond.corp.microsoft.com> <452C17BF.50A8@xyzzy.claranet.de> <F8ACB1B494D9734783AAB114D0CE68FE0B1B1C29@RED-MSG-52.redmond.corp.microsoft.com> <452C69E9.58B2@xyzzy.claranet.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
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>
Errors-To: ltru-bounces@ietf.org
I think adding only the 'interesting' information, in the Description or Comment field, would be a much more unobtrusive change to which I could agree (although still not thrilled). Reagrds, Martin. At 12:50 06/10/11, Frank Ellermann wrote: >Peter Constable wrote: >> "That's the job of a comment or description," you said. >> It's still not clear to me if you had a comment to make wrt >> John's proposal or not. > >The "interesting" types A, C, E, H, and S (what's H ?) could >be added to the description, e.g. > >Subtag: xzh >Description: Zhang-Zhung (A) > >Or preserved as a comment: > >Subtag: xzh >Description: Zhang-Zhung >Comment: Ancient > >There are only 617 entries with "interesting" types, anything >else is L (living). The scopes could be handled in the same >way, all 56 M are L, with that we would get at most one marker >per description or comment for now: A, C, E, H, S, or M. > >If later one of the Ms gets type E adding (M,E) to a description >(or saying Macrolanguage, Extinct in a comment) is no problem. > >Changing the 4646 syntax adding a completely new field however >is IMNSHO a very bad idea. We more or less promised that that >won't happen. #-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University #-#-# http://www.sw.it.aoyama.ac.jp mailto:duerst@it.aoyama.ac.jp _______________________________________________ Ltru mailing list Ltru@ietf.org https://www1.ietf.org/mailman/listinfo/ltru
- [Ltru] Proposal: include new "Language-Type:" fie… John Cowan
- Re: [Ltru] Proposal: include new "Language-Type:"… Addison Phillips
- Re: [Ltru] Proposal: include new "Language-Type:"… Mark Davis
- Re: [Ltru] Proposal: include new "Language-Type:"… John Cowan
- Re: [Ltru] Proposal: include new "Language-Type:"… Randy Presuhn
- RE: [Ltru] Proposal: include new "Language-Type:"… McDonald, Ira
- RE: [Ltru] Proposal: include new "Language-Type:"… Peter Constable
- [Ltru] Re: Proposal: include new "Language-Type:"… Doug Ewell
- RE: [Ltru] Re: Proposal: include new "Language-Ty… Kent Karlsson
- RE: [Ltru] Re: Proposal: include new "Language-Ty… Debbie Garside
- Re: [Ltru] Re: Proposal: include new "Language-Ty… John Cowan
- RE: [Ltru] Re: Proposal: include new "Language-Ty… Peter Constable
- [Ltru] Re: Proposal: include new "Language-Type:"… Doug Ewell
- Re: [Ltru] Re: Proposal: include new "Language-Ty… Addison Phillips
- [Ltru] Re: Proposal: include new "Language-Type:"… Frank Ellermann
- [Ltru] Re: Proposal: include new "Language-Type:"… Stephane Bortzmeyer
- Re: [Ltru] Re: Proposal: include new "Language-Ty… Mark Davis
- [Ltru] Re: Proposal: include new "Language-Type:"… Stephane Bortzmeyer
- Re: [Ltru] Re: Proposal: include new "Language-Ty… Marion Gunn
- [Ltru] Re: Proposal: include new "Language-Type:"… Stephane Bortzmeyer
- Re: [Ltru] Re: Proposal: include new "Language-Ty… John Cowan
- RE: [Ltru] Re: Proposal: include new "Language-Ty… McDonald, Ira
- Re: [Ltru] Re: Proposal: include new "Language-Ty… Addison Phillips
- Re: [Ltru] Re: Proposal: include new "Language-Ty… John Cowan
- RE: [Ltru] Re: Proposal: include new "Language-Ty… Peter Constable
- [Ltru] Re: Proposal: include new "Language-Type:"… Doug Ewell
- [Ltru] Re: Proposal: include new "Language-Type:"… Doug Ewell
- Re: [Ltru] Re: Proposal: include new "Language-Ty… Marion Gunn
- [Ltru] Is 639-3 bogus ? (was: Proposal: include n… Frank Ellermann
- RE: [Ltru] Is 639-3 bogus ? (was: Proposal: inclu… Peter Constable
- Re: [Ltru] Is 639-3 bogus ? (was: Proposal: inclu… Addison Phillips
- [Ltru] Re: Is 639-3 bogus ? Frank Ellermann
- Re: [Ltru] Is 639-3 bogus ? (was: Proposal: inclu… John Cowan
- Re: [Ltru] Re: Is 639-3 bogus ? John Cowan
- RE: [Ltru] Is 639-3 bogus ? (was: Proposal: inclu… Peter Constable
- RE: [Ltru] Re: Is 639-3 bogus ? Peter Constable
- [Ltru] Re: Is 639-3 bogus ? Frank Ellermann
- [Ltru] Re: Is 639-3 bogus ? Frank Ellermann
- Re: [Ltru] Is 639-3 bogus ? Addison Phillips
- RE: [Ltru] Re: Is 639-3 bogus ? Peter Constable
- RE: [Ltru] Is 639-3 bogus ? Peter Constable
- [Ltru] Re: Is 639-3 bogus ? Frank Ellermann
- Re: [Ltru] Re: Is 639-3 bogus ? John Cowan
- RE: [Ltru] Re: Is 639-3 bogus ? Peter Constable
- RE: [Ltru] Re: Is 639-3 bogus ? Peter Constable
- [Ltru] Re: Is 639-3 bogus ? Frank Ellermann
- Re: [Ltru] Re: Is 639-3 bogus ? Addison Phillips
- [Ltru] Re: Is 639-3 bogus ? Frank Ellermann
- Re: [Ltru] Is 639-3 bogus ? John Cowan
- RE: [Ltru] Re: Is 639-3 bogus ? Peter Constable
- Re: [Ltru] Re: Is 639-3 bogus ? Martin Duerst
- Re: [Ltru] Re: Is 639-3 bogus ? Martin Duerst
- Re: [Ltru] Is 639-3 bogus ? John Cowan
- Re: [Ltru] Is 639-3 bogus ? Addison Phillips
- RE: [Ltru] Re: Is 639-3 bogus ? Peter Constable