- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 05 Oct 2006 23:22:46 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3808 Summary: Constr-namespace-13.xml seems to missing namespace undeclaration Product: XML Query Test Suite Version: unspecified Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: XML Query Test Suite AssignedTo: andrew.eisenberg@us.ibm.com ReportedBy: per@bothner.com QAContact: public-qt-comments@w3.org Test Constr-namespace-13 results in either err:XQST0085 if XML Names 1.1 is not supported or Constr-namespace-13.xml is XML Names 1.1 is supported. The latter file consists of: <foo:elem xmlns:foo="http://www.example.com/parent"><child/></foo:elem> Shouldn't the child include the namespace unclaratation attribute as in: <foo:elem xmlns:foo="http://www.example.com/parent"><child xmlns:foo=""/></foo:elem> I'm not sure if this is required by a literal reading of the Spec, but it seems implied by "A namespace binding is created for each namespace that is declared in a namespace declaration attribute of an enclosing direct element constructor and not overridden by the current element constructor or an intermediate constructor". This does lead to the question of the behavior of fn:in-scope-prefixes and fn:namespace-uri-for-prefix for the child node. I would assume the former should return ("foo", "xml") and the latter should map "foo" to "".
Received on Thursday, 5 October 2006 23:22:55 UTC