I don't know whether with collection() the processor has the
freedom not to load the document into memory until its
needed, but I suspect it would have to be a specific
optimisation to not load it for document-uri()
The optimization is permitted by the spec (it's a general rule that the
processor is never obliged to do work that is needed only to detect errors
that would otherwise be missed); but it's not an optimization that Saxon
attempts.
Another way to do this would be to write a custom CollectionURIResolver; but
that involves writing Java code, whereas the method suggested by Andrew
doesn't.
Regards,
Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--