- From: David Carlisle <davidc@nag.co.uk>
- Date: Mon, 03 Jan 2011 21:25:19 +0000
- CC: public-html-xml@w3.org
On 03/01/2011 19:26, Michael Kay wrote: > One of the policy questions is whether every XDM instance should have an > HTML5 serialization That would be nice, but I don't think it's really feasible. The trouble is, if the aim is watered down to asking whether "reasonable" XDM instances could be serialised as html5, different people will have different opinions on what's reasonable. personally I'd like there to be some way to get the html5 parser to parse a fragment in "foreign content mode" but without a math or svg wrapper and without the forced closure of that mode by elements with html element names. That would allow at least any xml element tree to be serialised as html5 with the correct local names. namespaces could be dealt with either by the process just not supporting namespaces in a text/html context or by a post-parse namespace fixup initiated by script. David
Received on Monday, 3 January 2011 21:25:32 UTC