Karl Dubost wrote:
...
# PRODUCING BROKEN XML
The fact is that many atom feeds are broken for many reasons.
* edited by hand
* created by templating tools which are not XML producers
* mixing content from different sources (html, db, xml) with different
encodings
It means when designing an atom feed consumer, implementers are forced
to recover the broken content to be able to make it usable by the crowd
(social impact). Second part of the postel laws "Be liberal in what you
accept".
...
Are you *really* sure about that? My understanding is that there are
popular Atom consumers that require proper XML (except for the RFC3023
issue), and that falling back to handle broken XML is actually not
needed (opposed to RSS).
BR, Julian