intertwingly

As I recent posted there was a debate over Netscape’s decision to remove the DTD’s for older RSS types (0.9 and 0.91). One of the outcomes of this decision is that the feed validator will now give a warning if the DTD is linked to. The...

I’d submit that any use of any RSS variant that isn’t RSS 2.0 should be considered a “Common Feed Error”.

It would serve no purpose to declare that the Slashdot RSS feed (which happens to be valid RSS 1.0 and the authors assure me that they under no circumstances will ever support RSS 2.0) to be invalid.

Similarly, the authors of any of the other RSS variants have had ample opportunity to deprecate these other versions, yet not only have they declined to do so, in many cases they have publicly declared that they have no intention of doing so.

Finally, other than applications like the Validome feed validator, I know of none that would so much as raise an eyebrow if one were to put the value of pi to twelve significant digits into the version attribute.

Hi Sam,

I am a young french geek trying to push REST beyond but I have actually no connexion to any “pope” of the web software community

I’ve just summed up my ideas in a post called “Programming REST in REST” ([link]) and I wonder if you can take 5 minutes to decide if it’s just crap or an interesting lead to popularize (no code yet) through your smartly frequented blog.

Thanks,

Julien

Seen on a page linked to from the Common Feed Errors page:

XML Parsing Error: undefined entity
Location: http://intertwingly.net/blog/2004/05/28/detente/#Reuters
Line Number 6, Column 19:

<title>Sam Ruby: D&eacute;tente</title>
------------------^

The title of the link being, ironically, “Silent Data Loss.”

XML Parsing Error: undefined entity

Fixed.  Thanks!