14342 2011-09-30 11:00:17 +0000 [QT3TS] functx-fn-namespace-uri-for-prefix-all 2012-05-31 12:23:05 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3 & XPath 3 Test Suite Working drafts PC Windows NT CLOSED FIXED P2 normal --- 1 tim oneil jim.melton mike oneil public-qt-comments oldest_to_newest 57557 0 tim 2011-09-30 11:00:17 +0000 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. 67834 1 oneil 2012-05-18 09:36:48 +0000 This bug was fixed on the 2011-10-07 by myself. 67879 2 tim 2012-05-18 14:33:38 +0000 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> 68017 3 oneil 2012-05-22 16:56:50 +0000 I will check this one. 68023 4 mike 2012-05-22 19:23:09 +0000 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.) 68033 5 oneil 2012-05-23 08:21:31 +0000 Bug fix: Removed space in the test result. 68405 6 tim 2012-05-31 12:23:05 +0000 Confirmed fixed. Thanks.