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 file for Constr-namespace-13 requires XML Namespaces 1.1. The catalogue doesn't really warn of this (it has scenario="standard") Although I (think I could) use an XML Namespace 1.1 parser for the test suite, a more serious problem with this expected result file is that it assumes that namespace prefixes are undeclared on serialisation of query results but the test guidelines state that serialisation is performed with undeclare-prefixes no If this test was allowed to undeclare prefixes, to specifically test xml 1.1 features then a further problem is that it would be impossible to use the xml comparison as written as that depends on xml canonicalization, and thus on XPath 1, and so on XML 1.0. The supplied expected result file does not have a corresponding XPath 1 node set and so does not have a canonical form in the sense of http://www.w3.org/TR/xml-c14n It would seem that (at least) for those tests with a requirement for xml 1.1 they should be in an optional part of the test suite and with an xml 1.1-aware comparison method. Both the saxon and xq2xsl test harnesses (at least) don't use c14n but rather direstly compare the XDM trees using variants of deep-equal this would seem to be a natural way to avoid the problems that occur when you force the test to go via Xpath1 which can't capture all the features in an XPath2/Xquery data model. David
I have removed the undeclare of the namespace. As you point out, we specify that the value of undeclare-prefixes is "no". The expected result is now: <foo:elem xmlns:foo="http://www.example.com/parent"><child/></foo:elem> If you agree with this resolution, then please mark this bug as CLOSED.