XObject (was was was)

[Bill la Forge]

There seem to be a lot of problems with DOM:
    - an incomplete set of interfaces
    - excessive overhead for some applications.

But from the perspective of a component programming
environment, where each application object has a
peer member (or is a member) of the DOM tree,
there seems to be a big advantage:
    a standard navigation api.

So having a standard for converting an application-specific
document reference into application-specific elements of
a DOM tree means that we have decoupled the
application code from the tool that builds the DOM tree.

It also then creates a standard new kind of component--
an XObject, which could be a really good thing indeed
if they are easy to write.

Bill


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)