2104 2005-09-09 14:48:14 +0000 parts-queries-results-q1 can fail 2005-11-03 08:25:38 +0000 1 1 1 Unclassified XML Query Test Suite XML Query Test Suite 0.6.0 PC Windows XP CLOSED FIXED P2 normal --- 1 marc.van.cappellen carmelo oldest_to_newest 6018 0 marc.van.cappellen 2005-09-09 14:48:14 +0000 Following the static typing rules outlined in the Formal Semantics, we believe that static implementation will report XPTY0004. - in local:one_level, $p is statically typed as element() - $p/@partid is typed as attribute(partid, xs:anySimpleType)* - An implementation using the infoset mapping for fn:doc types $s/@partof as attribute(partof, xdt:untypedAtomic)* As a consequence, $s/@partof = $p/@partid should raise XPTY0004. 6977 1 carmelo 2005-10-31 20:36:01 +0000 Marc: I asked for Jonathan's input on the matter. He wrote the use cases and is quite well versed on the use cases. Thanks, Carmelo 6982 2 jonathan.robie 2005-11-01 14:39:34 +0000 I agree with Marc. So how do we process this? At the very least, our test suites should allow static implementations to raise this error. We might want to fix this in the use cases document and think about when to republish, since we probably want the use cases to match the test suite and we probably don't want to penalize anyone for supporting static typing. 6984 3 carmelo 2005-11-01 15:07:59 +0000 Mark/Jonathan: I can go ahead and change the test case entry in the catalog file to allow for a static error as well. Just need to think. How to set the scenario (standard or parse-error). Thanks, Carmelo 6987 4 carmelo 2005-11-01 16:14:57 +0000 Agree. Test case entry in catalog was changed to allow for an alternate error to be raised. This may be a temporary solution if the use case gets changed. Thanks, Carmelo 7001 5 marc.van.cappellen 2005-11-03 08:25:38 +0000 This resolution is satisfactory, change state to closed.