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;
	 Sun, 03 Apr 2005 05:24:18 +0200
X-Sieve: CMU Sieve 2.2
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 9BBB861B47
	for <harald@alvestrand.no>; Sun,  3 Apr 2005 05:24:18 +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 01472-03 for <harald@alvestrand.no>;
 Sun,  3 Apr 2005 05:24:15 +0200 (CEST)
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 8F2A861B03
	for <harald@alvestrand.no>; Sun,  3 Apr 2005 05:24:15 +0200 (CEST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHvhl-0006bx-3W; Sat, 02 Apr 2005 22:23:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DHvhk-0006bs-Ef
	for ltru@megatron.ietf.org; Sat, 02 Apr 2005 22:23:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18584
	for <ltru@ietf.org>; Sat, 2 Apr 2005 22:23:13 -0500 (EST)
Received: from [63.247.76.194] (helo=montage.altserver.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHvpO-00009c-Bq
	for ltru@ietf.org; Sat, 02 Apr 2005 22:31:11 -0500
Received: from lns-p19-1-idf-82-251-95-81.adsl.proxad.net ([82.251.95.81]
	helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44)
	id 1DHvhh-0000Nx-T0; Sat, 02 Apr 2005 19:23:14 -0800
Message-Id: <6.1.2.0.2.20050403051351.02f51ac0@mail.jefsey.com>
X-Sender: jefsey+jefsey.com@mail.jefsey.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Sun, 03 Apr 2005 05:23:06 +0200
To: "Doug Ewell" <dewell@adelphia.net>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
Subject: Re: [Ltru] Re: Proposed changes to region subtags
In-Reply-To: <012501c537ed$77b5b0e0$030aa8c0@DEWELL>
References: <20050401205735.MVSI2135.mta2.adelphia.net@megatron.ietf.org>
	<00c401c53754$cdfe41e0$030aa8c0@DEWELL>
	<6.1.2.0.2.20050402114743.03713610@mail.jefsey.com>
	<011101c537c7$be722b60$030aa8c0@DEWELL>
	<6.1.2.0.2.20050403005935.03c05b90@mail.jefsey.com>
	<012501c537ed$77b5b0e0$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 - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: ltru@ietf.org
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 03:35 03/04/2005, Doug Ewell wrote:
>JFC (Jefsey) Morfin <jefsey at jefsey dot com> wrote:
>
> >> Code elements don't have an expiration date.  They're good forever,
> >> or until the MA withdraws or deprecates them.  Subtags are good
> >> forever, or until the language tagging mechanism is totally replaced.
> >
> > What makes their expiration date.
>
>Can you predict when those events will happen?  If not, does it make
>sense to reserve a field for it?

I do not plan to reserve a field but to add the year in the code element. 
But the approach we _consider_ is quite different and much more Internet like.

>Never mind; this is the structure for your draft, and you will design it
>in the way you think is best.

Yes. But the idea is not to design it differently from APMD for the 
XML/HTML/CLDR applications (t)hey know better what they want and did not 
document the CLDR specific needs. But to maintain the underlaying 
information available to every possible application format. Including the 
currently discussed format. Them being free to use it or not, the way they 
think the best.

> >> I don't know what you mean by "APMD."  A quick Web search led me to
> >> information on power management for laptops, which I'm sure is not
> >> what you meant.
> >
> > Addison Philips' and Mark Davis' Draft.
>
>Aha.
>
>Please write to me publicly, on the list, on issues related to the
>Working Group.

Sorry, privacy was not intended. I copy the list.
jfc


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