Re: document() access. The combinations

Dave,
I think you should split your table up into examples of incorrect URI
and examples of correct ones, having them all mixed up confuses the
issue.

Also you ask

 Which other processors are popular?
>
    <entry>Saxon 6.5.2</entry>
    <entry>Microsoft V4</entry>
    <entry>Xalan</entry>
    <entry>LibXML 10029</entry>

At least for the Java ones I wouldn't have expected this to be
(directly) XSLT processor specific but rather a feature of the URI resolver
used by the XML parser used by the  XSLT processor.
Clearly any given XSLT processor will have some default, but actual
behaviour may well depend on several other factors, which JVM is being
used, which sax/XML parser is being used, etc.

David


________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list