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.