Lists Home |
Date Index |
At 09:54 23/02/2003 -0800, Tim Bray wrote:
>Sean McGrath wrote:
>> >It's OK to define a custom language for your own purposes, but it's
>> not OK at all to use the term "XML" in
>> >describing it;
>>Basically every XML editor/ETL/database loader I have ever come across is
>>the XML 1.0 specification in some way or other.
>>The world is full of "xml parsers" that only support bits of XML 1.0.
>Etc... there's a word for these situations: "bugs". Bugs are a fact of
>life and we fix them and deal with them. When someone writes a
>specification for a potentially-very-important software library and writes
>the bug into the definition, that's a different level of seriousness. -
Unfortunately, it is also a well known fact of life that some "bugs" are
never intended to be fixed - they are just unimplemented
How much of ANSI C++ does your average C++ compiler support? At what point
does it cease to be
a "C++ compiler" because of bugs/omissions? At what point does an XML
parser cease to be that because
As I said before, if we applied a draconian interpretation (which I think
would be great for interoperability), I wonder
how many of our favourite tools would be left standing?
The sad reality about standards is that all "standards" are just lunes on
XML is no different.
XML is just as much a state of mind as any other standard:-)
Actually, SGML was probably different. It allowed you to be 100% compliant
but leave out pretty much everything :-)