Lists Home |
Date Index |
- From: email@example.com
- To: Marcelo Cantos <firstname.lastname@example.org>
- Date: Sun, 07 Feb 1999 19:47:46 -0700
> Your comments give me the impression that this is unacceptable to you
> in the XML/heirarchical universe. You don't want DOM at any level.
> You insist on going straight to objects. It is not even good enough
> to build an object layer on top of the DOM layer. I find this a
> little implausible and hence am certain that you had something else in
> mind. Is it rather that you simply don't care what the underlying API
> is, that you are only interested in what happens at the object level?
I hope I'm not mis-representing Paul here, but as I've always read him (and
agreed), his point is that XML, and the various ancillary technologies such as
DOM and XML Schema, are more appropriate for content-exchange than for core
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
FourThought LLC, IT Consultants
Software engineering, project management, Intranets and Extranets
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)