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


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: Does DTD validation work with namespaces?

[ Lists Home | Date Index | Thread Index ]
  • From: "Winchel 'Todd' Vincent, III" <winchel@mindspring.com>
  • To: xml-dev@lists.xml.org, Norman Walsh <ndw@nwalsh.com>
  • Date: Mon, 14 Aug 2000 11:16:15 -0400

/ "Winchel 'Todd' Vincent, III" <winchel@mindspring.com> was heard to say:
| I suggest to Marcus).  This would allow you to use elements from someone
| else's DTD without having to create one big DTD and you might also be able
| to take advantage of some of the Namespace features (defaulted prefixes,
| instance), which I can't see how you would do otherwise.

I don't think it's a problem to require the author who wants to mix
several DTDs together to build the compound DTD. It's pretty straight
forward, and it lets all of the existing machinery (modulo the namespaces
tweak) to work the way it does now:

  <!-- A DocBook/HTML DTD -->
  <!ENTITY % docbook PUBLIC "-//OASIS//DTD DocBook XML V4.1.1//EN"
                     "some system URI here">


  <!ENTITY % html PUBLIC "-//W3C//DTD XHTML V1.0//EN"
                     "some system URI here">

That's pretty short and easy to do.

This is not correct.  The problem --> Element collision.

Further, as more or more DTDs are developed, there will be more and more
element collision.

Classic example: An HTML <Table> and a furniture manufacturer's <Table>.

Consider the legal industry -- any document, from any source, can show up on
a lawyers desktop as a peice of evidence.  This means mixed namespaces.




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

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