This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
As a result of bug 10004 the definition of when to raise FODC0002 vs FODC0004/0005 was changed. The following tests use valid URI values, and so should expect the error FODC0002 and not FODC0004: fn-collection-2 uses the URI: "thisfileshouldnotexists" fn-collection-3 uses the URI: "invalidURI<>" K2-SeqCollectionFunc-1 uses the URI "http:\\invalid>URI\someURI" I believe these are all valid URIs, as Schema states: The ·lexical space· of anyURI is finite-length character sequences which, when the algorithm defined in Section 5.4 of [XML Linking Language] is applied to them, result in strings which are legal URIs according to [RFC 2396], as amended by [RFC 2732]. and so, for example "invalidURI<>" is equivalent to "invalidURI%3C%3E" and "http:\\\\invalid>URI\\someURI" is equivalent to "http:%5C%5Cinvalid%3EURI%5CsomeURI". Either the expected error for these tests should be changed to FODC0002 or the tests should be changed to use URIs that are never valid (for example "%gg"). I believe the former fix is best for fn-collection-2 and the latter for the other two tests.
The XML Query and XSL WGs made their decision on Bug #10004 on 2010-10-19. I've made the changes that you requested in your final paragraph: fn-collection-2 expects FODC0002 fn-collection-3 now uses the URI "invalidURI%gg" K2-SeqCollectionFunc-1 now uses the URI "http:\\invalidURI\someURI%gg" Please close this bug report if you agree with these changes.