This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 30392 - [xslt30ts] package-021
Summary: [xslt30ts] package-021
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 Test Suite (show other bugs)
Version: Recommendation
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Abel Braaksma
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
Depends on:
Reported: 2019-01-15 22:27 UTC by Michael Kay
Modified: 2019-02-25 13:36 UTC (History)
0 users

See Also:


Description Michael Kay 2019-01-15 22:27:46 UTC
I believe the new test package-021 should raise an error. The situation exactly matches this Note in ยง3.5.2

It is not intrinsically an error to have two xsl:use-package declarations that identify the same package (or different versions of the same package). This has the same effect as having two declarations that identify packages with different names but identical content. In most cases it will result in an error ([see ERR XTSE3050]) due to the presence of multiple components with the same name; but no error would occur, for example, if the used package is empty, or if the two xsl:use-package declarations use xsl:accept to accept non-overlapping subsets of the components in the used package.

The same problem arises in package-022. Although xsl:accept is used to avoid a conflict on *:function1, there is still a conflict on *function2 which causes a clash as a result of being present via more than one use-package declaration.
Comment 1 Abel Braaksma 2019-02-25 13:36:57 UTC
The tests have been fixed (at least I hope I got it correct this time) and an inverse test has been added to test the mentioned error scenario.

The changes were committed to Mercurial.