Lists Home |
Date Index |
- From: Joe Lapp <email@example.com>
- To: firstname.lastname@example.org
- Date: Thu, 20 Nov 1997 16:43:27 -0500
"Mark L. Fussell" <email@example.com> wrote:
>[...] Object models describe the possible objects
>and structures that can exist in a system. [...]
>DTDs can describe some of this modeling information, but not particularly
>well and really only for a limited set of object models.
I do think that "object model" is too broad a term for what an SGML/XML
repository can accomplish. I think the SGML/XML repository offers a new
way of looking at objects. Clients may process SGML/XML constructs as
raw document information, or clients may process the constructs by
interpreting them (adding semantic value not provided by the repository).
I'm guessing that most clients that go about interpreting repository
data will create objects that contain those data, and those objects will
have behavior. We have a single object's data living as sibling objects
on many client machines. I'm guessing that these objects (instantiated
on client machines) will all have behavior and any other property we
ascribe to objects of an object model. The object model of an SGML/XML
repository is schizophrenic.
When we evaluate the capabilities of SGML/XML to support object models,
I think we need to take client behavior into account. The repository is
acting more like a file system for the state information of objects, and
the clients are more like applications that use the file system.
This seems like a different model for designing systems, and I wonder
how far we can take it.
Joe Lapp (Java Apps Developer/Consultant)
Unite for Java! - http://www.javalobby.org
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)