- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 02 Jun 2009 07:40:04 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6775 --- Comment #8 from Michael Kay <mike@saxonica.com> 2009-06-02 07:40:03 --- >I'm a little unclear on what the result of an XSLT transform is expected to yield. It doesn't seem entirely true that XSLT is an XML-to-XML transform since output (which is what generates the result XML serialization) is an optional (in XSLT 1) or at least external (in XSLT 2) step. Yes, I wasn't being 100% accurate when I said XML-to-XML. The XSLT stylesheet describes two processes, a transformation process followed by an optional serialization process. The transformation process is actually XDM-to-XDM (assuming that if you're talking about about 1.0, "XDM" means the tree data model described in the XPath 1.0 specification); and the serialization process is XDM to XML, HTML, or text. If you want something else as output, such as a DOM (in either XML or HTML flavour), or indeed visible pixels on the browser screen, then you are doing post-processing on the XDM output which is outside the scope of the XSLT specification. It's unclear to me where this bug report is leading. Is a change needed to the XSLT specification (or related specifications), and if so, what is that change? -- 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 Tuesday, 2 June 2009 07:40:11 UTC