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 18401 - Optional Features in XPath 3.0
Summary: Optional Features in XPath 3.0
Status: RESOLVED INVALID
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XPath 3.0 (show other bugs)
Version: Working drafts
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Jonathan Robie
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-25 16:38 UTC by Jonathan Robie
Modified: 2012-09-11 15:27 UTC (History)
2 users (show)

See Also:

Attachments

Description Jonathan Robie 2012-07-25 16:38:33 UTC 
Which features of XPath 3.0 are optional features?

* Dynamic function call?
* Inline function expressions?

Are there other candidates for optional features?
Comment 1 Michael Kay 2012-07-25 21:36:24 UTC 
I think the only reasonable candidate for an optional feature is "higher order functions" which would include the function() sequenceType syntax, inline functions, function literals (f#n), partial application, dynamic callling, functions such as fn:map, and functions such as fn:function-name and fn:function-lookup.

I have an open mind as to whether making this an optional feature would be a good idea. I think that before doing so, we would want to see a reasoned argument from an implementor or from the developers of a significant host language (e.g. XForms) as to why the feature is unwanted.
Comment 2 Jim Melton 2012-09-11 15:27:47 UTC 
Conformance to XPath is specified in the document defining the host language (e.g., XQuery), so it's not necessary to discuss such conformance issues in the XPath spec itself.