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 16744 - [XQ31ReqUC] fn:collection-available
Summary: [XQ31ReqUC] fn:collection-available
Status: NEW
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Requirements for Future Versions (show other bugs)
Version: Member-only Editors 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
Depends on:
Reported: 2012-04-16 08:24 UTC by Tim Mills
Modified: 2015-12-17 11:15 UTC (History)
1 user (show)

See Also:


Description Tim Mills 2012-04-16 08:24:14 UTC
Is there a good reason why fn:doc and fn:unparsed-text have corresponding functions fn:doc-available and fn:unparsed-text-available, but fn:collection does not have a corresponding fn:collection-available?
Comment 1 Michael Kay 2012-06-19 13:29:33 UTC
One possible reason is that if collection-available() has parallel semantics with the other functions, it could be quite expensive: it has to determine not only that a collection with the required name exists, but that it can be read in its entirety without error. Given that many operations on collections are likely to filter the collection, which might mean that some errors go undetected, the operation could be expensive. But I agree that's not a strong justification.

There is however a process argument against adding it now: the time for adding new features to the current 3.0 version of the spec is past.
Comment 2 Tim Mills 2012-06-19 13:37:08 UTC
I'm happy for it to be added to a 3.1 wishlist.
Comment 3 Tim Mills 2012-06-19 15:51:34 UTC
To be considered for inclusion in a future version.
Comment 4 Jonathan Robie 2014-05-20 16:51:39 UTC
Assigning to future requirements per Working Group decision (
Comment 5 Tim Mills 2015-12-17 11:15:30 UTC
It looks as if collection-available was noted as a future requirement, but hasn't made it into XQ3.1

Is is now too late again?