DTD: Extra Complexity?

[Paul Prescod]

"Steven R. Newcomb" wrote:
> 
> Given that XML is supposed to be used on the Web, DTDs are certainly
> essential to XML's widespread success in enhancing opportunities for
> open information interchange in a multivendor context.
> 
> On the other hand, open DTDs are not good news for the ultra-dominant
> software vendors.  

I noticed something ominous in one of the Office 2000 products. It was
generating a schema on the fly for the data it was sending. "We know this
data conforms to this standard because we invented the standard to fit the
data."

If the person on the other end can't see the schema *in advance* then they
can't code software that works with the data. That's pretty much as bad as
not having a schema at all.

I don't want to say that generating a schema on the fly is ALWAYS bad. The
point should be that you should specify as much as you can in a static
schema, (or other formal specification). "Inline extensions" should be a
last resort and should be explicitly catered for in the static schema.
-- 
 Paul Prescod  - ISOGEN Consulting Engineer speaking for only himself
 http://itrc.uwaterloo.ca/~papresco

"Remember, Ginger Rogers did everything that Fred Astaire did,
but she did it backwards and in high heels."
                                               --Faith Whittlesey

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/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)