Message-Id: <6.1.2.0.2.20050322031307.03db5930@pop.online.fr>
Date: Tue, 22 Mar 2005 03:26:19 +0100
To: "randy Presuhn" <randy_presuhn@mindspring.com>,
	Martin Duerst <duerst@w3.org>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ltRU Working Group <ltru@ietf.org>
Subject: [Ltru] we will produce another draft
Precedence: list
Sender: ltru-bounces@lists.ietf.org
Errors-To: ltru-bounces@lists.ietf.org

we decided to pursue on your suggestion and to produce another Draft for 
this WG-ltru.

1. please indicate which file name we should use. The draft will be 
produced by several WG-ltru Members. (I am not sure I will be among them)
2. we want to make sure this Draft supports the needs of the W3C and CDLR 
as expressed in the Addison Philips/Mark Davis' Draft. We count on their 
assistance.
3. we plan having an initial draft presented in two to three weeks.

We are interested in hearing about every proposition/need not documented in 
the current Draft.

Best regards.
jfc morfin
AFRAC, VP R&D
http://afrac.org
======================================================
Standardizing Tags for the Identification of Languages should not be a way
to standardize languages and to unify the world under a dominant culture.
======================================================
For your convenience:
RFC 3066: http://www.ietf.org/rfc/rfc3066.txt?number=3066
Draft: 	http://www.ietf.org/internet-drafts/draft-ietf-ltru-registry-00.txt
Charter: http://ietf.org/html.charters/ltru-charter.html
gmane: http://dir.gmane.org/gmane.ietf.ltru
If you were Bcced for information and not familliar with the IETF process:
http://www.ietf.org/rfc/rfc2026.txt
http://www.ietf.org/rfc/rfc2418.txt
http://www.ietf.org/rfc/rfc3934.txt
http://www.ietf.org/rfc/rfc3669.txt
http://www.ietf.org/rfc/rfc3160.txt
http://www.ietf.org/internet-drafts/draft-hoffman-taobis-02.txt
======================================================
Jon Postel (RFC 1591): "The IANA is not in the business of deciding
what is and what is not a country. The selection of the ISO 3166 list
  as a basis for country code top-level domain names was made with
  the knowledge that ISO has a procedure for determining which
entities should be and should not be on that list."
======================================================
Brian Carpenter (RFC 1958/3.2): "If there are several ways of doing the
same thing, choose one. If a previous design, in the Internet context
or elsewhere, has successfully solved the same problem, choose the
same solution unless there is a good technical reason not to.
Duplication of the same protocol functionality should be avoided as far as
possible, without of course using this argument to reject improvements."
======================================================
It seems that what works for countries and ISO 3166 since 1978, should
apply to languages and to ISO 693.
======================================================


_______________________________________________
Ltru mailing list
Ltru@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/ltru