- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 11 Jan 2007 20:10:12 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3808 andrew.eisenberg@us.ibm.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |INVALID ------- Comment #1 from andrew.eisenberg@us.ibm.com 2007-01-11 20:10 ------- I interpret our specifications differently than you have, Per. The first bullet of section 3.7.1.2, Namespace Declaration Attributes, says: "If the namespace URI is a zero-length string and the implementation supports [XML Names 1.1], any existing namespace binding for the given prefix is removed from the in-scope namespaces of the constructed element and from the statically known namespaces of the constructor expression." So, if XML Names 1.1 is supported, then foo:elem contains a binding for foo and child does not contain a binding for foo. In section C.3, Serialization Parameters, XQuery says that the value of the undeclare-prefixes serialization parameters is "no". In section 5.1.7, XML Output Method: the undeclare-prefixes Parameter, of Serialization, we say: "If the undeclare-prefixes parameter has the value no and the output method is XML or XHTML, then the undeclaration of prefixes MUST NOT occur." For these reasons, I believe that the test case result is correct. Please close this bug report if you agree with this resolution.
Received on Thursday, 11 January 2007 20:10:17 UTC