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

[Bug 29374] fn:transform

From: <bugzilla@jessica.w3.org>
Date: Thu, 14 Jan 2016 10:15:15 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29374-523-Eox58ul0DD@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29374

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
Can't really comment on the name; these things happen. Some of us like short
names, some like long names, but we all hate meetings where a lot of time is
spent on deciding the best terminology. The function names evolved as their
specification evolved: the original idea was to have something that dynamically
executed a query, but we decided that dynamically loading a query and making
its functions available for execution was much more powerful, so the name
changed to reflect this.

I believe the current state of the conformance rules is that a query processor
is required to recognize the fn:transform function, but it is allowed to throw
a dynamic error if "no suitable XSLT processor is available". This means
queries can be made interoperable provided they are written using try-catch.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 14 January 2016 10:15:33 UTC

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