W3C home > Mailing lists > Public > uri@w3.org > January 2014

Re: Standardizing on IDNA 2003 in the URL Standard

From: Andrew Sullivan <ajs@anvilwalrusden.com>
Date: Wed, 15 Jan 2014 12:19:26 -0500
To: Anne van Kesteren <annevk@annevk.nl>
Cc: Mark Davis ? <mark@macchiato.com>, "PUBLIC-IRI@W3.ORG" <public-iri@w3.org>, "uri@w3.org" <uri@w3.org>, John C Klensin <klensin@jck.com>, IDNA update work <idna-update@alvestrand.no>, Vint Cerf <vint@google.com>, "www-tag.w3.org" <www-tag@w3.org>
Message-ID: <20140115171926.GA20699@mx1.yitter.info>
On Wed, Jan 15, 2014 at 04:26:22PM +0000, Anne van Kesteren wrote:

> I have not checked what of that can be removed if we use UTS #46
> instead. Certainly referencing IDNA2008 directly does not work, as
> "A.com" does not become "a.com", which would presumably break too many
> scripts.

IDNA2008 has no effect at all on "A.com" or "a.com".

IDNA2008 does say that "Aà.com" is not PVALID.  I _believe_ that under
IDNA2003 that becomes "aà.com".  The reason IDNA2008 doesn't do that
is because you can't tell whether "Aà.com" is supposed to be "àà.com"
or "aà.com", so IDNA2008 tries to say "don't do that".

IDNA2008 also says that you can do some local mapping.  In my opinion,
UTS #46 goes too far with compatibility attempts to IDNA2003, but I'm
prepared to accept that lots of other people disagree.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com
Received on Wednesday, 15 January 2014 17:19:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:16 UTC