- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 30 Oct 2007 01:58:10 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5211 ------- Comment #9 from jim.melton@acm.org 2007-10-30 01:58 ------- In http://www.w3.org/Bugs/Public/show_bug.cgi?id=5211#c6, the assertion was made that "It's not as if there could ever be an XQuery 2.0 and XPath 3.0 Full-Text 1.0". I'm not as confident of that statement as the author of it is. I would be somewhat surprised if we were to go straight from Full Text version 1.0 for the current generation of XQuery/XPath to Full Text version 2.0 for XQuery 2.0 and XPath 3.0. To my way of thinking, the existing "1.0" is meant to imply that this is the first version applicable to the current generation (major version number) of the parent specs. On the other hand, it's only fair to point out that the Update Facility and its Requirements and Use Cases documents all call themselves "XQuery Update Facility 1.0", and NOT "XQuery 1.0 Update Facility 1.0". So, feeling mildly off center, I yield to the suggestion that we rename the document (and its Requirements and Use Cases documents!) to use the name "XQuery and XPath Full Text 1.0" (if there is a real consensus, then we might insert "Facility", "Extension", or "Brother-In-Law" before the "1.0"). (I note in passing that the Normative References in the Full Text spec spell the names of the Requirements and Use Cases documents incorrectly -- the final "1.0" is missing.)
Received on Tuesday, 30 October 2007 01:58:19 UTC