<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: FeedLounge: Tagging and Renaming</title>
	<atom:link href="http://gfmorris.com/2005/06/11/feedlounge-tagging-and-renaming/feed/" rel="self" type="application/rss+xml" />
	<link>http://gfmorris.com/2005/06/11/feedlounge-tagging-and-renaming/</link>
	<description>The Life and Times of Geof F. Morris</description>
	<lastBuildDate>Thu, 11 Mar 2010 01:03:05 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: FeedLounge - FeedLounge development: feed validation</title>
		<link>http://gfmorris.com/2005/06/11/feedlounge-tagging-and-renaming/comment-page-1/#comment-4300</link>
		<dc:creator>FeedLounge - FeedLounge development: feed validation</dc:creator>
		<pubDate>Tue, 05 Jul 2005 05:00:58 +0000</pubDate>
		<guid isPermaLink="false">http://ijsm.org/?p=2055#comment-4300</guid>
		<description>[...] We have feeds being parsed, but we also wanted to help make the world a better place by allowing the end user to know whether or not the feed is valid. As Geof rightly points out, we MUST follow Postel&#8217;s Law when parsing feeds (&#8221;be conservative in what you do, be liberal in what you accept from others&#8221;). Why not give a quick heads-up to someone that might be able to help fix the problem? So, in FeedLounge, there is a banner near the item content that tells the user the feed is invalid. The user is given a link to click on to see for themselves what is wrong with the feed, using the service from feedvalidator.org. [...]</description>
		<content:encoded><![CDATA[<p>[...] We have feeds being parsed, but we also wanted to help make the world a better place by allowing the end user to know whether or not the feed is valid. As Geof rightly points out, we MUST follow Postel&#8217;s Law when parsing feeds (&#8221;be conservative in what you do, be liberal in what you accept from others&#8221;). Why not give a quick heads-up to someone that might be able to help fix the problem? So, in FeedLounge, there is a banner near the item content that tells the user the feed is invalid. The user is given a link to click on to see for themselves what is wrong with the feed, using the service from feedvalidator.org. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FeedLounge - FeedLounge development: feed validation</title>
		<link>http://gfmorris.com/2005/06/11/feedlounge-tagging-and-renaming/comment-page-1/#comment-4299</link>
		<dc:creator>FeedLounge - FeedLounge development: feed validation</dc:creator>
		<pubDate>Sun, 19 Jun 2005 20:31:05 +0000</pubDate>
		<guid isPermaLink="false">http://ijsm.org/?p=2055#comment-4299</guid>
		<description>[...] orld a better place by allowing the end user to know whether or not the feed is valid.  As Geof rightly points out, we MUST follow Postel&#8217;s Law when parsing feed [...]</description>
		<content:encoded><![CDATA[<p>[...] orld a better place by allowing the end user to know whether or not the feed is valid.  As Geof rightly points out, we MUST follow Postel&#8217;s Law when parsing feed [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dotnot</title>
		<link>http://gfmorris.com/2005/06/11/feedlounge-tagging-and-renaming/comment-page-1/#comment-4298</link>
		<dc:creator>dotnot</dc:creator>
		<pubDate>Mon, 13 Jun 2005 15:47:08 +0000</pubDate>
		<guid isPermaLink="false">http://ijsm.org/?p=2055#comment-4298</guid>
		<description>&lt;strong&gt;FeedLounge development: feed validation&lt;/strong&gt;

	Welcome to the second of a series of posts on the development.  If you missed the first one, check it out here: FeedLounge development: the parser.
	The feed validator
	We have feeds being parsed, but we also wanted to help make the world a better pla...</description>
		<content:encoded><![CDATA[<p><strong>FeedLounge development: feed validation</strong></p>
<p>	Welcome to the second of a series of posts on the development.  If you missed the first one, check it out here: FeedLounge development: the parser.<br />
	The feed validator<br />
	We have feeds being parsed, but we also wanted to help make the world a better pla&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://gfmorris.com/2005/06/11/feedlounge-tagging-and-renaming/comment-page-1/#comment-4297</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Sun, 12 Jun 2005 07:29:30 +0000</pubDate>
		<guid isPermaLink="false">http://ijsm.org/?p=2055#comment-4297</guid>
		<description>Funny, I heard some people complaining about feedparser the other day about unresolved issues and a large and getting larger number of bugs that need to be addressed but it hasn&#039;t been updated in forever. I didn&#039;t find any details though.</description>
		<content:encoded><![CDATA[<p>Funny, I heard some people complaining about feedparser the other day about unresolved issues and a large and getting larger number of bugs that need to be addressed but it hasn&#8217;t been updated in forever. I didn&#8217;t find any details though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://gfmorris.com/2005/06/11/feedlounge-tagging-and-renaming/comment-page-1/#comment-4296</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Sun, 12 Jun 2005 03:32:27 +0000</pubDate>
		<guid isPermaLink="false">http://ijsm.org/?p=2055#comment-4296</guid>
		<description>We actually changed the tag on you - it&#039;s now &#039;fl-broken&#039;, sorry about that.</description>
		<content:encoded><![CDATA[<p>We actually changed the tag on you &#8211; it&#8217;s now &#8216;fl-broken&#8217;, sorry about that.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
