[whatwg] The problems with namespaces in text/html

Anne van Kesteren fora at annevankesteren.nl
Sat Nov 4 14:30:21 PST 2006

All good reasons to use XHTML5 and not HTML5. Tools supporting HTML5 will  
have to support the HTML5 parser as well and therefore the HTML5  
serialization. I don't really see your point.

On Sat, 04 Nov 2006 23:23:12 +0100, Elliotte Harold  
<elharo at metalab.unc.edu> wrote:
> Anne van Kesteren wrote:
>> Yes, exactly the reason they have the correct (MathML) namespace in the  
>> DOM. So they can be rendered, etc. The serialization format doesn't  
>> really matter.
> Like hell it doesn't matter! A DOM doesn't travel over the network. The  
> serialized form does. The DOM is one possible local model used to  
> process the document on one system. My tools may or may not be based on  
> the DOM, but they're going to start by receiving an actual XML instance.  
> We can use TagSoup to fudge HTML, but if you I want to handle MathML,  
> SVG, and other things in it, That instance had better be namespace  
> well-formed, and it had better use the right names for the right things,  
> both local and qualified.

Anne van Kesteren

More information about the whatwg mailing list