Lists Home |
Date Index |
- From: "Bill la Forge" <firstname.lastname@example.org>
- To: "Bill la Forge" <email@example.com>, "Graham Moore" <firstname.lastname@example.org>, <email@example.com>, <firstname.lastname@example.org>
- Date: Fri, 2 Oct 1998 09:07:55 -0400
>From: Graham Moore <email@example.com>
>>I agree. Although I dont think we should think of processing documents. We
>>should view it more generally as invoking operations on an object model.
>If the Object tree has been constructed using application-specific
>classes, then the result can take an active role as an agent, rather than
>a passive role as a DOM.
Sorry for the ramblings. What I meant to say was that invoking operations
on an object model seems too narrow a scope. I like to think of the whole
thing as document- or net-centric processing, where the focus is on
the document or the network of interconnected documents.
I fee the oo-view has failed in several ways. When you try to address
security issues of mobile agents, you get into a real mess so long as
you are dealing with objects--data and logic require distinct security
models and need to be handled independently. Which makes sense
when you realize that Classes are often pervasive within a small
community, while the data is often transitory.
XML processing in the most general sense might be thought of as
combining data (from the document) with the logic of an application
to render some desirable result. Lately I've been thinking of awt
components and JavaBeans as the applicaiton logic, and having the
objects in the object tree be wrappers which serve to connect the
document contents to the application logic.
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/
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)