W3C home > Mailing lists > Public > uri@w3.org > June 2008

Re: Error handling in URIs

From: Ian Hickson <ian@hixie.ch>
Date: Wed, 25 Jun 2008 23:24:26 +0000 (UTC)
To: John Cowan <cowan@ccil.org>
Cc: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>, uri@w3.org
Message-ID: <Pine.LNX.4.62.0806252322340.13974@hixie.dreamhostps.com>

On Wed, 25 Jun 2008, John Cowan wrote:
> Ian Hickson scripsit:
> 
> > I agree entirely that this kind of error handling stuff shouldn't be in 
> > HTML5. The only times HTML5 defines error handling for things outside the 
> > "HTML" language itself is when the relevant specs don't define their own 
> > error handling, and the relevant groups refuse to do anything about it.
> 
> It's only "error handling" when seen against the abstract background of 
> RFC-3986-centricity.  Otherwise, it is the HTML5 extension of URIs: how 
> do HTML5 browsers convert arbitrary Unicode strings to URIs? The answer 
> is different from RFC 3987, but no worse.

HTML5 (as defined today) doesn't allow authors to do anything that URIs 
and IRIs didn't allow. For example "http://example.com/{" is not valid in 
HTML5 (or in the URI or IRI specs). It's an error. However, HTML5 does 
define what browsers are to do with it. That's handling the error. So IMHO 
even from the point of view of the HTML5 spec it's still error handling.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 25 June 2008 23:25:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 January 2011 12:15:41 GMT