Lists Home |
Date Index |
- From: Rick Jellife <firstname.lastname@example.org>
- To: Mark Tucker <email@example.com>
- Date: Thu, 10 Sep 1998 16:24:13 +1000
Mark Tucker wrote:
> I was shocked to hear that namespaces invalidate validation.
This is only sort-of true.
> The problem seems to be that DTD validation does not expand
> prefixes, nor does it apply namespace defaulting.
DTD validation is completely namespace unaware. So no prefix expansion takes
place.Namespaces are a layer.
Namespace defaulting is superficially more disruptive to DTDs. It means that you
may indeed have two element types from different schemas which would (if you
used a single DTD to directly model them) have the same GI and content model.
Under these circumstances, the content model would tend to become ANY, of
course. But it is not really more disruptive: if you do not want to use
dont use it! Put a note in your products or documents saying "NO DEFAULTING"
and encourage people not to ue it.
At the moment, when you combine 2 DTDs, you have to rename element
types or combine content models. The namespace procedure does not alter this, so
even though it is superficially alarming, it is not much different from what
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)