This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The tests: eqname-001 eqname-002 eqname-003 eqname-004 eqname-005 eqname-006 eqname-007 eqname-008 eqname-009 eqname-010 eqname-011 eqname-012 eqname-013 eqname-901 eqname-902 eqname-903 expect XQST0031 when executed by an XQeruy 1.0 processor. However, they do not have a query version declaration.
I'm not sure what you are saying here. These tests are labelled either "XQ30+" or "XP30+ XQ30+". That means you shouldn't run them with an XQuery 1.0 processor. They therefore do not have an expected result when run with an XQuery 1.0 processor. I don't believe they require an XQuery version declaration, since an XQuery 3.0 processor assumes a version of "3.0"
Note that this is XQTS, not the new test suite. Here's an example. There's an expected-error for spec-version 1.0. The only way to get that error is to have a query declaration in the query and run in a processor not supporting 3.0. <test-case is-XPath2="false" name="eqname-001" FilePath="Basics/EQNames/" scenario="standard" Creator="Michael Kay"> <description>Use EQName as a step in a path expression</description> <spec-citation spec="XQuery" section-number="2" section-title="Basics" section-pointer="doc-xquery30-EQName"/> <query name="eqname-001" date="2010-03-16"/> <output-file spec-version="3.0" role="principal" compare="XML">eqname-001.out</output-file> <expected-error spec-version="1.0">XQST0031</expected-error> </test-case>
>Note that this is XQTS, not the new test suite. Sorry, I missed that. I don't know what we're doing about the XQTS test suite. I don't believe it contains anything of use that hasn't been migrated to QT3. Ideally we should probably roll it back to be a pure XQuery 1.0 test suite. Certainly, I don't think we should try and maintain both.
I am closing this bug issue as I believe QT1 is now obsolete and is not relevant in the new format of QT3 (see comment #1 and #3).