<?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: On Ignorant Feed Handling</title>
	<atom:link href="http://decafbad.com/blog/2006/03/26/on-ignorant-feed-handling/feed" rel="self" type="application/rss+xml" />
	<link>http://decafbad.com/blog/2006/03/26/on-ignorant-feed-handling</link>
	<description>It's all spinning wheels and self-doubt until the first pot of coffee.</description>
	<pubDate>Fri, 21 Nov 2008 01:15:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-beta3-9771</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dave Johnson</title>
		<link>http://decafbad.com/blog/2006/03/26/on-ignorant-feed-handling/comment-page-1#comment-9097</link>
		<dc:creator>Dave Johnson</dc:creator>
		<pubDate>Sun, 26 Mar 2006 18:40:20 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/2006/03/26/on-ignorant-feed-handling#comment-9097</guid>
		<description>&lt;p&gt;The MS Feeds API does some weird things because it tries to normalize the commonly used funky RSS elements like ,  and  to Microsoft Common Feed Format (based on RSS 2.0 and Atom 1.0). I do have some hope that they'll get that right in the end, but they're clearly not there yet. However, it's important to note that the Feeds API &lt;em&gt;does&lt;/em&gt; preserve that which it does not understand (such as iTunes, GeoRSS, extensions you add, etc.).&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>The MS Feeds API does some weird things because it tries to normalize the commonly used funky RSS elements like ,  and  to Microsoft Common Feed Format (based on RSS 2.0 and Atom 1.0). I do have some hope that they&#8217;ll get that right in the end, but they&#8217;re clearly not there yet. However, it&#8217;s important to note that the Feeds API <em>does</em> preserve that which it does not understand (such as iTunes, GeoRSS, extensions you add, etc.).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Aman</title>
		<link>http://decafbad.com/blog/2006/03/26/on-ignorant-feed-handling/comment-page-1#comment-9092</link>
		<dc:creator>Bob Aman</dc:creator>
		<pubDate>Sun, 26 Mar 2006 15:03:05 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/2006/03/26/on-ignorant-feed-handling#comment-9092</guid>
		<description>&lt;p&gt;I'd say FeedTools also falls into the "Ignore but Retain" model.  But I actually do translate into local data structures.  There are obvious limitations, yes, but since I also maintain the full original XML within the data structure, those limitations are largely defined by how much you care about what I chose to ignore.  The only really big problem comes in when you hit the generation methods, because of course, generation on such a data structure will ignore any elements that I don't explicitly include.  So you potentially get some silent data loss, though not unexpected data loss.  Although, I did also supply hooks into the generation code so that additional generation code could be inserted on the fly, so you're once again only limitted by what you actually needed to support.  The only person who really loses out is the guy down the line if you republish stuff.  And 99% of the time, he's not going to care so long as you give him the important stuff.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;d say FeedTools also falls into the &#8220;Ignore but Retain&#8221; model.  But I actually do translate into local data structures.  There are obvious limitations, yes, but since I also maintain the full original XML within the data structure, those limitations are largely defined by how much you care about what I chose to ignore.  The only really big problem comes in when you hit the generation methods, because of course, generation on such a data structure will ignore any elements that I don&#8217;t explicitly include.  So you potentially get some silent data loss, though not unexpected data loss.  Although, I did also supply hooks into the generation code so that additional generation code could be inserted on the fly, so you&#8217;re once again only limitted by what you actually needed to support.  The only person who really loses out is the guy down the line if you republish stuff.  And 99% of the time, he&#8217;s not going to care so long as you give him the important stuff.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
