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 30417 - [XSLT30TS] id-043
Summary: [XSLT30TS] id-043
Status: NEW
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 Test Suite (show other bugs)
Version: Recommendation
Hardware: PC Windows NT
: 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-03-18 23:10 UTC by Abel Braaksma
Modified: 2019-03-18 23:10 UTC (History)
0 users

See Also:


Description Abel Braaksma 2019-03-18 23:10:32 UTC
This test uses, as part of the environment:

<source select="parse-xml('&lt;root/>')" role="." />

The documentation is clear that role="." means that it should be used as context item, but it is less clear on what happens when there's neither @file attribute, nor <content> element (and also @uri is absent).

Since the @select attribute is present, which is described as creating a subselection into whatever document is loaded by @file (or the <content> element) to serve as initial context item. If this subselection doesn't require a context node itself, there's no reason to force the use of @file or the <content> element.

However, I couldn't find this anywhere specified and this is the only test like this and I'm reluctant to introduce new functionality into the catalog just for convenience of a single test.

This parses correctly with my test-driver, but perhaps we should just:

* use either <content> or @file
* clarify this in the documentation
* create a test in the catalog-verification testset to ensure this