<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: I Hate RSS</title>
	<atom:link href="http://stuffthathappens.com/blog/2007/10/29/i-hate-rss/feed/" rel="self" type="application/rss+xml" />
	<link>http://stuffthathappens.com/blog/2007/10/29/i-hate-rss/</link>
	<description>Technology and Geek Stuff by Eric Burke</description>
	<lastBuildDate>Mon, 26 Jul 2010 14:36:32 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: cooper</title>
		<link>http://stuffthathappens.com/blog/2007/10/29/i-hate-rss/comment-page-1/#comment-691</link>
		<dc:creator>cooper</dc:creator>
		<pubDate>Tue, 30 Oct 2007 03:03:28 +0000</pubDate>
		<guid isPermaLink="false">http://stuffthathappens.com/blog/2007/10/29/i-hate-rss/#comment-691</guid>
		<description>As a Rome developer, thanks!

The problem here is really one of RSS -- there is no differentiation between entity-escaped HTML and plain text in any node, nor a certified XHTML content quality.

It does totally blow. Quite frankly, if you are using Rome Fetcher, we are already second guessing update times vs Last-Modified vs Etags vs TTL and UTF-8 vs Win-1251 encoding and a THOUSAND other things that people screw up all the time, even with Atom it is hard. Add to that (in my area) Apple and Yahoo not honoring capitalization or trailing &quot;/&quot;s in namespaces, and the number of workarounds in Rome grows to a truly horrendous level.

Rome does a best-fit guess well. If you need some additional code, I will gladly share some of my wrap arounds, but frankly, there are still just some shortcomings in the specs, and a MILLION bad feeds to try and deal with.</description>
		<content:encoded><![CDATA[<p>As a Rome developer, thanks!</p>
<p>The problem here is really one of RSS &#8212; there is no differentiation between entity-escaped HTML and plain text in any node, nor a certified XHTML content quality.</p>
<p>It does totally blow. Quite frankly, if you are using Rome Fetcher, we are already second guessing update times vs Last-Modified vs Etags vs TTL and UTF-8 vs Win-1251 encoding and a THOUSAND other things that people screw up all the time, even with Atom it is hard. Add to that (in my area) Apple and Yahoo not honoring capitalization or trailing &#8220;/&#8221;s in namespaces, and the number of workarounds in Rome grows to a truly horrendous level.</p>
<p>Rome does a best-fit guess well. If you need some additional code, I will gladly share some of my wrap arounds, but frankly, there are still just some shortcomings in the specs, and a MILLION bad feeds to try and deal with.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.462 seconds -->
