This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26801 - [XT30] evaluate-026 should raise XTTE3210, evaluate-023 should raise XTTE0780
Summary: [XT30] evaluate-026 should raise XTTE3210, evaluate-023 should raise XTTE0780
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 Test Suite (show other bugs)
Version: Last Call drafts
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-15 00:36 UTC by Abel Braaksma
Modified: 2015-05-06 21:14 UTC (History)
0 users

See Also:


Attachments

Description Abel Braaksma 2014-09-15 00:36:34 UTC
-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.
Comment 1 Abel Braaksma 2014-09-15 01:38:42 UTC
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.
Comment 2 Abel Braaksma 2015-05-06 21:14:02 UTC
Was resolved > 30 days ago, closing.