W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2013

[Bug 22911] [XSLT 3.0] Temporary Output State

From: <bugzilla@jessica.w3.org>
Date: Tue, 24 Sep 2013 16:33:51 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-22911-523-dQyxgPg0iG@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22911

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
We discussed various ways of reducing the inconvenience of the current
restrictions on xsl:result-document without reducing interoperability.

We're inclined towards adding an attribute (say deterministic="no") on
xsl:result-document whose effect is (a) to mean that it's not an error to use
it in temporary output state, and (b) to remove the restriction on writing to
the same URI more than once. The effect of setting this would, of course, be to
accept reduced interoperability - in effect xsl:result-document would then have
the same status as calls to side-effecting extension functions.

If temporary output state is retained then it should be extended to places like
xsl:merge-key. We could remove the restriction from xsl:attribute, xsl:comment
etc but there's not much point: it wouldn't benefit users. It's xsl:function
where the resl restriction lies.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 24 September 2013 16:33:53 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:53 UTC