Re: [Ltru] rechartering to handle 639-6

"Debbie Garside" <> Tue, 14 July 2009 12:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 45D873A699C for <>; Tue, 14 Jul 2009 05:03:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.656
X-Spam-Status: No, score=-1.656 tagged_above=-999 required=5 tests=[AWL=-0.916, BAYES_20=-0.74]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id BFqLzRc70iqM for <>; Tue, 14 Jul 2009 05:03:00 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 06C703A6822 for <>; Tue, 14 Jul 2009 05:02:59 -0700 (PDT)
Received: from ([]) by ( []) (MDaemon PRO v9.6.6) with ESMTP id md50009627843.msg for <>; Tue, 14 Jul 2009 12:11:39 +0100
X-Spam-Processed:, Tue, 14 Jul 2009 12:11:39 +0100 (not processed: message from trusted or authenticated source)
Received: from Vickynew ([]) by with MailEnable ESMTP; Tue, 14 Jul 2009 11:51:34 +0100
From: "Debbie Garside" <>
To: "'Randy Presuhn'" <>, "'LTRU Working Group'" <>
References: <> <000801ca03e0$6a22bea0$6801a8c0@oemcomputer>
Date: Tue, 14 Jul 2009 11:52:25 +0100
Message-ID: <3e0701ca0471$2cbf4ab0$0300a8c0@Vickynew>
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1250"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <000801ca03e0$6a22bea0$6801a8c0@oemcomputer>
thread-index: AcoD4bQ+D/G5PZFDQCmTpi1sjgPW9AAi4njw
X-MDAV-Processed:, Tue, 14 Jul 2009 12:11:39 +0100
Subject: Re: [Ltru] rechartering to handle 639-6
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 14 Jul 2009 12:40:58 -0000

Whilst I can see that the process for including ISO 639-3 and updating
RFC4646 has been long and arduous and people are pretty tired, I believe
there will be a need for inclusion of ISO 639-6 data at some point in the
future - particularly when end users request a language tag on
IETF-Languages that is facilitated within the ISO 639-6 code once published.
This begs the question, who is ultimately going to make the decision to
ignore an ISO 639 standard?

The ISO 639-6 data is hierarchical in nature, goes to a level of granularity
that will facilitate virtually any requirement and also differentiates
between written and spoken language variations - something that will be
extremely useful for metadata registries within archive industries as well
as tagging for the visually impaired, deaf and hard of hearing.

That said, I don't believe now is the correct time to re-charter for the
purposes of including ISO 639-6 data. I don't think I am ready for this - I
may be in 6-12 months. 

I do, however, think it would be a good idea to keep this list open for
general discussions and if this proves the case I will inform the list as
and when I consider ISO 639-6 data sufficiently ready for incorporation.
Whether you decide to re-charter at that point (or at any other time) is up
to you.

Best regards

Debbie Garside
Editor ISO FDIS 639-6

-----Original Message-----
From: [] On Behalf Of
Randy Presuhn
Sent: 13 July 2009 18:36
To: LTRU Working Group
Subject: Re: [Ltru] rechartering to handle 639-6

Hi -

As a technical contributor...

I, too, oppose re-chartering ltru at this time.
The additions made by the documents recently approved
take us well past the point of diminishing returns
in terms of language coverage.

What that might convince me that re-chartering was needed
would be the appearance large quantities of data in large
numbers of languages in use by substantial speech communities
not covered by the recent updates, and not adequately handled
by the registration procedures.  I don't think that's going to
happen anytime in the foreseeable future.


Ltru mailing list

Internal Virus Database is out-of-date.
Checked by AVG. 
Version: 7.5.560 / Virus Database: 270.12.26/2116 - Release Date: 15/05/2009

Internal Virus Database is out-of-date.
Checked by AVG. 
Version: 7.5.560 / Virus Database: 270.12.26/2116 - Release Date: 15/05/2009