> I am arguing for a data model for XML. There is no
> conflict between having a data model for XML - so that we all know
> what the parsing *layers* do and emit - and having user defined
> vocabularies!
Sure, a data model is fine, and gives a basis for formalism.... I argued for
that in the DOM WG until I was blue in the face.
That said, few application deal with that model directly, and there are a
number of slants one can take. Editing applications, for example, really do
need to know about whitespace, attribute ordering, etc. etc. etc. where most
data processing applications don't.
