[Bug 27140] New: [xslt3ts] match-144


            Bug ID: 27140
           Summary: [xslt3ts] match-144
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0 Test Suite
          Assignee: abel.online@xs4all.nl
          Reporter: mike@saxonica.com
        QA Contact: public-qt-comments@w3.org

In test match-144 there are two template rules that match the same node:

<xslt:template match="element(*, pre:partNumberType)">


<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.

You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 23 October 2014 10:15:33 UTC