Re: Another issue

Dimitris raised the issue at the DOM teleconference an hour.

The current wording in the specification is clear regarding throwing
an exception or not.

[[
INUSE_ATTRIBUTE_ERR: Raised if newAttr is already an attribute of
another Element object. The DOM user must explicitly clone Attr nodes
to re-use them in other elements.
]]
http://www.w3.org/TR/2002/WD-DOM-Level-3-Core-20020114/core.html#ID-887236154

You can replace an Attribute node with itself with setAttributeNode, therefore
the failure of the Xerces implementation on the test is appropriate.

On the other hand, it is not clear if this operation is considered as
a "no-op" one or should behave like a normal setAttributeNode operation, i.e. fire 
the appropriate events, etc. With no objection, it was decided to not
consider it as a normal operation, therefore replacing an Attribute node with
itself is a no-op operation and "does nothing".

The same decision should be applied to setNamedItemNS.

Errata will follow soon.

Philippe