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 29169 - [QT3TS] functx-fn-resolve-uri-5
Summary: [QT3TS] functx-fn-resolve-uri-5
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3 & XPath 3 Test Suite (show other bugs)
Version: Last Call drafts
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: O'Neil Delpratt
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-02 08:24 UTC by Michael Kay
Modified: 2015-10-02 11:17 UTC (History)
1 user (show)

See Also:

Attachments

Description Michael Kay 2015-10-02 08:24:00 UTC 
In test set app-FunctxFn test case functx-fn-resolve-uri-5:

The query is 

resolve-uri( '', 'http://datypic.com')

The expected result is

http://datypic.com

I believe that the following result is acceptable

http://datypic.com/

Reasoning:

We refer to RFC 3986 (section 5 is relevant)

Section 5.2.1 says: The base URI (Base) is ... parsed into the five main components described in Section 3.

This gives (scheme:"http", authority: "datypic.com", path: (empty))

Section 5.2.1 further says: "Normalization of the base URI, as described in Sections 6.2.2 and 6.2.3, is optional."

Section 6.2.3 is about scheme normalization, and says "In general, a URI that uses the generic syntax for authority with an empty path should be normalized to a path of "/"

The F+O spec for resolve-uri() says: "Where the cited RFCs permit variations in behavior, so does this specification."
Comment 1 Michael Kay 2015-10-02 08:28:46 UTC 
Note, this also affects the result of functx-fn-resolve-uri-all which includes the same test.
Comment 2 Tim Mills 2015-10-02 09:37:24 UTC 
Agreed.
Comment 3 Michael Kay 2015-10-02 11:17:30 UTC 
Fixed as suggested.