> Please forgive my ignorance, but I'm really confused about the
> use of the saxon extension element saxon:output. On page 652 of
> _XSLT Programmer's Reference_ it is stated that using saxon:output
> "[output] can also be directed to be processed by another named
> stylesheet." But there are no examples in the book showing how
> this can be done.
True. I plead limitations of space. (Also, you're referring to the first
edition, so the documentation you're using is 18 months older than the
Look up saxon:next-in-chain in the extensions.html file. There's still no
example, but it's simple enough:
The saxon:next-in-chain is available both on xsl:output and on xsl:document
To be honest, though, I usually control stylesheet chaining from the Java
API rather than using this facility.
> So when I look at the documentation on the saxon:output element
> it says that "the saxon:output instruction is a synonym for
> xsl:document". But I thought the xsl:document element provides for
> multiple inputs and has nothing to do with output!
xsl:document is a feature introduced in the XSLT 1.1 working draft to allow
multiple output documents. Don't confuse it with the document() function,
which supports multiple inputs.