27140 2014-10-23 10:15:31 +0000 [xslt3ts] match-144 2015-05-06 21:16:28 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Test Suite Working drafts PC All CLOSED FIXED P2 normal --- 1 mike abel.online abel.braaksma public-qt-comments oldest_to_newest 113636 0 mike 2014-10-23 10:15:31 +0000 In test match-144 there are two template rules that match the same node: <xslt:template match="element(*, pre:partNumberType)"> and <xslt:template match="element(*, pre:partIntegerUnion)"> This is because partIntegerUnion is a union type with partNumberType as one of its members. The test results are assuming that pre:partNumberType will match. But in fact the match is ambiguous, so the later rule in document order should be taken. This test demonstrates an incompatiblity between 3.0 and 2.0, caused by changes to the handling of unions in the XPath 3.0 type rules. I propose to resolve it by adding priorities to the rules. 113637 1 mike 2014-10-23 10:18:22 +0000 Also affects tests match-145, match-164, and match-169. Possibly also, subject to confirmation, match-211. 113640 2 mike 2014-10-23 12:11:34 +0000 The situation with match-211 is (as suspected) different. I think the expected results are correct; Saxon was getting them wrong because of a bug (failing to recognize a Union type V as being derived-from U when V is derived from U by restriction.) 118725 3 mike 2015-03-20 15:19:15 +0000 I believe these tests have been fixed in cases where a fix was needed. 120174 4 abel.braaksma 2015-05-06 21:16:28 +0000 Was resolved > 30 days ago, closing.