9879 2010-06-08 15:36:32 +0000 XQuery 1.1 tests have invalid XQueryX versions 2010-06-18 22:15:57 +0000 1 1 1 Unclassified XML Query Test Suite XML Query Test Suite unspecified PC Windows NT RESOLVED FIXED P2 normal --- 1 oliver andrew.eisenberg public-qt-comments oldest_to_newest 36045 0 oliver 2010-06-08 15:36:32 +0000 Consider test WhereExpr020: for $file in ($input-context//Folder)[1]/File where true() where false() return $file/FileName This has differing results for XQuery 1.0 and 1.1: <output-file role="principal" compare="Text" spec-version="1.1">WhereExpr020.txt</output-file> <expected-error spec-version="1.0">XPST0003</expected-error> However, an XQueryX version of this test exists which has two whereClauses in a flowrExpr. In XQueryX 1.0 the query does not conform to the XQueryX schema. Should schema validation errors be considered to be parse error for the purposes of running the test suite, or do we need some way to annotate that the XQueryX versions of the test only apply to XQueryX 1.1 processors? K2-WhereExpr-1 has a similar problem. K2-ExternalVariablesWithout-18 has an external variable with a default value which has also been translated to an invalid XQueryX 1.0 document. 36268 1 andrew.eisenberg 2010-06-18 22:15:57 +0000 The XML Query WG discussed this issue at its June 15 meeting. Before we added XQuery 1.1 test cases to the test suite, these test cases used scenario parse-error and no XQueryX documents were generated for them. For the purposes of testing XQueryX 1.0, a test harness may now skip the execution of a test case when: 1) the scenario is parse-error, or 2) an XQuery 1.0 expected error is XPST0003, or 3) the XQueryX document does not validate using the XQueryX 1.0 schema The Guidelines for Running the XML Query Test Suite will be updated to reflect the resolution of this issue. Please close this bug report if you agree with this resolution.