Lists Home |
Date Index |
- From: firstname.lastname@example.org
- To: email@example.com
- Date: Mon, 5 Apr 1999 19:09:32 +0100
I'm beginning to get some insight in the DOM specs, nevertheless some
points still seem dark to me:
I would really appreciate if some one could illuminate myself (and others
interested maybe) on the following points.
Can an attribute have more than one entity reference as a child?
What should a DOM implementation behave like if a DOM user appends to an
Attr node an unexpanded
entity reference that contains Element nodes as child ? In other words is
it true that if an entity
reference is appended to an Attr node, it can contain only Text nodes as
Can an Attr node have non null value and, at the same time, no Text
When cloning an Attr node with deep set to false, does the cloned Attr node
attribute value? In this case should it also have a Text child? So, if the
attribute had its value splitted among several Text child nodes, the cloned
will contain only one text child holding the attribute value? Or is all
specific (irrelevant to the DOM specs)?
What should the getOwnerDocument method return for an Entity node (or for a
Notation or for
a DocumentType), as no createX method is specified in the Document
Form the DOM specs, the getOwnerDocument method should return null for a
Why wouldn't be better to return the Document node itself, as this (seems
to me) would
simplify a little bit implementation efforts (For example when checking the
of a Node when appending it as child of a Document node).
Thanks a lot.
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)