- From: <bugzilla@jessica.w3.org>
- Date: Tue, 29 Aug 2017 15:37:59 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=30155
C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cmsmcq@blackmesatech.com
--- Comment #2 from C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com> ---
Perhaps replacing "query environment" with "XPath environment" would fix the
issue?
In the XQuery spec, we could either leave it at "query environment" or adopt
the same change, but one goal of the paragraph is (I think) to divide the
universe of functions into those defined by the XPath Functions spec, those
defined by users, those defined by the host language, and those defined by the
implementation, with "external function" covering host-language functions and
implementation-defined functions. If host-language functions are external,
then "outside the XPath environment" seems a clearer description, and has the
advantage of keeping the two definitions in synch. But the current text does
not seem impossible to keep, for the XQuery spec.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 29 August 2017 15:38:02 UTC