Re: Anomaly in upcoming registry
ISO639-3@sil.org Mon, 29 June 2009 17:03 UTC
Return-Path: <Joan_Spanne@sil.org>
X-Original-To: ietf-languages@alvestrand.no
Delivered-To: ietf-languages@alvestrand.no
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 489B439E24F for <ietf-languages@alvestrand.no>; Mon, 29 Jun 2009 19:03:32 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
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 1FXVoWFdxxfb for <ietf-languages@alvestrand.no>; Mon, 29 Jun 2009 19:03:28 +0200 (CEST)
X-Greylist: delayed 00:44:10 by SQLgrey-1.6.8
Received: from pechora5.lax.icann.org (pechora5.icann.org [208.77.188.40]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 32BDE39E243 for <ietf-languages@alvestrand.no>; Mon, 29 Jun 2009 19:03:28 +0200 (CEST)
Received: from smtp1.wsfo.org (smtp1.wsfo.org [208.145.81.51]) by pechora5.lax.icann.org (8.13.8/8.13.8) with ESMTP id n5TGIu3D011117 for <ietf-languages@iana.org>; Mon, 29 Jun 2009 09:19:16 -0700
Received: from dfwcom.sil.org (philippi.dallas.sil.org [172.20.1.21]) by smtp1.wsfo.org (8.13.8/8.13.8) with ESMTP id n5TG0ARj017274 for <ietf-languages@iana.org>; Mon, 29 Jun 2009 12:00:10 -0400
In-Reply-To: <CFD23A71C2E244B881C35DB95451EC03@DGBP7M81>
From: ISO639-3@sil.org
To: ietf-languages@iana.org
Subject: Re: Anomaly in upcoming registry
MIME-Version: 1.0
X-KeepSent: AAB71499:FE636271-862575E4:0055AD5D; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006
Message-ID: <OFAAB71499.FE636271-ON862575E4.0055AD5D-862575E4.00581C39@notes.sil.org>
Sender: Joan_Spanne@sil.org
Date: Mon, 29 Jun 2009 10:59:23 -0500
X-MIMETrack: Serialize by Router on DFWCOM/Servers/WCT(Release 8.0.1|February 07, 2008) at 06/29/2009 10:59:26 AM, Serialize complete at 06/29/2009 10:59:26 AM
Content-Type: multipart/alternative; boundary="=_alternative 00581C31862575E4_="
X-Scanned-By: MIMEDefang 2.62 on 172.22.65.23
X-Greylist: Delayed for 00:18:36 by milter-greylist-4.0 (pechora5.lax.icann.org [208.77.188.40]); Mon, 29 Jun 2009 09:19:16 -0700 (PDT)
X-BeenThere: ietf-languages@alvestrand.no
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Language tag discussions <ietf-languages.alvestrand.no>
List-Unsubscribe: <http://www.alvestrand.no/mailman/listinfo/ietf-languages>, <mailto:ietf-languages-request@alvestrand.no?subject=unsubscribe>
List-Archive: <http://www.alvestrand.no/pipermail/ietf-languages>
List-Post: <mailto:ietf-languages@alvestrand.no>
List-Help: <mailto:ietf-languages-request@alvestrand.no?subject=help>
List-Subscribe: <http://www.alvestrand.no/mailman/listinfo/ietf-languages>, <mailto:ietf-languages-request@alvestrand.no?subject=subscribe>
X-List-Received-Date: Mon, 29 Jun 2009 17:03:32 -0000
Hello All, I do not think that there is anything requiring correction. There are other instances of macrolanguages in ISO 639-3 that do not exist in Part 2 (much less, Part 1). See [luy] and [kln]. The deprecation of [sh] in Part 1, and the retirement of [hbs] from the predecesor of Part 2 with the split into three individual languages were actions taken before the notion of "macrolanguage" was in existence in the 639 standards group. The decision to include [hbs] as a macrolanguage in Part 3 was a separate decision, taken in 2005 and reiterated in 2007 with the adoption of ISO 639-3. Best regards, Joan Spanne ISO 639-3/RA SIL International 7500 W Camp Wisdom Rd Dallas, TX 75236 ISO639-3@sil.org "Doug Ewell" <doug@ewellic.org> Sent by: ietf-languages-bounces@alvestrand.no 2009-06-29 08:04 AM To <ietf-languages@iana.org> cc Subject Re: Anomaly in upcoming registry Randy Presuhn <randy underscore presuhn at mindspring dot com> wrote: >> ... It certainly isn't patently obvious to me that this is a bug in >> the draft-4645bis Registry that needs to be fixed. > > I think no one is suggesting that anything be done to draft-4645bis. I > think re-opening 4645bis to make a change of this nature would be > inappropriate. No, I agree that Mark was not calling to change anything in draft-4645bis, but rather in the "draft-4645bis Registry" -- the Registry to be supplied to IANA by draft-4645bis, whose method of construction is described in draft-4645bis. My position is that the change Mark suggests may not be appropriate, and is certainly not a <span lang="en-US">slam dunk</span>. It depends on our interpretation of draft-4646bis and any priorities it does or doesn't give to ISO 639-3 over other parts of ISO 639, and it depends on whether the relevant RA or JAC decides to correct the inconsistency in 639 by either (a) reviving "sh" in 639-1 and adding "hbs" to 639-2, or (b) withdrawing "hbs" from 639-3. I don't see why the philosophical discussion necessarily must wait until the new Registry is in force, but if others want to wait, that's fine with me. -- Doug Ewell * Thornton, Colorado, USA * RFC 4645 * UTN #14 http://www.ewellic.org http://www1.ietf.org/html.charters/ltru-charter.html http://www.alvestrand.no/mailman/listinfo/ietf-languages ˆ _______________________________________________ Ietf-languages mailing list Ietf-languages@alvestrand.no http://www.alvestrand.no/mailman/listinfo/ietf-languages
- Re: Anomaly in upcoming registry Doug Ewell
- Anomaly in upcoming registry Mark Davis ⌛
- Re: Anomaly in upcoming registry Doug Ewell
- Re: Anomaly in upcoming registry Mark Davis ⌛
- Re: Anomaly in upcoming registry Randy Presuhn
- Re: Anomaly in upcoming registry Mark Davis ⌛
- Re: Anomaly in upcoming registry Doug Ewell
- RE: Anomaly in upcoming registry Phillips, Addison
- Re: Anomaly in upcoming registry Mark Davis ⌛
- Re: Anomaly in upcoming registry ISO639-3
- Re: Anomaly in upcoming registry Mark Davis ⌛
- Re: Anomaly in upcoming registry John Cowan
- Re: Anomaly in upcoming registry Mark Davis ⌛
- Re: Anomaly in upcoming registry Caoimhin O Donnaile
- Re: Anomaly in upcoming registry Doug Ewell
- RE: Anomaly in upcoming registry Lang Gérard
- Re: Anomaly in upcoming registry Doug Ewell
- RE: Anomaly in upcoming registry Lang Gérard
- Re: Anomaly in upcoming registry Doug Ewell
- Re: Anomaly in upcoming registry Rebecca S Guenther
- Re: Anomaly in upcoming registry Mark Davis ⌛
- Re: Anomaly in upcoming registry Doug Ewell
- Re: Anomaly in upcoming registry Mark Davis ⌛
- Re: Anomaly in upcoming registry Randy Presuhn
- Re: Anomaly in upcoming registry Randy Presuhn
- Re: Anomaly in upcoming registry Doug Ewell
- Re: Anomaly in upcoming registry Doug Ewell
- RE: Anomaly in upcoming registry Peter Constable
- Re: Anomaly in upcoming registry Roozbeh Pournader
- Re: Anomaly in upcoming registry Mark Davis ⌛
- Re: Anomaly in upcoming registry Gerard Meijssen
- Re: Anomaly in upcoming registry Doug Ewell
- RE: Anomaly in upcoming registry Peter Constable
- RE: Anomaly in upcoming registry Peter Constable
- Re: Anomaly in upcoming registry Mark Davis ⌛
- Re: Anomaly in upcoming registry Doug Ewell
- Re: Anomaly in upcoming registry Randy Presuhn
- Re: Anomaly in upcoming registry Doug Ewell
- Re: Anomaly in upcoming registry Gerard Meijssen
- Re: Anomaly in upcoming registry Randy Presuhn
- Re: Anomaly in upcoming registry John Cowan