This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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?
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.
I'm happy for it to be added to a 3.1 wishlist.
To be considered for inclusion in a future version.
Assigning to future requirements per Working Group decision (https://lists.w3.org/Archives/Member/w3c-xsl-query/2012Oct/0087.html).
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?