- From: <bugzilla@jessica.w3.org>
- Date: Tue, 23 Oct 2012 20:04:05 +0000
- To: public-qt-comments@w3.org
- Message-ID: <bug-19655-523-JJwKELMRRy@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19655 --- Comment #3 from Michael Kay <mike@saxonica.com> --- It's universal practice throughout the test suite to label tests as say XQnn if they are known to require an exact version and XQnn+ if there is a reasonable expectation that they will run on future versions also. At present the ONLY backwards incompatibility between XQuery 1.0 and 3.0 is that XQuery 3.0 will not run a query that specifies 1.0 in its version declaration. I've raised a bug against that because it seems absurd that the only backwards incompatibility should be such an unnecessary one. However, if it remains WG policy for version numbers to work this way, then users who want their queries to be forwards compatible will be well advised not to include a version number in the prolog, and the same goes for tests in the test suite. Meanwhile, we have to take a punt on whether our queries are likely to run under 3.1 or not. There is no way of knowing, so we have to guess, and I think it's better to make the same guess everywhere, which is that they will run under future versions. It's easier to change it across the board if we have made the same policy decision across the board. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 23 October 2012 20:04:06 UTC