Re: HTML5 URL vs. IRI vs. URI...

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