Thanks a lot to you and Mike for the help.
As I'm planning to start working with the latest version of Saxon anyway,
I'll probably just stop using <xsl:document> for few weeks or so, until I'll
get Saxon 7; the reason I can afford to do so is that <xsl:document> support
is not crucial for us at this stage, as it's executed in a separate filter
which takes an svg input and links an html output to it, this is for clients
which may prefer to get an html instead of direct svg.
But one thing I still don't quite understand is why an OutputURIResolver has
to be used for resolving <xsl:document>'s href ? I undestand that it *may*
be used if I wish to provide a custom Result (which justifies an overhead
associated with creating some custom Java classes), but I've thought that a
systemID's value should take precedence in this case (when set on
What do you think ?
----- Original Message -----
From: "Trevor Nash" <tcn@...>
To: "'Siarhei Biarozkin'" <sberyozkin@...>
Cc: "'Saxon List'" <saxon-help@...>
Sent: Thursday, December 05, 2002 11:05 AM
Subject: Re: [saxon] Using <xsl:document>
On Wed, 4 Dec 2002 19:31:12 -0000, Mike wrote:
>Saxon 7.x provides an OutputURIResolver hook that allows you to control
>this kind of thing. There's no equivalent built-in to 6.5.2, but Trevor
>Nash has written an extension to do it - he's on the list so I expect
>he'll chime in and say how to get it...
What I have is a modified version of Saxon 6.5.1 (not 6.5.2, though
carrying the changes forward should be trivial). It implements the
OutputURIResolver, I believe in the same way as Saxon 7 - but I wrote
it before Saxon 7, and I haven't yet looked at what Mike did to make a
precise list of differences. Package names will certainly come into
it, and the way you supply the resolver class name is probably
If you go to http://www.melvaig.co.uk and download the Sock product, you will
find in there a file 'dane.jar'. This is the same as saxon.jar from
6.5.1 but with the OutputURIResolver facility. All the source code
comes with Sock as well. Documentation is in Dane/dane.html. I have
called it Dane rather than Saxon not to hide the fact that its based
on Saxon, but to avoid any confusion with the 'real' Saxon.
BTW Mike, have you ever had any contact with the JAXP people about the
OutputURIResolver interface? I wrote to the address on the web site
but never got an acknowledgement.
If anyone uses this, contact me off list if you need help.
Melvaig Software Engineering Limited
voice: +44 (0) 1445 771 271
email: tcn@... web: http://www.melvaig.co.uk