4537 2007-05-04 23:35:45 +0000 [UPD] Section 3.1.11 upd:rename: Add well-formedness check for attribute duplicates 2007-06-15 21:04:16 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Update Facility Working drafts PC Windows XP CLOSED FIXED editorial P2 minor --- 1 mrys andrew.eisenberg public-qt-comments oldest_to_newest 15013 0 mrys 2007-05-04 23:35:45 +0000 Add well-formedness check for attribute duplicates. While upd:applyUpdates seems to check for it, other sections call it out. Make spec consistent. 15070 1 chamberl 2007-05-11 23:52:56 +0000 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 15072 2 mrys 2007-05-11 23:57:37 +0000 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. 15444 3 chamberl 2007-06-15 21:04:05 +0000 This editorial suggestion has been accepted and implemented. --Don Chamberlin (for the Query Working Group)