- From: Robert Burns <rob@robburns.com>
- Date: Thu, 6 Sep 2007 22:52:24 -0500
- To: Karl Dubost <karl@w3.org>
- Cc: Henri Sivonen <hsivonen@iki.fi>, Liam Quin <liam@w3.org>, public-html WG <public-html@w3.org>
Hi Karl, On Sep 6, 2007, at 10:44 PM, Karl Dubost wrote: > > Henri, Liam, > > Context > http://lists.w3.org/Archives/Public/public-html/2007Sep/0164 > > > Henri Sivonen (6 sept. 2007 - 21:36) : >> Doing it this way addresses pretty much all the issues raised >> about using the text/html serialization of HTML5 together with >> XSLT. With the current crop of XSLT processors this entails taking >> out SAX as opposed to bytes from the XSLT processor and plugging >> in an HTML5 serializer. I suggest considering the "html" output >> method of XSLT obsolete as of HTML5. > > The HTML output method would not be obsolete, except if we were > rescinding HTML 4.01. Though it might be useful to coordinate > with the XML Activity and the XSL WG to see if the HTML ouput > method defined in XSLT 2.0 can evolve. > > > * XSLT 1.0 > http://www.w3.org/TR/xslt#section-HTML-Output-Method > > * XSLT 2.0 > http://www.w3.org/TR/xslt20/#element-output > The output methods are defined in > http://www.w3.org/TR/xslt-xquery-serialization/ > The HTML output method would not be obsolete for HTML5 either. The XSLT proposal would either need to be updated to ignore the HTMLL5 text/html serialization xmlns permitted attribute or would need to be made namespace aware for text/html serializations. Without the HTML output method there would be no way to output text/ html serialized versions of HTML5 that didn't have errant end tags (like <br></br>). This is strictly a namespace issue. The XSLT recommendation never anticipated namespaces or namespace declarations for text/html serialized elements. Another approach might be just to change the recommendation to strip xmlns declarations from the HTML output. It all depends on where the WG takes namespaces in that serialization. Take care, Rob
Received on Friday, 7 September 2007 03:52:42 UTC