[Bug 24970] Non-contextual function calls definition misinterprets the Core functions definition

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24970

--- Comment #2 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
Tony Graham wrote on the XSL list[1] about another spot in the spec where the
term core functions were not used correctly:

The 'Statically known function signatures' are[2]:

   The core functions defined in [Functions and Operators],
   together with the functions element-available,
   function-available, type-available, and system-property
   defined in this specification, plus the set of extension
   functions that are present in the static context of
   every XPath expression (other than a use-when expression)
   within the content of the element that is the parent of
   the use-when attribute.


I suggest we remove "defined in [Functions and Operators], because the
definition in Core Functions is wider than that (it also includes map functions
defined in the XSLT spec).


----------------------------
NOTE: for reference and historical accuracy, at the moment that I write this,
the definition of Core Functions [3] has been updated in the internal draft to
the following (it used to only include the standard fn namespace):

"[Definition: The core functions are: functions specified in [Functions and
Operators] in either the standard function namespace or the namespace
http://www.w3.org/2005/xpath-functions/math; plus functions defined in this
specification in namespace http://www.w3.org/2005/xpath-functions/map.]"



[1] Tony's question and my answer: http://markmail.org/message/tpsdbz2tzh3bzbqi
[2] https://www.w3.org/TR/xslt-30/#static-expression
[3] http://www.w3.org/TR/xslt-30/#dt-core-function

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 26 March 2014 18:33:34 UTC