As a practical matter, DTDs are not just about validation. They cause a lot
other stuff to happen. In most cases, people who are not validating still
very much want it to be processed and want to know if anything goes wrong.
So don't get too tied up on DTDs being just a validation mechanism. Some
people think thats a bad thing, that DTDs aren't just about structural
validation, but that's the way it is. I know that, even if I don't need any
structural validation, I'd like default and fixed attributes to be
generated, for entity references to be recognized and expanded, notations
that I've defined to be recognized, ID/IDREF stuff to be checked, the types
of attributes to be checked against their definitions, etc... None of those
things are related to how many X's can be inside a Y, but they are all
driven by the DTD. And I don't necessarily want to have to do validation in
order to get these things to happen.
--------------------------
Dean Roddey
The CIDLib C++ Frameworks
Charmed Quark Software
[EMAIL PROTECTED]
http://www.charmedquark.com
"Why put off until tomorrow what you can
put off until the day after tomorrow?"
----- Original Message -----
From: "Bil Mason" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 26, 2001 11:39 AM
Subject: RE: PLEASE HELP: SAX parser errors on validation when ValScheme=V
al_Never?????
> I think I see what you are saying but I thought
> the whole point of Section 5 of the spec. was
> that skipping external entities would cause non-
> validating parsers to act differently than
> validating ones, possibly missing some well-
> formedness errors:
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
