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 should be: <any-of> <!-- supported --> <assert-false/> <!-- not supported --> <error code="XQST0120"/> </any-of> since there is not element declaration in a schema for element 'element'.
My intent while writing the test was actually: (validate lax { <element xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xsi:type="xs:integer">42</element> }) instance of element(*, xs:integer) So I fixed the three tests using this query accordingly. I think that otherwise a dynamic error XQDY0027 would be thrown, and I designed the test to succeed.
As a general rule, if we expect a test to produce different results depending on what features an implementation supports, we should not simply list all the results in an <any-of> - we should have different versions of the test with different dependencies, giving one expected result for each set of dependencies.
All prohibit/require-feature tests have now been split into supported/non-supported using the dependency tags, following your remark.
Please see Bug 19858.
I confirm this bug has been fixed
Thanks.