Re: [Ltru] Action items on draft-initial?

"Mark Davis" <mark.davis@icu-project.org> Tue, 26 July 2005 18:42 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DxUNT-0000Me-Th; Tue, 26 Jul 2005 14:42:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DxUNS-0000KZ-IT for ltru@megatron.ietf.org; Tue, 26 Jul 2005 14:42:06 -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 OAA13748 for <ltru@ietf.org>; Tue, 26 Jul 2005 14:42:05 -0400 (EDT)
Received: from icu-project.org ([66.160.189.149]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1DxUsY-0006NC-5t for ltru@ietf.org; Tue, 26 Jul 2005 15:14:15 -0400
Received: from markdavis ([24.23.194.196]) by icu-project.org for <ltru@ietf.org>; Tue, 26 Jul 2005 11:35:27 -0700
Message-ID: <03cc01c59211$b55cbbe0$666e3009@sanjose.ibm.com>
From: Mark Davis <mark.davis@icu-project.org>
To: Addison Phillips <addison.phillips@quest.com>, Randy Presuhn <randy_presuhn@mindspring.com>, LTRU Working Group <ltru@ietf.org>
References: <634978A7DF025A40BFEF33EB191E13BC0C3F93CF@irvmbxw01.quest.com>
Subject: Re: [Ltru] Action items on draft-initial?
Date: Tue, 26 Jul 2005 11:42:00 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1506
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id OAA13748
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

That's what I was saying. We don't need 'normative closure'.

Suppose standard A makes a normative reference to standard B, and B makes a
normative reference to C. It is unnecessary (and counterproductive) for A to
make a normative reference to C because of this. That is, it would only be
necessary for A to make a normative reference to C if it needed to
*independent of the requirements of B*.

‎Mark

----- Original Message ----- 
From: "Addison Phillips" <addison.phillips@quest.com>
To: "Randy Presuhn" <randy_presuhn@mindspring.com>; "LTRU Working Group"
<ltru@ietf.org>
Sent: Tuesday, July 26, 2005 11:35
Subject: RE: [Ltru] Action items on draft-initial?


>> What about the normative/informative issue?  I don't remember any
>> agreement as to whether the source standards whose code elements were
>> used in the initial registry should be normative, and as I said, I
>> would rather leave that judgment to others.
>...
>
>I believe the only normative reference in the initial registry draft should
>be the reference to the registry draft, since the latter is the only one of
>the references that is required to "implement" the initial registry.

It really doesn't matter ultimately.

Draft-registry does normatively reference the ISO standards as normative
sources for subtag values.

The instructions in Section 2 of draft-initial refer to the ISO standards
explicitly. The information taken from these standards by draft-initial is
normative. Thus it would be reasonable to put a normative reference to the
ISO standards into draft-initial. But since it doesn't really make any
difference the resulting document. We can make (keep?) the references as
informative and achieve identical results.

Addison

Addison P. Phillips
Globalization Architect, Quest Software
Chair, W3C Internationalization Core Working Group

Internationalization is not a feature.
It is an architecture.




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




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