This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The F&O spec indicates that in case there is no base uri parameter, and no base uri in the static context, and error should be raised: << The first form of this function resolves $relative against the value of the base-uri property from the static context. If the base-uri property is not initialized in the static context an error is raised [err:FONS0005]. >> The corresponding tests are not indicated as raising such an error: fn-resolve-uri-6 fn-resolve-uri-7 fn-resolve-uri-8 fn-resolve-uri-9 fn-resolve-uri-10 fn-resolve-uri-11 fn-resolve-uri-12 fn-resolve-uri-13 fn-resolve-uri-14 fn-resolve-uri-15 - Jerome
Jerome: I wanted to test function interaction for these tests. Rather than just expecting a message, I much rather change the test a bit to achieve the intended operation. Thanks, Carmelo
Jerome: Changed the tests as follows: fn-resolve-uri-6 to fn-resolve-uri-15 - Used the two argument version of the function. Resubmitted new results new tests. fn-resolve-uri-16 - left as is but changed it as a "runtime-error" test. Removed fn-resolve-uri-6.txt file and added code "FONS0005" as expected error. Please close the bug if in agreement and when able to verify. Thanks, Carmelo
Verified. Thanks, - Jerome