Re: Unobtrusive Namespaces, Imaginary Nmespaces

On Nov 12, 2009, at 05:13, Liam Quin wrote:

> The idea is define the HTML 5 behaviour with respect to namespaces
> in such a way that XML systems could be [changed to be]
> compatible,

If you are OK with changing XML systems, wouldn't the most sensible change be putting an HTML parser that exposes an XML API at the start of the pipeline when the input is text/html?

See: http://about.validator.nu/htmlparser/
It exposes SAX, DOM and XOM so the app can behave as though it were dealing with an XML parser parsing the equivalent XHTML5 document.

> 3. For added brownie points, Web browsers would fetch namespace
>   definition files if they are mentioned (and are not in the browser's
>   cache, of course).

This is highly unlikely to happen.

-- 
Henri Sivonen
hsivonen@iki.fi
http://hsivonen.iki.fi/

Received on Thursday, 12 November 2009 09:08:34 UTC