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 expected result of this test in XQTS was: http://datypic.com/pre http://datypic.com/unpre http://datypic.com/pre but in QT3 is: |http://datypic.com/pre|http://datypic.com/unpre|http://datypic.com/pre The latter, I believe, is wrong. See Bug 11590.
This bug was fixed on the 2011-10-07 by myself.
The expected result does not match the one in XQTS. In QT3 it is: <assert-string-value> http://datypic.com/pre http://datypic.com/unpre http://datypic.com/pre</assert-string-value> To match XQTS it would be: <assert-string-value>http://datypic.com/pre http://datypic.com/unpre http://datypic.com/pre</assert-string-value>
I will check this one.
I agree, the result is wrong. It hinges on the first function call: namespace-uri-for-prefix('', $in-xml) The spec says: If $prefix is the zero-length string or the empty sequence, then if $element has a default namespace (that is, a namespace node with no name), the function returns the namespace URI of the default namespace. If $element has no default namespace, the function returns the empty sequence. The discussion on bug 11590 confirmed that the expected result here was an empty sequence, and therefore the expected result should not have the leading space. (There were many oscillations before we reached that conclusion, and it's quite likely that a change was made to the XQTS result after we did the conversion.)
Bug fix: Removed space in the test result.
Confirmed fixed. Thanks.