[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

XObject (was was was)

• From: "Bill la Forge" <b.laforge@j...>
• To: <xml-dev@i...>
• Date: Thu, 8 Oct 1998 14:30:17 -0400

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@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • Re: XObject (was was was)
    • From: Peter Murray-Rust <peter@u...>

• Prev by Date: ANNOUNCE - XML Europe '99 Call for Parti
• Next by Date: Re: More namespaces perversion
• Previous by thread: ANNOUNCE - XML Europe '99 Call for Parti
• Next by thread: Re: XObject (was was was)
• Index(es):
  • Date
  • Thread