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

[Bug 29830] [FO31] Unclear what happens w.r.t. backwards / forwards compatibility in fn:transform

From: <bugzilla@jessica.w3.org>
Date: Tue, 20 Sep 2016 18:42:44 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29830-523-ENTXoEqSaL@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29830

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
I think the intended behaviour is:

* you request a processor that is an implementation of a specific version of
XSLT using the xslt-version option, which defaults to the version attribute of
the top-level stylesheet module/package. Let's say the version you request is
V.

* the system gives you a processor that supports that version or a higher
version, say W.

* the processor then goes into forwards or backwards compatibility mode based
on the rules of XSLT version W, for example if W = 3.0 and the stylesheet
specifies version = 1.0 then it goes into backwards compatibility mode; if W =
2.0 and the stylesheet specifies version 3.0 then it goes into forwards
compatibility mode.

I agree that this could usefully be clarified in the spec. (I think that this
is essentially editorial)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 20 September 2016 18:42:51 UTC

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