<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.3.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: How not to do RSS</title>
	<link>http://www.barelyfitz.com/blog/archives/2006/07/12/396/</link>
	<description>Patrick Fitzgerald of BarelyFitz Designs</description>
	<pubDate>Wed, 09 Jul 2008 02:54:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.2</generator>
		<item>
		<title>By: pat</title>
		<link>http://www.barelyfitz.com/blog/archives/2006/07/12/396/#comment-5105</link>
		<dc:creator>pat</dc:creator>
		<pubDate>Thu, 13 Jul 2006 14:37:59 +0000</pubDate>
		<guid>http://www.barelyfitz.com/blog/archives/2006/07/12/396/#comment-5105</guid>
		<description>&gt; The brilliance is that it’s perfectly acceptable according to the RSS 2.0 specification.

According to the spec, the GUID is "a string that uniquely identifies the item"; however, these people are setting it to a random value each time the feed is retrieved. Since that's not really a GUID, it should not be provided.

The GUID seems perfectly fine for entry identification, but since it can be misused (as in this case) some RSS aggregators (like SharpReader) choose to deal with it in other ways.</description>
		<content:encoded><![CDATA[<p>> The brilliance is that it’s perfectly acceptable according to the RSS 2.0 specification.</p>
<p>According to the spec, the GUID is &#8220;a string that uniquely identifies the item&#8221;; however, these people are setting it to a random value each time the feed is retrieved. Since that&#8217;s not really a GUID, it should not be provided.</p>
<p>The GUID seems perfectly fine for entry identification, but since it can be misused (as in this case) some RSS aggregators (like SharpReader) choose to deal with it in other ways.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny</title>
		<link>http://www.barelyfitz.com/blog/archives/2006/07/12/396/#comment-5103</link>
		<dc:creator>Danny</dc:creator>
		<pubDate>Wed, 12 Jul 2006 23:27:28 +0000</pubDate>
		<guid>http://www.barelyfitz.com/blog/archives/2006/07/12/396/#comment-5103</guid>
		<description>The brilliance is that it's perfectly acceptable according to the RSS 2.0 specification. Duplicate items are unavoidable with (especially when aggregating from multiple sources) unless they are clearly identified. RSS 2.0 is totally sloppy on entry identification. But at least it's simple, eh?</description>
		<content:encoded><![CDATA[<p>The brilliance is that it&#8217;s perfectly acceptable according to the RSS 2.0 specification. Duplicate items are unavoidable with (especially when aggregating from multiple sources) unless they are clearly identified. RSS 2.0 is totally sloppy on entry identification. But at least it&#8217;s simple, eh?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scripting News Annex &#187; Scripting News for 7/12/2006</title>
		<link>http://www.barelyfitz.com/blog/archives/2006/07/12/396/#comment-5102</link>
		<dc:creator>Scripting News Annex &#187; Scripting News for 7/12/2006</dc:creator>
		<pubDate>Wed, 12 Jul 2006 18:25:34 +0000</pubDate>
		<guid>http://www.barelyfitz.com/blog/archives/2006/07/12/396/#comment-5102</guid>
		<description>[...] Patrick Fitzgerald sheds some light.&#160; [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Patrick Fitzgerald sheds some light.&nbsp; [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
