Project

Profile

Help

Actions
Send by e-mail Copy link

Bug #3861

closed

Incorrect type checking when xsl:key contains sequence constructor in place of @use attribute

Added by Michael Kay over 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Michael Kay
Category:
XSLT conformance
Sprint/Milestone:
-
Start date:
2018-07-28
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
9.8, trunk
Fix Committed on Branch:
9.8, trunk
Fixed in Maintenance Release:
9.9.0.1, 9.8.0.15
Platforms:

Description

When the use expression of an xsl:key is computed using a sequence constructor rather than an XPath expression in an @use attribute, incorrect type checking is applied: the required type of the result is set to xs:anyAtomicType? rather than xs:anyAtomicType*, disallowing a sequence of more than one value. (This applies whether or not composite="yes" is specified).

Test case key-097 added to the XSLT 3.0 test suite.

Raised by Martin Honnen here: https://saxonica.plan.io/boards/3/topics/7274

Please register to edit this issue

Actions
Send by e-mail Copy link

Also available in: Atom PDF