4173 2007-01-09 18:38:54 +0000 [UPD] Namespace binding clash 2007-05-04 21:27:03 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Update Facility Working drafts PC Linux CLOSED FIXED P2 normal --- 1 john.snelson andrew.eisenberg public-qt-comments oldest_to_newest 13390 0 john.snelson 2007-01-09 18:38:54 +0000 In various places the XQuery Update specification updates the namespace bindings for a given element. However, no mention is made of the case when a given namespace prefix is already bound to a namespace URI, and cannot be removed since it is in use by another attribute or the element itself. I would suggest that either this is an error case, or that the inserted or modified node should adopt a new application generated prefix. 13977 1 chamberl 2007-02-13 18:44:01 +0000 John, Thanks for your comment, which was discussed by the working group on 13 Feb 2007. The working group agrees with your comment. In the next draft of the specification, error conditions will be identified whenever an updating expression would generate a namespace binding that conflicts with an existing binding of the same prefix. New error codes XUDY0023 and XUDY0024 will be defined for this purpose. When you have reviewed the changes in the next draft, if you are satisfied, please change the status of this bug to Closed. Regards, Don Chamberlin (for the Query Working Group) 14998 2 jim.melton 2007-05-04 21:27:03 +0000 A new draft of XQuery Update has been available and there has been no objection to the resolution of this bug. Because you are a member of the WG and have had the opportunity to review and object to the solution, but have not done so, we are marking the bug CLOSED.