- From: <bugzilla@jessica.w3.org>
- Date: Sat, 31 Jan 2015 16:11:07 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27779 Andrew Coleman <andrew_coleman@uk.ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |andrew_coleman@uk.ibm.com Resolution|--- |FIXED --- Comment #3 from Andrew Coleman <andrew_coleman@uk.ibm.com> --- At the telecon on 2015-01-27, the working group decided to adopt the following wording as the resolution to this bug... [[ An XQuery version number consists of two integers separated by a dot. The first integer is referred to as the major version number; the second as the minor number. Any XQuery processor that implements any version of XQuery with a given major number MUST accept any query with the same major version number. The processor MAY reject queries labeled with a different major version number. The processor MAY reject queries with the same major version number and a greater minor version number than the processor recognizes. In all cases if a query is rejected because of a verison mismatch with the processor, error XQST0031 MUST be raised. Note: The processor MAY have an option to require that minor versions also match, or that the minor number of the version in the query is not larger than the largest minor version understood by the processor in this major release of XQuery, or to allow more permissve version matching, perhaps with warnings, but the behaviour is then outside the scope of this specification. ]] -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Saturday, 31 January 2015 16:11:08 UTC