--On Sunday, 27 February, 2005 18:15 -0800 Erik van der Poel
<[EMAIL PROTECTED]> wrote:
>...
> As I indicate at nameprep.org, I found some character tables
> at the IANA site, but I found even more at the GNU libidn
> site. One of the first things to do is to agree on a single
> machine-readable format. The tables do not all use the same
> format yet, it seems. Then we would also need to have the
> latest and most official tables from the registries themselves
> (instead of possibly out of date IANA tables and possibly
> embellished unofficial GNU libidn tables).
Erik,
I'm been mildly resisting standard-format,
machine-interpretable, tables at IANA for a few reasons. The two
most important ones are:
(i) ICANN is still assuming that this is a registry
issue. As such, if someone else starts guessing at what
a registry is doing, we may get into trouble, especially
since the tables may not show all of the relevant
registry rules and restrictions.
(ii) We've got at least two models for processing a
proposed IDN. One compares the proposed label against a
list of characters for the selected language as
maintained by that registry and, if it passes, registers
it if it isn't already taken. The other involves the
JET "variant" model, or some relative of it, to
determine what labels, or sets of labels, are permitted.
The first plan requires a simple list of characters; the
second requires a three (or two, or four) column table.
Also please note that the IANA tables make no attempt to be
authoritative for any given language. They are just
documentation of what characters a given registry permits to be
associated with a given "language" for their registry. To have
three different, and incompatible, tables --associated with
three different registries-- for "the same language" is not only
possible, but likely.
john
