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 26753 - currneet-output-uri
Summary: currneet-output-uri
Status: CLOSED DUPLICATE of bug 26755
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 Test Suite (show other bugs)
Version: Working drafts
Hardware: PC Windows NT
: P2 minor
Target Milestone: ---
Assignee: johnlumley
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-08 09:27 UTC by johnlumley
Modified: 2014-09-08 13:07 UTC (History)
1 user (show)

See Also:


Attachments

Description johnlumley 2014-09-08 09:27:00 UTC

    
Comment 1 johnlumley 2014-09-08 09:42:23 UTC
current-output-uri-00[23] assert ends-with(/out,'fn/current-output-uri/results...') to check the determined output-uri for a normal and a result document. These locations are relative to the test sources, but the XTtest schema suggests that this might not be the correct location.

The documentation for assert-result-document/@uri states:

The uri corresponds to the URI used in the href [error in schema documentation - should be uri - jwL] attribute of the xsl:result-document instruction. It is supplied as a relative URI, interpreted as being relative to the implicit base output URI chosen by the test driver.

Hence it is possible (or even likely) that the outputs (and hence values) could be elsewhere.

A common alternative case might be where all results are held in a single separate file tree, such that:

current-output-uri-102:
<assert>ends-with(/out,'current-output-uri-002.xml')

current-output-uri-103:
<assert-result-document uri="second/current-output-uri-003.xml">
   <assert>ends-with(/out,'second/current-output-uri-002.xml')

These tests can be added as alternatives, but aren't particularly taxing.
I'll think about some more taxing possibilities.


[Sorry about the title spelling - finger trouble and hitting Ctrl-S too early]
Comment 2 johnlumley 2014-09-08 09:48:52 UTC
Closed to replace with a proper title !
Comment 3 Abel Braaksma 2014-09-08 13:07:12 UTC

*** This bug has been marked as a duplicate of bug 26755 ***