<?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: Weird feeds</title>
	<atom:link href="http://rakaz.nl/2005/05/weird-feeds.html/feed" rel="self" type="application/rss+xml" />
	<link>http://rakaz.nl/2005/05/weird-feeds.html</link>
	<description>about standards, webdesign, usability and open source</description>
	<lastBuildDate>Fri, 03 Sep 2010 12:52:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: anand</title>
		<link>http://rakaz.nl/2005/05/weird-feeds.html/comment-page-1#comment-633</link>
		<dc:creator>anand</dc:creator>
		<pubDate>Thu, 12 May 2005 09:55:50 +0000</pubDate>
		<guid isPermaLink="false">#comment-633</guid>
		<description>Here is a request.&lt;br /&gt;
&lt;br /&gt;
Can you add an API call where I send out a feed and get back a  structure of posts in return ?&lt;br /&gt;
&lt;br /&gt;
Will be useful for building feed specific applications.&lt;br /&gt;
&lt;br /&gt;
TIA!</description>
		<content:encoded><![CDATA[<p>Here is a request.</p>
<p>Can you add an API call where I send out a feed and get back a  structure of posts in return ?</p>
<p>Will be useful for building feed specific applications.</p>
<p>TIA!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rakaz</title>
		<link>http://rakaz.nl/2005/05/weird-feeds.html/comment-page-1#comment-628</link>
		<dc:creator>rakaz</dc:creator>
		<pubDate>Sun, 08 May 2005 11:03:47 +0000</pubDate>
		<guid isPermaLink="false">#comment-628</guid>
		<description>Why not re-use your universal feed parser? Well, mainly because your is written in Python and I use PHP. I also looked at some other parsers written in PHP, most notable Magpie, but that one is based on a different principle than what I was looking for.</description>
		<content:encoded><![CDATA[<p>Why not re-use your universal feed parser? Well, mainly because your is written in Python and I use PHP. I also looked at some other parsers written in PHP, most notable Magpie, but that one is based on a different principle than what I was looking for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://rakaz.nl/2005/05/weird-feeds.html/comment-page-1#comment-627</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Sun, 08 May 2005 09:51:24 +0000</pubDate>
		<guid isPermaLink="false">#comment-627</guid>
		<description>&gt; Building a universal feed reader is not easy. &lt;br /&gt;
&lt;br /&gt;
So why don&#039;t you re-use one that&#039;s already written?&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;http://feedparser.org/&quot; rel=&quot;nofollow&quot;&gt;http://feedparser.org/&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>&gt; Building a universal feed reader is not easy. </p>
<p>So why don&#8217;t you re-use one that&#8217;s already written?</p>
<p><a href="http://feedparser.org/" rel="nofollow">http://feedparser.org/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Ruby</title>
		<link>http://rakaz.nl/2005/05/weird-feeds.html/comment-page-1#comment-626</link>
		<dc:creator>Sam Ruby</dc:creator>
		<pubDate>Sat, 07 May 2005 20:27:55 +0000</pubDate>
		<guid isPermaLink="false">#comment-626</guid>
		<description>Good catches!&lt;br /&gt;
&lt;br /&gt;
My intent on my RSS 1.1 feed was to use the payload element, but due to a coding error, this was not done.  I&#039;ve now corrected this.&lt;br /&gt;
&lt;br /&gt;
As to my RSS 2.0 feed, many feeds use an xhtml:body element, such as Dare Obasanjo&#039;s.  The primary difference between his and mine is that I don&#039;t duplicate this information.  I use description for summaries of my longer entries.</description>
		<content:encoded><![CDATA[<p>Good catches!</p>
<p>My intent on my RSS 1.1 feed was to use the payload element, but due to a coding error, this was not done.  I&#8217;ve now corrected this.</p>
<p>As to my RSS 2.0 feed, many feeds use an xhtml:body element, such as Dare Obasanjo&#8217;s.  The primary difference between his and mine is that I don&#8217;t duplicate this information.  I use description for summaries of my longer entries.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rakaz</title>
		<link>http://rakaz.nl/2005/05/weird-feeds.html/comment-page-1#comment-625</link>
		<dc:creator>rakaz</dc:creator>
		<pubDate>Thu, 05 May 2005 16:07:04 +0000</pubDate>
		<guid isPermaLink="false">#comment-625</guid>
		<description>Hi Norman,&lt;br /&gt;
&lt;br /&gt;
Using draft 8 was actually a very good thing. I just build in support for draft 5 when you changed your feed to draft 8, which caused my Planet plugin to stop working again. So you are the one responsible for me going all the way and supporting up to draft 8. :)</description>
		<content:encoded><![CDATA[<p>Hi Norman,</p>
<p>Using draft 8 was actually a very good thing. I just build in support for draft 5 when you changed your feed to draft 8, which caused my Planet plugin to stop working again. So you are the one responsible for me going all the way and supporting up to draft 8. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Norman Walsh</title>
		<link>http://rakaz.nl/2005/05/weird-feeds.html/comment-page-1#comment-624</link>
		<dc:creator>Norman Walsh</dc:creator>
		<pubDate>Thu, 05 May 2005 12:17:21 +0000</pubDate>
		<guid isPermaLink="false">#comment-624</guid>
		<description>Yes, publishing my fees in Atom 05 was a questionable decision at best. It must have seemed like a good idea at the time, but I&#039;ll migrate to Atom 1.0 as fast as possible.&lt;br /&gt;
&lt;br /&gt;
I actually used 08 for a moment or two, but that turned out to be a real mistake :-)</description>
		<content:encoded><![CDATA[<p>Yes, publishing my fees in Atom 05 was a questionable decision at best. It must have seemed like a good idea at the time, but I&#8217;ll migrate to Atom 1.0 as fast as possible.</p>
<p>I actually used 08 for a moment or two, but that turned out to be a real mistake :-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

