- From: <bugzilla@jessica.w3.org>
- Date: Fri, 02 Oct 2015 13:13:18 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29162 Abel Braaksma <abel.braaksma@xs4all.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abel.braaksma@xs4all.nl --- Comment #1 from Abel Braaksma <abel.braaksma@xs4all.nl> --- I believe this requirement was added to allow for the serialization feature that is described in: http://www.w3.org/TR/xslt-xquery-serialization-30/#serparams-in-xdm-instance > we always resisted making the serialisation attributes on xsl:output > dynamic (AVTs) I often wondered the same thing. Perhaps because none of our declarations have it? But we now have shadow attributes, which I think suffice. I think we should best resolve this by saying that: 1) For xsl:output, the parameter document must be part of the statically available documents and is retrieved using the same semantics as for the fn:doc() function. If the document is not part of the statically available documents, the result is an empty sequence / error. 2) For xsl:result-document, the parameter document is retrieved using a dynamic call on the fn:doc() function and follows the same semantics in terms of stability. This allows for proper precompilation of packages, as a processor can simply add the declarations statically for xsl:output (i.e., if the document is there at compile time, it does not have to be there at run time). It then works the same way as if someone had written (using his own format of parameter document): <xsl:output _method="{doc('settings.xml')/output/method}" /> -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 2 October 2015 13:13:21 UTC