Lists Home |
Date Index |
Perhaps I'm atypical, but most of my XML data is based on (if not
>validated against) a DTD. If my DTD doesn't mesh with my data, it probably
>means that my data is wrong. Reports about the death of DTDs continue to
>be greatly exaggerated...
I use DTDs for their most excellent powerful, intuitive, consise,
extended regular expression notation. I eschew all the other stuff
heaped in there from the SGML days where possible. It is truly exasperating
to see *ML.org sites being created at a rate of knots and their drivers
getting all "deeply committed" to W3C XML Schema without thinking
through the implications. Especially for document-oriented XML applications.
I said it at the Orlando conference and I'll say it again here. If w3C schema
is so complex that you *need* tools to visualize it then its XML 1.0 syntactic
base will not save us from the clutches of proprietary tool vendors.
I want to own my own data. Thats why I use XML and semantic encoding where
possible. I also want to *own* my content models. Any technology that precludes
me popping my models into a text editor and grokking what is going on flies
in the face of my goals.
DTDs are not perfect, there are multiple alternatives, some better than
others for document-oriented XML applications.
I used to think that XML would finally break down what I always thought of as
an accidental divide between "data" and "documents".
It does appear to me now that the chasm is too wide for XML to cross. Our kids
will revisit this one mid-century.