This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7975 - [XQTS] Test results with namespace URIs that are not URIs cannot be canonicalized.
Summary: [XQTS] Test results with namespace URIs that are not URIs cannot be canonical...
Status: RESOLVED DUPLICATE of bug 6868
Alias: None
Product: XML Query Test Suite
Classification: Unclassified
Component: XML Query Test Suite (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Frans Englich
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-20 10:22 UTC by Oliver Hallam
Modified: 2011-08-30 00:32 UTC (History)
3 users (show)

See Also:

Attachments

Description Oliver Hallam 2009-10-20 10:22:36 UTC 
The following tests contain namespace URIs that are not valid URIs in their results.

K2-DirectConElemNamespace-59
K2-DirectConElemNamespace-60
K2-DirectConElemNamespace-75
K2-DirectConElemNamespace-76
K2-DirectConElemNamespace-78
K2-DirectConElemNamespace-82
K2-DirectConElemNamespace-83
K2-DirectConElemNamespace-84
K2-DirectConElemNamespace-85
K2-CopyNamespacesProlog-1

In order to compare the results of these tests, the expected result documents should be canonicalized.  Unfortunately canonicalization is defined to raise an error in this case (where a namespace URI is not a valid absolute URI).
Comment 1 Oliver Hallam 2009-10-20 10:45:56 UTC 
Two more tests with the same problem:

K2-DirectConElem-47
K2-NamespaceProlog-13
Comment 2 Frans Englich 2010-03-15 09:34:55 UTC 
This report at least partly duplicates bug #6868. The problem is that these tests test valid syntax & semantics, which needs to be done. That it then fails in c18n, is a separate problem.
Comment 3 Michael Kay 2010-03-15 10:00:42 UTC 
>The problem is that these tests test valid syntax & semantics, which needs to be done.

See comment #12 of bug #6868.

I think our purpose is to test interoperability, and the state of the XML specs, taken as a whole, is such that there is no expectation of interoperability when invalid or relative URIs are used as namespace names. So we shouldn't use them in the public test suite.

Of course products will have their own rules on how such cases are handled, and will therefore need such tests in their private test suites, but that's a different matter.
Comment 4 Frans Englich 2010-03-15 13:54:20 UTC 

*** This bug has been marked as a duplicate of bug 6868 ***
Comment 5 Sorin Nasoi 2010-10-12 14:15:24 UTC 
I have added XQST0022 as an alternate result for tests:

K2-DirectConElem-47
K2-DirectConElemNamespace-59
K2-DirectConElemNamespace-65
K2-DirectConElemNamespace-75
K2-DirectConElemNamespace-76

because, as it was also mentioned by a comment for these tests, some processors MAY report the URI's as invalid.
Comment 6 Michael Dyck 2011-08-30 00:32:55 UTC 
Re the previous comment, see Bug 13966.