Re: [Ltru] rechartering to handle 639-6 (was FW: Anomaly inupcomingregistry)

CE Whitehead <cewcathar@hotmail.com> Wed, 15 July 2009 22:50 UTC

Return-Path: <cewcathar@hotmail.com>
X-Original-To: ltru@core3.amsl.com
Delivered-To: ltru@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 31AE83A68CD for <ltru@core3.amsl.com>; Wed, 15 Jul 2009 15:50:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.602
X-Spam-Level:
X-Spam-Status: No, score=-3.602 tagged_above=-999 required=5 tests=[AWL=0.996, BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1FcmzRvw3wNZ for <ltru@core3.amsl.com>; Wed, 15 Jul 2009 15:50:08 -0700 (PDT)
Received: from blu0-omc3-s19.blu0.hotmail.com (blu0-omc3-s19.blu0.hotmail.com [65.55.116.94]) by core3.amsl.com (Postfix) with ESMTP id 8A4D428C139 for <ltru@ietf.org>; Wed, 15 Jul 2009 15:48:43 -0700 (PDT)
Received: from BLU109-W8 ([65.55.116.72]) by blu0-omc3-s19.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 15 Jul 2009 15:43:53 -0700
Message-ID: <BLU109-W89100B76ED0A33824F058B3200@phx.gbl>
Content-Type: multipart/alternative; boundary="_06b7b5cc-c2a4-4287-81b0-d4d2f5e8d103_"
X-Originating-IP: [168.12.253.82]
From: CE Whitehead <cewcathar@hotmail.com>
To: <ltru@ietf.org>
Date: Wed, 15 Jul 2009 18:43:53 -0400
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 15 Jul 2009 22:43:53.0616 (UTC) FILETIME=[BAD75900:01CA059D]
Subject: Re: [Ltru] rechartering to handle 639-6 (was FW: Anomaly inupcomingregistry)
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jul 2009 22:50:09 -0000

Hi. 


I tend to agree with Mark Davis that the structure of tags that we have enables parsing when a variant is not known.  But I like what Peter and Debbie have worked out:  

From: "Debbie Garside" <debbie at ictmarketing.co.uk> 

Date: Wed, 15 Jul 2009 21:51:03 +0100 
>Peter wrote:

>> That might not be unreasonable. Of course, we wouldn't need a
>> change in BCP 47 to effect that; it might be sufficient just
>> to have a working procedure within ietf-languages that, if a
>> variant registration comes along, then we always look into
> the possibility of registering the 639-6 ID, adapted as
>> needed. The most important reason to revise BCP 47 would be
>> to formalize requirements on how the ID should be adapted
>> (e.g. requiring "6" + alpha4 -- or whatever).

> Exactly! :-)

> Debbie

 

My personal feeling is that the geographic codes are generally well-suited for handling regional variation -- so we should definitely only take regional variants of languages that have ISO 639-6 codes on a case-by-case basis because I cannot see a long list of subtags with all this overlapping.
 
I am not familiar with ISO 639-6 but appreciate Debbie's list of English dialects (I need to go over these sometime). 
 
How is it decided in ISO 639-6 what is a language and what is a dialect???  Are there any rules since apparently ISO 639-6 deals more with dialects?
 
Also, will adopting the ISO 639-6 code elements mean deprecating a number of codes and many variant subtags (such as "Valencian")???  Or is that still up for discussion??

 
Thanks.
 
--C. E. Whitehead
cewcathar@hotmail.com 
 
 


From: "Debbie Garside" <debbie at ictmarketing.co.uk> 
Date: Wed, 15 Jul 2009 08:10:31 +0100 
> Doug wrote:

>> I think there are still some basic concepts to be worked out
>> since that post 2½ years ago.  For example, John Cowan has
>> since suggested using 5-character variant subtags starting
>> with "6" to hold ISO 639-6 code elements, instead of using
>> the 4-letter language subtags reserved for
>> (shhhh) this purpose.  That wasn't mentioned in the November
>> 2006 post, but it's something we would have to decide upon.

> Actually Peter constable suggested 5 characters some 6/7 years ago when I
> first joined the list.

> I really don't  have the time at present to enter into in-depth discussions
> on the inclusion/benefits/problems of incorporating ISO 639-6 especially as
> it would appear to be an uphill battle.  I would rather wait until the
> standard is published and somebody comes along and states their need.

> Best regards

> Debbie