- From: Dan Connolly <connolly@w3.org>
- Date: Fri, 22 Aug 2008 10:51:55 -0500
- To: "public-html@w3.org WG" <public-html@w3.org>
connecting this thread with tracker ISSUE-56 urls-webarch http://www.w3.org/html/wg/tracker/issues/56 On Fri, 2008-08-22 at 09:18 +0200, Julian Reschke wrote: > Phillips, Addison wrote: > > (on behalf of the I18N Core WG) > > > > During a recent discussion of this thread, our working group noted that Section 2.5.1 defines the term "valid URL" using four bullet points. The third bullet point says: > > > > -- > > The URL is a valid IRI reference and its query component contains no unescaped non-ASCII characters. > > -- > > > > This definition isn't quite complete. "Non-ASCII characters" can be escaped in lots of ways using a wide variety of character encodings. You should mention the use of UTF-8 to escape non-ASCII characters or (better?) reference section 3.1 of IRI (3987). > > ... > > Although I still disagree with how HTML5 introduces this, I think *this* > part is incorrect. It *does* allow query parameters to be encoded using, > for instance, ISO-8859-1, and it needs to do this for compatibility with > existing content. > > BR, Julian -- Dan Connolly, W3C http://www.w3.org/People/Connolly/ gpg D3C2 887B 0F92 6005 C541 0875 0F91 96DE 6E52 C29E
Received on Friday, 22 August 2008 15:50:48 UTC