- From: <bugzilla@jessica.w3.org>
- Date: Tue, 06 Jul 2010 14:51:08 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10089
John Snelson <john.snelson@marklogic.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |john.snelson@marklogic.com
--- Comment #2 from John Snelson <john.snelson@marklogic.com> 2010-07-06 14:51:07 ---
Thanks for your bug report - this is a personal response.
I agree that it's important to make XQuery and XPath 2.0 operators available as
functions, but I don't think these should necessarily be in the specifications.
Since these functions can easily be defined in XQuery or XSLT 2.0, I think
instead they would be better off defined in a standard EXPath module that can
be imported when needed. It is my intention to design such a module when XQuery
1.1 and XSLT 2.1 become nearer completion, should no one step up to do so
before me.
A few comments on your list:
set-product() - How would you represent the resulting sequence of pairs?
apply() - How would you represent the list of argument values?
filter() - This already exists in F&O 1.1
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 6 July 2010 14:51:09 UTC