- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 06 Apr 2009 13:58:47 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6775 --- Comment #5 from Michael Kay <mike@saxonica.com> 2009-04-06 13:58:46 --- >I observe that browsers implement XSLT 1.0 rather than XSLT 2.0. Well, clearly, any solution that involves changing XSLT 1.0 is a non-starter. Apart from anything else, most XSLT 1.0 processors are no longer actively developed. >In any case, this needs to be triggered on the output method even though it is a DOM-to-DOM transform. Well, I don't think there's anything to stop you defining a process called say H5Transform which takes an XSLT stylesheet, processes the source document as defined in the XSLT specification, and then does some further processing on the result tree based on what you find in the xsl:output definition. That wouldn't require any changes to XSLT, and you could do it without waiting for a new XSLT release. You could even define it using XSLT 1.0 rather than 2.0 as the baseline. >I think this the XSLT spec should specify this behavior. I don't. XSLT is a pure XML-to-XML transformation language, there's no room for special-casing it for particular XML vocabularies. We've even moved the serialization stuff into a separate spec to keep it separate. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Monday, 6 April 2009 13:58:57 UTC