Lists Home |
Date Index |
- From: "Hunter, David" <dhunter@Mobility.com>
- To: XML Developers' List <email@example.com>
- Date: Wed, 16 Jun 1999 10:59:39 -0400
David Megginson [mailto:firstname.lastname@example.org] writes:
> Paul Prescod writes:
> > I am genuinely interested in improving XML usability, however, so I
> > would like to hear counter-arguments.
> In my opinion, the best counter argument is that you can include
> structured documentation as part of the schema itself. In a DTD, an
> awful lot of useful information is stashed away in comments, and has
> to be copied into documentation using cut-and-paste.
> All the best,
If I could throw in a point which is scarily reminiscent of the DOM+CSS vs.
XSLT and XSL-FO debate, I'm a little worried that we're inventing two
languages which do exactly the same thing. Or rather, we've <em>got</em>
one language, and we're inventing <em>another one</em> to do the same thing.
Now in most cases, having multiple languages is a Very Good Thing. (e.g. I
happen to love C++, but use Visual Basic almost exclusively for what I do.
And I'm itching to use more Java, so I will when I get the chance.)
However, in this case, when Schemas become a recommendation are all XML
parsers going to have to know how to validate against DTDs as well as
Schemas? Are we going to have some parsers that only understand DTDs and
some that only understand Schemas? Are DTDs going to become obsoleted, if
Schemas can do everything they can do and more? If so, what happens to all
of the existing XML documents with DTDs? Do we re-write them?
Don't get me wrong, I happen to like Schemas much better than DTDs, and the
data typing alone makes them a better choice for many things. I'm just
wondering if we wouldn't be better off adding the extra functionality to
DTDs, instead of creating a new language. Are there technical reasons why
we can't? (Does it have something to do with SGML compatibility? If so I'd
be willing to shut up right now. :-)
MediaServ Information Architects
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/ and on CD-ROM/ISBN 981-02-3594-1
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)