This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
-evaluate-023 The test currently raises XPTY0004, but the spec states: "The as attribute, if present, indicates the required type of the result. [....]. This may cause a type error if conversion is not possible." and later: [ERR XTTE0780] If the as attribute [of xsl:function ] is specified, then the result evaluated by the sequence constructor (see 5.8 Sequence Constructors) is converted to the required type, using the function conversion rules. It is a type error if this conversion fails. So: there seems to be no specific error to use with evaluate-023 (which has a type error in the result), however, I would argue that XTTE0780 makes an excellent candidate. Or should we update the spec and create a specific error for this case? It seems to me that XPTY0004 is actually reserved for XPath type errors, not necessarily for XSLT-conversion-to-required-as-type. -evaluate-026 That test currently raises XPTY0004, while the spec states: [ERR XTTE3210] If the result of evaluating the context-item expression is a sequence containing more than one item, then a type error is signaled.
Currently fixed in Rev#680 by allowing both errors for evaluate-023 and introducing the error for evaluate-026. Leaving the bug open and assigning the bug to Michael Kay, for extra review and further discussion, if so needed.
Was resolved > 30 days ago, closing.