W3C home > Mailing lists > Public > public-qt-comments@w3.org > December 2016

[Bug 29990] [XSLT30] result documents in temporary trees and in patterns as a result of fn:transform calls

From: <bugzilla@jessica.w3.org>
Date: Thu, 01 Dec 2016 11:00:14 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29990-523-OCJ8FKWhQE@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29990

--- Comment #6 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
Update: the proposal in F&O Bug 29951, comment#11 removes the problem of
side-effects in temporary output state to an implementation-defined function.

The proposed solution is for fn:transform to call a function for each result
document, which itself can be defined as an option to fn:transform. This
function may or may not be implementation-defined and/or have side effects.

This in itself creates a peculiar situation: if called from an XSLT stylesheet,
that stylesheet will *not* be able to save the results through such function
(unless it uses implementation extensions), because a function call operates in
a temporary output state.

A workaround would be to write stylesheets that return all result documents as
part of the principal result.

Another workaround would be for XSLT to define an extra parameter for the
$options of fn:transform, for instance to define a template, named output
definition or mode, which receives the result. This would then in turn
"inherit" the output state the call itself is in.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 1 December 2016 11:00:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:03 UTC