- From: <bugzilla@jessica.w3.org>
- Date: Tue, 09 Feb 2016 18:21:09 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29441 --- Comment #1 from Michael Kay <mike@saxonica.com> --- Suggested definition, and elaboration: [Definition: An extension function is a function that is available for use within an XPath expression, other than a function defined directly or by reference in this XSLT specification.] Extension functions typically are either defined by the implementer of the XSLT processor, or by a user using implementer-supplied APIs. The following are NOT classed as extension functions: core functions defined in [Functions and Operators 3.0]; additional functions defined in this XSLT specification; constructor functions named after an atomic type; stylesheet functions defined using an xsl:function declaration; XPath 3.0 inline functions; functions returned by (higher-order) functions such as load-xquery-module and random-number-generator. Functions returned as the result of evaluating a construct such as a named function reference or a partial function application or a call on function-lookup are classified as extension functions if the construct includes a reference to an extension function. NOTE: It is possible in principle for named extension functions to be present in the dynamic context even though they are not present in the static context, and vice versa. This can arise, for example, when the environment in which a stylesheet is executed differs from the environment in which it is compiled. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 9 February 2016 18:21:20 UTC