Altova Mailing List Archives

Re: [xml-dev] We need SAX features to say a parser supports XML

From: Elliotte Rusty Harold <elharo@-------.---.--->
To: John Cowan <jcowan@-------------.--->
Date: 10/25/2002 2:52:00 PM
At 10:14 AM -0400 10/25/02, John Cowan wrote:

>Read the errata page.

Oh joy. Another erratum that rewrites history because the working 
group changed its mind. Sorry. I don't accept such errata as 
normative. The spec is clear an unambiguous. There is no plausible 
argument that the original spec made a mistake. The people who wrote 
the spec knew what they were writing and why they were writing it. 
Now, retroactively, somebody's decided they were wrong, and they're 
going to fix it.

Sorry. This can't be done in an erratum. XML 1.0 says what it says. 
Parsers are designed around it. If you're going to change the BNF 
grammar, then you've invented a new language. XML 1.0 plus errata is 
no longer XML 1.0. It is provably true that

<?xml version="1.1"?><root />

is a well-formed XML 1.0 document.

| Elliotte Rusty Harold | elharo@m... | Writer/Programmer |
|          XML in a  Nutshell, 2nd Edition (O'Reilly, 2002)          |
|                  |
|  |
|  Read Cafe au Lait for Java News:      |
|  Read Cafe con Leche for XML News:    |


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.