Re: [Ltru] [psg.com #1099] WGLC add empty extension registry

"Kent Karlsson" <kentk@cs.chalmers.se> Mon, 15 August 2005 07:59 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E4ZsS-0007a4-J7; Mon, 15 Aug 2005 03:59:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E4ZsQ-0007Zr-Pz for ltru@megatron.ietf.org; Mon, 15 Aug 2005 03:59:22 -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 DAA19058 for <ltru@ietf.org>; Mon, 15 Aug 2005 03:59:21 -0400 (EDT)
Received: from anubis.medic.chalmers.se ([129.16.30.218]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E4aRW-0000A0-Me for ltru@ietf.org; Mon, 15 Aug 2005 04:35:39 -0400
X-Medic-Info: 1f6d.43004b4c.0 cr5GezPZb84vXXJa
Received: from webmail.chalmers.se (elbe1.ita.chalmers.se [129.16.222.100]) by mail.chalmers.se (Postfix) with ESMTP id 34804467C; Mon, 15 Aug 2005 09:59:08 +0200 (CEST)
Received: from 83.248.26.202 (SquirrelMail authenticated user kent); by webmail.chalmers.se with HTTP; Mon, 15 Aug 2005 09:59:08 +0200 (CEST)
Message-ID: <61696.83.248.26.202.1124092748.squirrel@webmail.chalmers.se>
In-Reply-To: <001701c5a163$52d8c7a0$7f1afea9@oemcomputer>
References: <001801c5a159$7b0f78e0$030aa8c0@DEWELL> <001701c5a163$52d8c7a0$7f1afea9@oemcomputer>
Date: Mon, 15 Aug 2005 09:59:08 +0200
Subject: Re: [Ltru] [psg.com #1099] WGLC add empty extension registry
From: Kent Karlsson <kentk@cs.chalmers.se>
To: Randy Presuhn <randy_presuhn@mindspring.com>
User-Agent: SquirrelMail/1.4.3a-7.EL3
X-Mailer: SquirrelMail/1.4.3a-7.EL3
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Priority: 3 (Normal)
Importance: Normal
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: quoted-printable
Cc: LTRU Working Group <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

> I disagree.  Section 3.6 says "[t]his registry MUST use the record-jar
> format described by the ABNF in Section 3.1."  That would give it a
> File-Date record.

Not directly by the ABNF, but by the text following it.

Since I like the file self declarations, I would suggest to
make the following text replacement, with obvious consequences:

---------------------OLD TEXT-----------------
The first record in the file contains the single field whose field-name is
"File-Date".
The field-body of this record contains the last modification date of this
copy of the registry,
making it possible to compare different versions of the registry. The
registry on the IANA
website is the most current. Versions with an older date than that one are
not up-to-date.

File-Date: 2004-06-28
%%
---------------------NEW TEXT-----------------
The first record in the file SHALL contain two fields whose field-names
are "File-Date" and "Description".
The field-body of the "File-Date" field of this record SHALL contain the
last modification date of this copy
of the registry. This makes it possible to compare different versions of
the registry. The registry on the
IANA website is the most current. Versions with an older date than that
one are not up-to-date.
The field-body of the "Description" field SHALL contain a short comment on
what the content of the
registry is. For example,

File-Date: 2004-06-28
Description: IANA Language subtag registry (see RFC XXXX)
-----------------------------------------

This would then apply to both registries. (Maybe some other sentence needs
to be amended too.) Note the introduction of the "SHALL"s above, to make
it proper standardese.

   /kent k



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