Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] Validation - a history.

From: Gavin Thomas Nicol <gtn@----.--->
To: XML List Developers <xml-dev@-----.---.--->
Date: 3/2/2007 3:24:00 PM
On Mar 2, 2007, at 8:32 AM, Len Bullard wrote:

> 1.  The "NO DTD" crew lost.  There was too much experience with  
> DTDless
> systems at the time to let that happen.   The optional DTD crew won  
> because
> we had plenty of experience with that.

One side of that was that people found DTD's to be useful only at  
certain points in the process... during the production process a  
document is not always/seldom 'valid'. Market forces made them  
optional ;-)

> 2.  The cost of an SGML parser had already gone to zero by the time  
> the SGML
> ERB was formed.

I think that there were actually few, if any 'true' SGML parsers. The  
reality was that a significant number of SGML *subset* parsers  
existing that shared a fairly common set of features.

> Things improved as they will in a technology that is heavily used  
> and more
> people get a voice.  Speeches that justify the mistakes or the  
> triumphs at
> the expense of the pioneers don't help.

Very true, though it is useful to see everyone's perspectives on the  
battle for supremacy.


transparent
Print
Mail
Like It
Disclaimer
.

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 www.altova.com/list/index.html. 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.

.
.

transparent

transparent