16744 2012-04-16 08:24:14 +0000 [XQ31ReqUC] fn:collection-available 2015-12-17 11:15:30 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Requirements for Future Versions Member-only Editors Drafts PC Windows NT NEW P2 normal --- 1 tim mike jim.melton public-qt-comments oldest_to_newest 66732 0 tim 2012-04-16 08:24:14 +0000 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? 69227 1 mike 2012-06-19 13:29:33 +0000 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. 69228 2 tim 2012-06-19 13:37:08 +0000 I'm happy for it to be added to a 3.1 wishlist. 69239 3 tim 2012-06-19 15:51:34 +0000 To be considered for inclusion in a future version. 106471 4 jonathan.robie 2014-05-20 16:51:39 +0000 Assigning to future requirements per Working Group decision (https://lists.w3.org/Archives/Member/w3c-xsl-query/2012Oct/0087.html). 124449 5 tim 2015-12-17 11:15:30 +0000 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?