DocumentFragment and load/loadXML

The Load and Save spec says that the DocumentLS interface will be
implemented by objects that currently implement document. The Level 1 Core
spec says:

DocumentFragment is a "lightweight" or "minimal" Document object. It is very
common to want to be able to extract a portion of a document's tree or to
create a new fragment of a document. Imagine implementing a user command
like cut or rearranging a document by moving fragments around. It is
desirable to have an object which can hold such fragments and it is quite
natural to use a Node for this purpose. While it is true that a Document
object could fulfill this role, a Document object can potentially be a
heavyweight object, depending on the underlying implementation. What is
really needed for this is a very lightweight object. DocumentFragment is
such an object.

Furthermore, various operations -- such as inserting nodes as children of
another Node -- may take DocumentFragment objects as arguments; this results
in all the child nodes of the DocumentFragment being moved to the child list
of this node.

Therfore, shouldn't the DocumentLS interface be implemented by
DocumentFragment objects also?

Thanks, Dominic.

Received on Thursday, 31 October 2002 09:31:34 UTC