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 30253 - [XSLT30] map:find returns an array, but must be supported even if a processor does not support the XP31 feature, which is not possible
Summary: [XSLT30] map:find returns an array, but must be supported even if a processor...
Status: NEW
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Recommendation
Hardware: PC Windows NT
: P2 major
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: 2018-05-11 00:43 UTC by Abel Braaksma
Modified: 2018-05-11 00:46 UTC (History)
0 users

See Also:

Attachments

Description Abel Braaksma 2018-05-11 00:43:23 UTC 
Currently, the map:find function is listed as mandatory function to support, even if you don't support the XP31 feature. However, the function returns an array, which is an XP31 feature.

Ergo, the two are not each other's supplement anymore. I think the map:find was not meant to be part of the mandatory functions.
Comment 1 Abel Braaksma 2018-05-11 00:46:10 UTC 
> the two are not each other's supplement anymore.
That wasn't clear. I meant: the intent of the spec was that it is possible to support maps, without the need to support (all of) XP31, of which arrays are a main new feature. With the inclusion of map:find, it becomes impossible to split the two, as it requires an implementation to support arrays, and hence (most of) XP31, just for one function. I don't think that was intentional.