Return-Path: <ltru-bounces@lists.ietf.org>
Received: from murder ([unix socket])
	 by eikenes.alvestrand.no (Cyrus v2.2.8-Mandrake-RPM-2.2.8-4.2.101mdk) with LMTPA;
	 Fri, 08 Jul 2005 20:15:59 +0200
X-Sieve: CMU Sieve 2.2
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id A0F1761B05
	for <harald@alvestrand.no>; Fri,  8 Jul 2005 20:15:59 +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 05649-06 for <harald@alvestrand.no>;
 Fri,  8 Jul 2005 20:15:56 +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 B4BE261B03
	for <harald@alvestrand.no>; Fri,  8 Jul 2005 20:15:54 +0200 (CEST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DqxND-0003W3-EX; Fri, 08 Jul 2005 14:14:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DqxNB-0003Vx-NB
	for ltru@megatron.ietf.org; Fri, 08 Jul 2005 14:14:49 -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 OAA02727
	for <ltru@ietf.org>; Fri, 8 Jul 2005 14:14:48 -0400 (EDT)
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dqxoc-0000Hv-1c
	for ltru@ietf.org; Fri, 08 Jul 2005 14:43:11 -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 1DqxN8-0001dJ-T4; Fri, 08 Jul 2005 11:14:47 -0700
Message-Id: <6.2.1.2.2.20050708193920.0498eeb0@mail.afrac.org>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2
Date: Fri, 08 Jul 2005 19:54:54 +0200
To: "Doug Ewell" <dewell@adelphia.net>,
	"LTRU Working Group" <ltru@ietf.org>
From: r&d afrac <rd@afrac.org>
Subject: Re: [Ltru] Re: status? last call?
In-Reply-To: <00f101c583ca$075a0660$030aa8c0@DEWELL>
References: <20050629114419.FFKU24938.mta8.adelphia.net@megatron.ietf.org>
	<009901c58382$89634a60$030aa8c0@DEWELL>
	<42CE2056.8070408@megared.net.mx>
	<00a701c5838a$21e66540$030aa8c0@DEWELL>
	<6.2.1.2.2.20050708130647.03e462a0@mail.afrac.org>
	<00f101c583ca$075a0660$030aa8c0@DEWELL>
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 - afrac.org
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
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
	<ltru.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>,
	<mailto:ltru-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@lists.ietf.org>
List-Help: <mailto:ltru-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>,
	<mailto:ltru-request@lists.ietf.org?subject=subscribe>
Sender: ltru-bounces@lists.ietf.org
Errors-To: ltru-bounces@lists.ietf.org
X-Virus-Scanned: amavisd-new at alvestrand.no

At 16:33 08/07/2005, Doug Ewell wrote:
>r&d afrac <rd at afrac dot org> wrote:
>
> >> The initial-registry draft refers the reader to the registry-
> >> structure draft for all details concerning the format and encoding
> >> conventions of the registry.  The registry-structure draft, in turn,
> >> does contain an informative reference to Unicode 4.1.0.
> >
> > This cannot be as this is not an ISO 639-4 accepted reference. Nothing
> > protects the IETF which is not an ISO nor a Unicode expert, from
> > conflict. As the Chair put it, ISO is ISO and IETF is IETF.
>
>I have no idea what this means.  Are you saying that the
>initial-registry draft needs to include an explicit reference to the
>Unicode Standard, instead of indirectly referencing it through the
>registry-structure draft?

No. I say directly or indirectly you cannot reference an third party. 
Unicode is a consortium of private interets, the same as W3C, etc. This WG 
is to deal with ISO 639, 3166 and 15924, plus UN M.49 (in a way I partly 
disagree with because the format is confusing). Outside of that no other 
code has been accepted: because no other maintainer has committed to stay 
compatible with these codes and her commitment accepted by the IETF.

>I don't see what ISO 639-4 has to do with any of this.

ISO 639-4 is the ISO document which commits on the consistency of ISO 639 
series, 15924 and 3166 series. ISO 639-4 is to describe the possible 
relations between these codes. The matter is debated and not made. It would 
be odd if IETF standardised relations between codes the authors of that 
codes would identify as wrong. This is why we must do the things in 
sequence. Our charter is to deal with ISO 639. The author of ISO 639-3 
being at the origin of all this effort, I undersnand that he insisted on 
ISO 639-3. I find other ISO 639-3 based formats more interesting 
networkwise, but all this is a question of technical experimentation and 
testing by users. I always marvel at people who invent best common practices.
jfc


_______________________________________________
Ltru mailing list
Ltru@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/ltru