This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This test assumes that URIs end up being percent encoded. e.g. <assert>/out/e3 = "true , http://base.example.org/ns/two%20organizations"</assert> Regarding resolve-uri, F&O 3.0 says "No percent-encoding takes place."
It looks like this, and related issues with resolve-uri do not fully adhere to this special case. I propose to go over the resolve-uri tests and improve and adjust where needed.
Thanks.
Fixed for the mentioned test-case, by s/%20/ /. There were no other escapes in this test-set that I could find and a trivial search elsewhere didn't come up with other tests that have the same issue. Marked resolved/fixed, changes pushed.
Reopening this, as the decision on this bug appears to contradict the decision on bug #20602, which I have reopened as a spec bug.
As discussed during the XSLWG telcon of 2015-10-15 this bug was re-assessed in light of bug 20602. Conclusion: the issue can be closed, there are no ambiguities with the QT30 test suite anymore.