DOMs and data models

[Paul Prescod]

Gavin Thomas Nicol wrote:
> 
> I actually think that syntax is independent of data model, and that
> it is not necessary for the API to directly reflect the data model.

I didn't say it should "directly" reflect the data model. I said that it
should reflect it. You use the word "expose" below. What's the
difference?

> A data model is essentially a set of data structures, and an algebra
> for manipulating them. How they are exposed through an API is largely
> and application dependent question, as is the syntax.

Fine. You seem to agree that you need the data model so that you can
"expose" it through an API and syntax. You can't expose something until
it exists.

I've heard a couple of DOM-developers say that now (here and in
private). Perhaps we can call a moritorium on adding features to the DOM
*until the underlying data models* "exposed" by the features have been
published through a W3C REC. How about it?

-- 
 Paul Prescod  - ISOGEN Consulting Engineer speaking for himself
"Ivory towers are no longer in order. We need ivory 
networks. Today, sitting quietly and thinking is the 
world´s greatest generator of wealth and prosperity."
 - http://www.bespoke.org/viridian/print.asp?t=140

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ or CD-ROM/ISBN 981-02-3594-1
Please note: New list subscriptions and unsubscriptions
are  now ***CLOSED*** in preparation for list transfer to OASIS.