This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Add well-formedness check for attribute duplicates. While upd:applyUpdates seems to check for it, other sections call it out. Make spec consistent.
Michael, I don't understand what you are requesting here. I don't see any sections (apart from upd:applyUpdates) that check for duplicate attribute names. Can you give me an example of a rule in some section that you think should be replicated in Section 3.1.11? (Note that upd:rename() can only rename a single attribute node, so there is no possibility of an internal name conflict within that primitive.) --Don Chamberlin
A rename could change the name of an attribute to a name that conflicts with an already existing name. The application of upd:applyUpdates() makes sure that this does not happen, but somebody who just reads the section on rename does not see that this check occurs. It would be useful to call it out editorially with a note that such checks will occur when we talk about the operation, and not only burry it deep down in the semantics.
This editorial suggestion has been accepted and implemented. --Don Chamberlin (for the Query Working Group)