[jdom-interest] Internal DTD subset verification

[Elliotte Rusty Harold]

At 10:14 AM -0400 5/7/02, Alex Rosen wrote:
>>  if verification took place in the outputters
>
>The biggest problem with this technique would be that you don't find out
>about the problem until after the output stream has been created. E.g. if
>you're writing to a file, you'll be left with a zero-length or partial XML
>file on disk.
>

Or worse yet, in somebody else's database halfway around the planet. 
One can hope they're verifying on input, but you're never quite sure 
(which is why it pays to have multiple layers of verification, of 
course. In theory, all documents are well-formed. In practice, trust 
but verify :-)
-- 

+-----------------------+------------------------+-------------------+
| Elliotte Rusty Harold | elharo at metalab.unc.edu | Writer/Programmer |
+-----------------------+------------------------+-------------------+
|          The XML Bible, 2nd Edition (Hungry Minds, 2001)           |
|             http://www.cafeconleche.org/books/bible2/              |
|   http://www.amazon.com/exec/obidos/ISBN=0764547607/cafeaulaitA/   |
+----------------------------------+---------------------------------+
|  Read Cafe au Lait for Java News:  http://www.cafeaulait.org/      |
|  Read Cafe con Leche for XML News: http://www.cafeconleche.org/    |
+----------------------------------+---------------------------------+