- From: Frank Ellermann <nobody@xyzzy.claranet.de>
- Date: Wed, 25 Jun 2008 01:15:35 +0200
- To: uri@w3.org
Ian Hickson wrote: > Is there any chance that the URI and IRI specifications might > get updated to handle these issues? RFC 3986 is a full Internet standard, software doing something else is broken. Of course old software has the excuse of being old. An update of RFC 3987 (IRIs) makes no sense until IDNAbis is ready. YMMV, IDNAbis won't affect query parts. Note that RFC 3987 is by definition an *immature* standard like any other proposed standard, expect changes when it is later promoted on standards track. The same goes for IDNA, but not STDs 63 + 66. > It would be much cleaner if instead HTML5 could just defer to > the URI specs for everything URI-related. That is not only "much clearer", it is a minimal requirement to talk about it (unless you want HTML5 published by ECMA). There are no non-ASCII characters in an STD 66 URI. And there are no non-ASCII characters in the URI-representation of an RFC 3987 IRI. Just reference RFC 3986 + 3987 "as is" and be done with it, it's no rocket science, and any attempt to "redefine" these standards can only cause confusion. Frank -- <http://0xd0.0x4d.0xbc.0xa6/> <shudder> Read STD 66 </shudder>
Received on Tuesday, 24 June 2008 23:14:38 UTC