- From: <bugzilla@jessica.w3.org>
- Date: Fri, 21 Dec 2012 05:20:22 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20416 Henry Zongaro <zongaro@ca.ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Henry Zongaro <zongaro@ca.ibm.com> --- At the joint XSLT/XQuery teleconference of 18 December 2012,[1] the working groups decided to make the changes suggested by Josh. I also replaced the XSLT fragment that describes how the item-separator serialization parameter is treated with the following, as the original had the same problem as the XQuery expression: <xsl:document> <xsl:for-each select="$seq"> <xsl:sequence select="if position() gt 1 then $sep else ()"/> <xsl:choose> <xsl:when test=". instance of node()"> <xsl:sequence select="."/> </xsl:when> <xsl:otherwise> <xsl:value-of select="."/> </xsl:otherwise> </xsl:choose> </xsl:for-each> </xsl:document> Finally, Ghislain pointed out that the second step of sequence normalization indicates that if an item in the sequence is not atomic, it will be a node. That was true in Serialization 1.0, but is no longer, with the addition of functions. Similarly, the final sentence of the paragraph indicates error SERN0001 is reported if the sequence contains namespace or attribute nodes. That should also mention functions. I will update both accordingly. These changes will be reflected in the next working draft. Josh, as you were present when this decision was made, I will assume you are in agreement with these changes, and so mark the bug as CLOSED. [1] https://lists.w3.org/Archives/Member/w3c-xsl-query/2012Dec/0054.html (Member-only link) -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 21 December 2012 05:20:25 UTC