[XML-DEV Mailing List Archive Home]
[Reply To This Message]
Re: Error and Fatal Error
- From: Stephen D Green <firstname.lastname@example.org>
- To: email@example.com
- Date: Mon, 18 Jul 2011 08:38:13 +0100
Thanks Liam, but it seems the spec also seeks to cater for the use case
where the conforming XML parser is used as a first step to repairing
errors, isn't it? It is in catering for this use case that there seems to me
to be a deficiency (as per my numerous postings in the rest of this thread
- apologies for that but it seems document-centric use cases somehow
cloud the issue, which I respect if it was the primary scenario of XML).
Stephen D Green
On 16 July 2011 23:26, Liam R E Quin <firstname.lastname@example.org>
On Sat, 2011-07-16 at 17:09 +0100, Stephen D Green wrote:An expert system could be used to try to determine what the user might
> It's a bane to developers that parsers regard errors in XML
> as fatal which need not be fatal, IMO.
have meant, but we wanted XML to be embeddable in small devices.
Programs like "tidy" can go a long way.
You'll find the C# compiler does that too, and so does javac and the C
> e.g. the .NET parser causes me grief when code falls over
> because of illegal characters
compiler and many others.
So if the Microsoft parser accepts attributes without quotes around
> So it would be better for future versions of XML (influenced
> perhaps by recent discussion related to MicroXML on this list)
> if the specs gave less of a push towards parsers regarding
> errors as fatal.
them,and the Sun^H^H^HOracle parser accepts </> as an erroneous way of
closing an element, and the libxml open source parser accepts a missing
> in <a><b<c>, how many XML documents will work in all three parsers?
The HTML5 approach was used for HTML 5 (duh) because the authors
basically only really care about 5 implementations. I'd be surprised if
there were fewer than 1,000 XML parsers, and many of them are in
situations where updates won't occur for many years - televisions,
aircraft navigation systems, shoes :-), washing machines, car
engines.... you name it. This is made possible because of reliable
On the other hand, if there's a groundswell _outside_ the Web browser
context, maybe we could say, e.g., xml documents starting
can contain errors, since older (all existing) processors will fail on
My own concern is rather more one of, how do we help people make
documents that don't contain errors in the first place more often.
More on that (I hope) at Balisage.
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
| [Thread Prev]
| [Thread Next]
| [Date Next]
| [Thread Index]
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format
Stylus Studio has published XML-DEV in RSS and ATOM formats,
enabling users to easily subcribe to the list from their preferred news reader application.
Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website.
they were not included by the author in the initial post. To view the content without the Sponsor Links please