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 "uri" attribute for <source> elements should be absolute (according to the documentation). The following do not satisfy this rule. test suite bug ? URI id/SpaceBracket.xml should be absolute test suite bug ? URI id/HighUnicode.xml should be absolute test suite bug ? URI id/HighUnicode2.xml should be absolute test suite bug ? URI id/BCisInvalid.xml should be absolute test suite bug ? URI id/InvalidUmlaut.xml should be absolute test suite bug ? URI id/NamespaceSuppliedInternally.xml should be absolute test suite bug ? URI id/XMLIdDuplicated.xml should be absolute test suite bug ? URI id/InvalidXMLId.xml should be absolute test suite bug ? URI id/Books2.xml should be absolute test suite bug ? URI id/QObject.xml should be absolute test suite bug ? URI id/0x010D.xml should be absolute test suite bug ? URI id/builtinEntities.xml should be absolute test suite bug ? URI id/XMLIdWhitespace.xml should be absolute test suite bug ? URI id/XMLIdDuplicated.xml should be absolute test suite bug ? URI id/InvalidXMLId.xml should be absolute
I'm inclined to push back on this. If the URIs for documents accessed using doc() are always absolute, then how do we test that doc() accepts a relative URI? I think we should say instead that if the URI is relative, then it's interpreted as being relative to the base URI of the XML catalog file.
An acceptable fix would be to change the documentation. The only reason our test driver reports this problem is because the documentation says to expect absolute URIs.
I suggest to change the documentation to accept either relative and absolute URI.
The documentation has been updated as suggested.