3281 2006-05-12 21:16:03 +0000 value-comparison-3 and value-comparison-4 without schema import 2006-07-06 13:06:25 +0000 1 1 1 Unclassified XML Query Test Suite XML Query Test Suite 0.9.0 PC Windows XP CLOSED FIXED P2 normal --- 1 marc.van.cappellen carmelo oldest_to_newest 9774 0 marc.van.cappellen 2006-05-12 21:16:03 +0000 For both value-comparison-3 and value-comparison-4 XPST0017 should be added as an alternate (negative) result. Implementations not supporting the optional feature Schema Import report XPST0017 as myType:hatsize() and myType:shoesize() are unknown functions. Thanks, Marc 9779 1 marc.van.cappellen 2006-05-12 22:24:57 +0000 And similar for the new 'UserDefined' tests: user-defined-1 user-defined-2 user-defined-3 user-defined-4 user-defined-5 user-defined-6 user-defined-7 user-defined-8 user-defined-9 user-defined-10 9793 2 andrew.eisenberg 2006-05-15 20:34:35 +0000 If an implementation does't recognized schema import, then it should raise err:XQST0009. Section 5.2.1, Schema Import Feature, of XQuery says: "If an XQuery implementation does not support the Schema Import Feature, it MUST raise a static error [err:XQST0009] if it encounters a schema import." 9796 3 marc.van.cappellen 2006-05-15 20:52:09 +0000 But the XQTS guidelines allow to substitute a "schema import" with a "namespace declaration". That's what our test harness does first of all. As such XQST0009 doesn't apply and XPST0017 is reported. Does this make sense? 9803 4 davidc 2006-05-16 09:56:48 +0000 (In reply to comment #3) > But the XQTS guidelines allow to substitute a "schema import" with a "namespace > declaration". That's what our test harness does first of all. > As such XQST0009 doesn't apply and XPST0017 is reported. > > Does this make sense? > This guideline of replacing schema import by a namespace declaration has been the cause of bug reports in just about every release of the test suite. I think that it would be __much__ better if this guideline were removed and tests that didn't really need the schema import were written to use a namespace declaration, and those that do need it were moved to test groups that explictly depend on schema import feature, so that they can be skipped cleanly by implementations not supporting that feature. David 9807 5 marc.van.cappellen 2006-05-16 19:04:43 +0000 +1 for David's suggestion Actually here are some more queries for which we have the same issue with one of our products. Either add XPST0017 or gor for David's approach. notation-cast-3 qname-cast-3.xq qname-cast-4.xq Thanks, Marc 9866 6 carmelo 2006-05-19 14:31:44 +0000 Marc/David: Thanks for raising this issue. After discussion at the testting task force, we agree that implementations are allowed to raise XPST0017 on these tests. An alternate error code was added to the test cases. Please close the bug if in agreement. We also decided not to change the guidelines at this point. Thanks, Carmelo 10401 7 Tom.Brosens 2006-07-06 13:06:25 +0000 We agree. Closing. Thanks, Tom.