Saxon

Firstly, let's look at what happens without next-in-chain. If my stylesheet does:

    <xsl:template match="/">
        <xsl:result-document href="out.xml">
            <one/>
        </xsl:result-document>
    </xsl:template>

and I invoke it with:

-xsl:test.xsl -s:test.xml -o:outdir/dummy.xml

then both 9.6 and 9.7 correctly write the output to outdir/out.xml

and produce the message

Writing to file:/Users/zzzz/Desktop/temp/outdir/out.xml

If I now add

<xsl:output saxon:next-in-chain="test2.xsl"/>

where test2.xsl does

    <xsl:template match="/">
        <xsl:result-document href="out2.xml" saxon:next-in-chain="test2.xsl">
            <two><xsl:copy-of select="."/></two>
        </xsl:result-document>
    </xsl:template>

then 9.6 produces the two messages

Writing to file:/Users/zzzz/Desktop/temp/out.xml
Writing to file:/Users/zzzz/Desktop/temp/out2.xml

while 9.7 produces the two messages

Writing to file:/Users/zzzz/Desktop/temp/outdir/out.xml
Writing to file:/Users/zzzz/Desktop/temp/out2.xml

I believe the correct action according to the spec is to write to:

file:/Users/zzzz/Desktop/temp/outdir/out2.xml

and neither release is doing that.

The key statement in the documentation is: "The output of the second stylesheet will be directed to the destination that would have been used for the first stylesheet if no saxon:next-in-chain attribute were present." This means the base output URI for the second transformation should be the same as the base output URI of the first.

Closing this as it's not clear that there is a bug here.