[Bug 29148] New: [XSLT30] Text on constructing complex content says that document nodes are removed, but this is not always true

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29148

            Bug ID: 29148
           Summary: [XSLT30] Text on constructing complex content says
                    that document nodes are removed, but this is not
                    always true
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

Under 5.8.1 Constructing Complex Content, we write (4th item):

4. Any document node within the result sequence is replaced by a sequence
containing each of its children, in document order.

However, when inside an xsl:variable, the result sequence implicitly contains a
document node. This document node is not removed. Conversely, if you write:

<xsl:variable>
    <xsl:document>+

you could say that the document not is not removed either, as the xsl:variable
will not have to be converted into a variable containing a document node.

Likewise, if you have as="document-node()", the sequence is required to create
a document node and it is not removed (if we did so, it would invalidate the
variable).

Though I am unsure how this could be written more clearly (rules elsewhere are
clear), I stumbled upon it, considering it an (albeit small) ambiguity.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 24 September 2015 08:55:06 UTC