Bug #4484

Documentation of fn:collection()

Added by Michael Kay 5 months ago. Updated 5 months ago.

In Progress
Start date:
Due date:
% Done:


Estimated time:
Legacy ID:
Applies to branch:
10, 9.9
Fix Committed on Branch:
10, 9.9
Fixed in Maintenance Release:


The status section of the documentation for fn:collection() (in the Function Library chapter) refers to the old CollectionURIResolver interface, which is deprecated in 9.9 and withdrawn in 10.0. It should be updated to refer to the new CollectionFinder.


#1 Updated by Debbie Lockett 5 months ago

  • Status changed from New to Resolved

Committed updates to Function Library documentation for fn:collection() and fn:uri-collection(). Plus further related edits under sourcedocs/collections and extensibility/config-extend/uri-resolution/collection-uri-resolver. In particular, "Writing your own Collection Finder" is moved to a subsection of "Collections" (i.e. sourcedocs/collections/user-collections).

#2 Updated by Debbie Lockett 5 months ago

  • Status changed from Resolved to In Progress

Online 10 documentation (XML and HTML versions) updated.

I need to make the relevant changes in 9.9 too.

#3 Updated by Debbie Lockett 5 months ago

  • Status changed from In Progress to Closed
  • Fix Committed on Branch 10, 9.9 added

Relevant content changes also now made and committed in 9.9 documentation, for the following pages:

  • extensibility/config-extend/uri-resolution/collection-uri-resolver
  • functions/fn/collection, uri-collection
  • sourcedocs/collections

(I didn't bother with the subsection changes in sourcedocs/collections for the 9.9 branch. Section restructuring is a bit disruptive.)

Online 9.9 documentation (XML and HTML versions) updated, so now marking as closed.

#4 Updated by Debbie Lockett 5 months ago

  • Assignee changed from Michael Kay to Debbie Lockett
  • % Done changed from 0 to 100

#5 Updated by Michael Kay 5 months ago

  • Status changed from Closed to In Progress

One more: I notice that the last section in!sourcedocs/collections says

On the .NET product there is another way to use a collection URI (provided that you use the API rather than the command line): you can register a collection using the Processor.RegisterCollection method on the Saxon.Api.Processor class.

In fact the Java product now also has Collection.registerCollection() - though for some reason it's not exposed at the s9api Processor level. This only works if the standard CollectionFinder is used. Also, I see, it isn't tested - I'll add a unit test.

Please register to edit this issue

Also available in: Atom PDF