This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
From thread "modules binding the xml/xmlns prefix" on the public-qt-comments list: <quote> 4.12 Namespace Declaration specifies that it is not allowed to redeclare the xml and xmlns prefix(XQST0070). A module declaration also allows an namespace binding to be done: "In the statically known namespaces of the library module, the namespace prefix specified in the module declaration is bound to the module's target namespace". I don't see what makes it invalid to do for example "module namespace xml = 'example.org/ns';". </quote> In other words, from what I can tell there is none which says XQST0070 should be raised if the code "module namespace xml = 'example.org/ns';" is encountered. Jonathan Robie added: <quote> I think we say this clearly in "4.12 Namespace Declaration", but in several other parts of our spec where we create namespace bindings, we do not refer to section 4.12, and do not state that the same error conditions apply. </quote> One way could be to not "duplicate" specifying namespace declaration, but to, in the case of module declaration, state that it is module declaration /plus/ a namespace declaration, and then map it into 4.12 Namespace Declaration such that 4.12 takes care of all namespace related. Frans
Frans, On 14 March 2006, the Query Working Group agreed to add a reference to error code XQST0070 to the sections on Module Declaration, Schema Import, and Module Import. All these sections bind namespace prefixes. None of them will be permitted to bind the prefix xml or xmlns, or to bind another prefix to the namespace associated with the prefix xml. I have marked this Bugzilla entry as "Fixed". If this resolution is acceptable to you, please change the status of this entry to "Closed". If you take no action the working group will close this entry at the end of March. Regards, Don Chamberlin (on behalf of the Query Working Group)
Nice work. I'm satisfied with the resolution and therefore change the status to CLOSED. Regards, Frans
Frans: There is already a test to evaluate this condition in the test suite. Thanks, Carmelo
Just to clarify in case Carmelo's comment seems out-of-place in this closed bug report; Carmelo is probably referring to the issue in ACTION TTF-066-05. I'm taking that up on member-query-test@w3.org since I think it is more relevant there, as opposed to this report.