- From: <bugzilla@jessica.w3.org>
- Date: Tue, 06 Jul 2010 16:15:55 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10089 --- Comment #3 from dnovatchev@gmail.com 2010-07-06 16:15:55 --- (In reply to comment #2) > 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. The missing functions are among the *most important* XPath functions. They represent a significant hole in the current document. On the other side, the spec define a lot of less important functions -- just think how many date/date-time functions are there and how many people use date functions on a daily basis vs. such important functions as and(), or(), eq(), ... (any of the other missing functions). > 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. We don't need kludges, we need a clear and useful specification. The next step after recognizing the hole in the spec is to fill it in, not to delay or perpetuate it by avoiding responsibility and "delegating" the fix to another party. EXPath's goal is to provide useful *extensions* to existing specifications. This is not the case. In this case the specification needs to be fixed, not "extended". > 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. With all due respect, it is the task of the WG to create consistent and complete documents that do not immediately need to be patched. Dimitre Novatchev. -- 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 16:15:57 UTC