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

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

--- Comment #2 from Michael Kay <mike@saxonica.com> ---
The current language is:

When the selected item is an atomic value or function item ... [or] when the
selected item is an attribute node, text node, comment node, processing
instruction node, or namespace node.... The sequence constructor is not
evaluated, and must not generate any type errors.

The wording of the last sentence in 2.0 was simply:

The sequence constructor, if present, is not evaluated.

I'm going to propose that we move back to the 2.0 wording, and remove the
phrase "and must not generate any type errors"; I can't think of any sensible
way of distinguishing the kind of type errors it makes sense to raise from
those it doesn't.

In fact I would propose another change, to say:

The sequence constructor is not evaluated.

on the grounds that the sequence constructor is always present (it may be
empty, but it's always there).

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

Received on Tuesday, 28 January 2014 18:00:42 UTC