Lists Home |
Date Index |
- From: David Brownell <db@Eng.Sun.COM>
- To: XML Dev <firstname.lastname@example.org>
- Date: Fri, 06 Nov 1998 03:40:00 -0800
Paul Prescod wrote:
> David Brownell wrote:
> > To put it differently: is there really room for another API
> > to represent XML structure?
> > I tend to think that DOM, warts and all, is "good enough" for
> > most purposes. And for those other purposes, I suspect that
> > no standard API could suit.
> I find it odd that we can have "standard APIs" for the full complexity of
> relational data, and probably eventually for object database data, but it
> is perceived to be impossible to do the same for the parse tree of XML
> data. I mean it is just annotated tree structures: it shouldn't be rocket
> science (but neither is it trivial).
If it's just annotated tree structures, I'd say that's what DOM is for!
Or should be, warts and XML Data Model conformance aside.
Why would I say no "standard API" would exist for the rest? There are
thousands (conservatively!) of data/object models specialized to each
application. While a tree (or grove, or graph) would seem isomorphic
with any such model, it's not necessarily optimal for any one of them.
Similarly, "pure data" is a model many of us have been moving folk away
from over the last decade. It's critical for interoperability between
system components (e.g. over the web, with XML!), but raw data must be
joined with methods (or other code) before it's used. Ergo, "objects"
instead of APIs to data; classes not structs.
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/
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)