[Bug 5629] [UPD] Namespace conflict when renaming attributes

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5629


mike@saxonica.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Namespace conflict when     |[UPD] Namespace conflict
                   |renaming attributes         |when renaming attributes




------- Comment #1 from mike@saxonica.com  2008-04-07 17:36 -------
I think this problem is actually rather more pervasive. Consider "rename",
where the new name of the element has the namespace binding (null, null) (that
is, no prefix, no namespace URI). The current rules imply that the namespace
binding (null, null) is added to the namespaces property of the element.
However, the namespaces property of an element should never contain such a
namespace binding: see the third bullet in XDM 3.3.3: "For every element node
whose name has no prefix, the element must have a a binding for the empty
prefix to the namespace URI of the element name, or must have no binding for
the empty prefix in the case where the name of the element has no namespace
URI." That is, the association (null, null) is represented by the absence in
the namespaces property of any binding of the form (null, X). 

So the action of "rename" in such a case should be to remove any namespace
binding of the form (null, X). And in practice this is a much more desirable
result, because it means that the updated document doesn't carry so many
obsolete and no-longer-used namespace bindings.

Received on Monday, 7 April 2008 17:37:26 UTC