Lists Home |
Date Index |
- From: "Bill la Forge" <email@example.com>
- To: <firstname.lastname@example.org>, "Marcelo Cantos" <email@example.com>
- Date: Sun, 7 Feb 1999 22:19:20 -0500
This seems similar to the conclusions I've reached. On the one hand,
most processes can be driven by a set of object created directly from
the SAX events, just using a filter or two to do the transformation.
On the other hand, when there is information which must alternately exist
as a set of application objects or an XML document, then the DOM
seems to be appropriate for modeling the structure of the document.
This is in addition to applications where navigating the document is
The proposal here is to have a common api, MDSAX or something like
it, which can serve as a framework for transforming XML into the appropriate
application objects; and to have a set of filters that plug into that framework
for creating a DOM, when appropriate.
(I have a new hammer. Forgive me if I experiment a bit with nails, screws,
pieces of wire, and thumb tacks. I'm not sure what the limits of this tool
are just yet.)
From: firstname.lastname@example.org <email@example.com>
>I don't think it makes sense to build a business-object model on top of DOM,
>but I do think it makes sense to define an exchange protocol that selializes
>objects to XML representations using DOM as a programmatic interface.
>Hopefully in this effort, one can leverage the support of such technologies as
>WDDX and XML-RPC, especially as they develop closer ties with other object
>technologies, including the locally much-maligned CORBA.
>I think it also makes sense to use the DOM to develop a user-interface layer
>for such objects, possibly using the same WDDX or XML-RPC mappings in
>association with a set of style-sheets (although this is just one of many
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)