DOM Node.cloneNode()

[Don Park]

Tyler,

>The spec says:
>
>"The Attribute inherits the Node interface, which has a parentNode
attribute.
>This attribute is set to the Element associated with the attribute as an
>expedient way of getting from the attribute to the Element. Note: In XML,
the
>value of an attribute is represented by the child nodes of an attribute
node,
>since the value can be contain entity references. Thus, attributes which
contain
>entity references will have a child list containing both text nodes and
entity
>reference nodes. In addition, tokenised attribute types, such as NMTOKENS
will
>result in a child list where each child represents a single token from the
>attribute value."


Please read the just recently released Proposed Recommendation version of
the DOM spec which says:

"DOM Attribute objects inherit the Node interface, but since they are not
actually child nodes of the element they describe, the DOM does not consider
them part of the document tree. Thus, the Node attributes parentNode,
previousSibling, and nextSibling have a null value for Attribute objects."

>>From a personal perspective, it would really suit the DOM much better if
you
>totally did away with the Node interface altogether and traverse the DOM
tree by
>element.  The other option would of course be to nest elements, text, PIs,
etc.
>inside a Node object just like you would with any basic tree
implementation.

I don't think we are on the same page.

Best,

Don Park



xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)