[Bug 24140] New: [xslt 3.0] xsl:copy "must not generate any type errors"

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

            Bug ID: 24140
           Summary: [xslt 3.0] xsl:copy "must not generate any type
                    errors"
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: mike@saxonica.com
        QA Contact: public-qt-comments@w3.org

Under xsl:copy we say that the sequence constructor (under given conditions)
"is not evaluated and must not generate any type errors."

This wording is potentially confusing; it could be read as meaning that it is
an error it the sequence constructor generates any type errors, which would be
a truism. The intended meaning, I think, is that if the processor DOES evaluate
the sequence constructor then any errors in doing so must be masked. 

Perhaps it is also intended to mean that processors that normally do static
type checking must not do so (or must mask any errors from so doing) in respect
of the sequence constructor. However, this seems a bit too strong. If the
instruction is

<xsl:copy select="$a">
  <xsl:value-of select="2 + 'London'"/>
</xsl:copy>

then it's unreasonable to stop the processor reporting a type error for the
arithmetic expression. I think the real intended meaning is that there must be
no type errors arising from the fact that the selected item is not an element
or document node.

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

Received on Thursday, 19 December 2013 14:14:36 UTC