- From: <bugzilla@jessica.w3.org>
- Date: Sat, 27 Feb 2016 23:37:52 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29431 --- Comment #2 from Michael Kay <mike@saxonica.com> --- I propose the following. (a) whether or not the principal and/or secondary results are serialized is a decision made by the application and established using the processor's API; it is not affected by anything in the stylesheet. (b) in the case of the principal result, the "raw result" is the immediate result of the sequence constructor in the initial template or function, converted if necessary to the declared type of that template or function using the function conversion rules. In the case of a secondary result, the "raw result" is the immediate result of the sequence constructor in the xsl:result-document instruction (there is no declared type in this case, therefore no conversion). (c) if a result document is to be serialized, then the raw result is passed to the serializer, where it goes through the various phases of serialization starting with "sequence normalization" (where sequence normalization applies to the chosen output method). The serialization parameters defined in xsl:output or xsl:result-document (as appropriate) (including item-separator) are passed to the serializer. The effect of item-separator is thus (like all other serialization parameters) defined solely by the serialization spec. (d) if a result document is _not_ to be serialized, then the application may receive either the raw result (as defined above), or the result of applying sequence normalization as defined in the serialization specification. This choice is controlled by the build-tree attribute of xsl:output or xsl:result-document, and may be overridden using the processor's transformation API. (If build-tree is yes, then the sequence normalization process is applied.) All serialization parameters other than item-separator are ignored (so sequence normalization takes place even if there are serialization parameters specifying, say, method="json"). The consequence of this rule is that item-separator is applicable whether or not the result is being serialized, and that its meaning is as defined in the serialization spec. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Saturday, 27 February 2016 23:37:56 UTC