OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: Default DTD URI

[ Lists Home | Date Index | Thread Index ]
  • From: Kay Michael <Michael.Kay@icl.com>
  • To: "'Sarveshwar Rao Duddu'" <duddu@vsnl.com>, Xmldev <xml-dev@xml.org>
  • Date: Mon, 10 Jul 2000 10:05:30 +0100

> The problem is like this: the server (accepting commands in XML) has a
> well - published DTD. So all documents sent by client must 
> conform to this.
> If the XML document contains ELEMENT or ATTLIST declarations, then the
> server will have to do extra job of checking whether that is 
> canonically equivalent to predefined DTD. 

I think this is a real problem, and I have in the past recommended against
using DTDs for validation for this reason. A validating parser checks that
the document conforms to whatever rules the sender wants it to conform to,
not that it conforms to the rules required by the recipient. Since DTDs are
only capable of expressing a small subset of the application-level validity
rules anyway, I've found it easier in practice to do all the validation at
application level. Perhaps I didn't try hard enough: there are parsers that
allow you to build a DOM, modify the doctype declaration to reference your
own DTD, and then validate against that. But I wanted to be
parser-independent, and SAX1 didn't even allow the application to discover
whether the parser was validating or not.

I'm hoping that XML Schemas will improve this situation, but it depends  on
how they are supported in products.

Mike Kay 

This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS