"Canonical" HTML5 and XHTML5 output

I'd like to write an XSL transform that serialises XML (say with XHTML 1.0 Strict vocabulary for a start) to HTML5 or XHTML5 text.

I don't have an XSLT processor that can generate HTML5 output, so I'll have to write my own (by using a transform to text).

Do you think it would be useful to add a "description of canonical output" section to the existing documents? Developers using the term 'canonical' forms are often concerned with ensuring ease of comparability. I'm not so concerned with that here, I'm just thinking about 'best practice' methods of output for authoring tools that generate HTML5 or XHTML5.

The current July 2007 documents do of course describe serialisation to HTML5 already, maybe if they get 'beefed-up' at some later stage, then this will serve.

Is it intended that XHTML5 will have a defined 'old-UA-friendly serialisation', in the sense attempted by the XHTML1.0 compatibility appendix? - whether or not that is awarded 'canonical XHTML5' status.


Cecil Ward.

Received on Tuesday, 24 July 2007 14:53:15 UTC