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 19548 - [XP30] Higher-order functions feature
Summary: [XP30] Higher-order functions feature
Status: CLOSED INVALID
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XPath 3.0 (show other bugs)
Version: Working drafts
Hardware: PC Windows NT
: 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-10-16 12:26 UTC by Tim Mills
Modified: 2012-10-16 13:59 UTC (History)
0 users

See Also:

Attachments

Description Tim Mills 2012-10-16 12:26:49 UTC 
Shouldn't higher-order functions be an optional feature, as in XQuery?
Comment 1 Jonathan Robie 2012-10-16 13:37:41 UTC 
XPath a component used in other specifications, which are allowed to subset it or extend it, as long as they do not change the syntax or semantics of the things defined in the XPath spec. Given that, what does it mean for a feature to be optional?

We currently say that static typing is a optional feature in XPath, no other features are optional. That's because static typing actually does change the semantics, and we allow implementations to interpret the spec with or without static typing.

But I don't think we need to do the same for higher order functions.
Comment 2 Tim Mills 2012-10-16 13:59:41 UTC 
OK, fine.