- From: <bugzilla@jessica.w3.org>
- Date: Tue, 21 Jun 2016 22:46:37 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29381 Abel Braaksma <abel.braaksma@xs4all.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #7 from Abel Braaksma <abel.braaksma@xs4all.nl> --- For sake of reference, let me add the rationale of this decision. The reason we dropped this test case is that the WG concluded that the RFC-3986 we reference in the spec is too vague in this respect to create a reliable test-case for fn:resolve-uri with a URN. It was recognized that a strict following of the algorithm in sections 5.2.1 and 5.2.2 of RFC-3986 would allow using fn:resolve-uri with a URN without raising an error. However, it was also recognized that it didn't make sense to use fn:resolve-uri without hierarchical URIs. While RFC-3986 is written in such away to remove the differences between hierarchical and non-hierarchical URIs, we decided that a base URI that is not hierarchical is allowed to raise this error. Since both raising an error and returning a result based on the algorithm of 5.2.2 are both allowed, it was considered senseless to keep the test. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 21 June 2016 22:46:41 UTC