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 24968 - Two arg fn:collation-key and three arg fn:deep-equal are not context-dependent
Summary: Two arg fn:collation-key and three arg fn:deep-equal are not context-dependent
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (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-03-07 12:42 UTC by Abel Braaksma
Modified: 2014-08-02 13:54 UTC (History)
0 users

See Also:


Attachments

Description Abel Braaksma 2014-03-07 12:42:06 UTC
We have two versions of fn:collation-key [1], the two argument function taking the collation as an argument, hence the two-argument version of this function is not context-dependent.

Likewise, we have two versions of fn:deep-equal [2], the three argument function taking the collation as an argument, making it context-independent.

I think it is best that, in the same way other overloaded functions are described, a line is added for the two and three argument functions respectively, explaining this difference.

[1] http://www.w3.org/TR/xslt-30/#func-collation-key
[2] http://www.w3.org/TR/xslt-30/#func-deep-equal
Comment 1 Michael Kay 2014-03-07 20:58:41 UTC
The versions of these functions that omit the collation argument are context-dependent because they depend on the default collation.

The versions that take an explicit collation argument are context-dependent because the set of known collation URIs is context dependent; in addition (sadly), they use the static base URI to resolve the collation URI if it is relative.

F+O 3.0 (see for example http://www.w3.org/TR/xpath-functions-30/#func-deep-equal) is a bit more precise about exactly what the context dependencies are, and I will endeavour to add this information for XSLT 3.0 also.
Comment 2 Michael Kay 2014-05-15 14:44:08 UTC
This has been fixed in the current build.