This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
"assert-eq" is the wrong assertion in the test cases below. I think asssert-string-value is probably what was intended. <test-case name="K2-SeqMAXFunc-6"> <description> Invoke fn:max() with an unsupported collation and one xs:anyURI value. </description> <created by="Frans Englich" on="2007-11-26"/> <test>max(xs:anyURI("str1"), "max://example.com/UNSUPPORTED_COLLATION")</test> <result> <any-of> <assert-eq>str1</assert-eq> <error code="FOCH0002"/> </any-of> </result> </test-case> <test-case name="K2-SeqMINFunc-5"> <description> Invoke fn:min() with an unsupported collation and one xs:anyURI value. </description> <created by="Frans Englich" on="2007-11-26"/> <test>min(xs:anyURI("str1"), "http://example.com/UNSUPPORTED_COLLATION")</test> <result> <any-of> <assert-eq>str1</assert-eq> <error code="FOCH0002"/> </any-of> </result> </test-case>
Changed the assertion to <assert-eq>xs:anyURI("str1")</assert-eq>