28335 2015-03-25 18:05:15 +0000 [XT30] test match-82a has wrong XSLT version and assumes different priority for parenthesized patterns 2015-05-06 21:19:02 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Test Suite Last Call drafts PC Windows NT CLOSED FIXED P2 normal --- 1 abel.braaksma abel.online mike public-qt-comments oldest_to_newest 118937 0 abel.braaksma 2015-03-25 18:05:15 +0000 According to the spec, parentheses are removed prior to assessing for default priority (internal current draft), this test assumes that the priority is different. Also, the test is written for 3.0, but the stylesheet has version 2.0. 118940 1 mike 2015-03-25 19:19:56 +0000 I think the test match-082 was originally written for XSLT 2.0, and was then forked because a 3.0 processor gives a different result. It's perfectly legal to run a stylesheet with version="2.0" with a 3.0 processor, and the results are well-defined. You're right that at some point the rules changed so that match="(doc|cod)" is now treated as a UnionPattern for priority purposes, which means the second template rule should be chosen in preference. I propose we simply change the expected results. 118943 2 mike 2015-03-25 22:14:15 +0000 Fixed the second problem. 118954 3 abel.braaksma 2015-03-26 12:16:57 +0000 We were both fixing the same test, but differently, I have merged the changes. 118955 4 abel.braaksma 2015-03-26 12:44:18 +0000 > It's perfectly legal to run a stylesheet with version="2.0" with a 3.0 > processor, and the results are well-defined. Yes, but if it tests backwards-compatibility, it should probably be placed in a different category. I split the test-case in three variants to cover the same-priority situation more clearly. 120184 5 abel.braaksma 2015-05-06 21:19:02 +0000 Was resolved > 30 days ago, closing.