[Bug 25174] [XSLT30] Buffering with xsl:try wrapped around xsl:stream or xsl:result-document

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25174

--- Comment #7 from Michael Kay <mike@saxonica.com> ---
At the telcon on 14 August we studied the new text, and the question was raised
again of whether to put the new attribute on xsl:result-document, xsl:try, or
both.

On reflection I'm inclined to put it on xsl:try. This has the advantage,
originally pointed out in comment 5, that it becomes more visible what the
recovery units are, and where buffering might be required to enable recovery.

If we were to add the attribute on xsl:result-document as well then I would
propose that this merely acts as a default for the value on xsl:try. However,
since the association of an xsl:result-document instruction to an xsl:try
instruction is dynamic, this adds another piece of dynamic context information
which I think we could well do without. Also, putting the attribute on
xsl:result-document makes it messy to define an equivalent for the principal
result tree: xsl:output is not really the right place as it's all about
serialization. So my proposal is to have it on xsl:try only.

The text of section 24.3 is largely still applicable, though it now becoomes
logical to move it to 8.3.2.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 21 August 2014 14:10:39 UTC