<?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: Apple creates RSS the Microsoft way</title>
	<atom:link href="http://blog.forret.com/2006/01/apple-creates-rss-the-microsoft-way/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.forret.com/2006/01/apple-creates-rss-the-microsoft-way/</link>
	<description>and I mean it</description>
	<lastBuildDate>Wed, 18 Nov 2009 21:45:03 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Peter</title>
		<link>http://blog.forret.com/2006/01/apple-creates-rss-the-microsoft-way/comment-page-1/#comment-371</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Wed, 18 Jan 2006 22:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://peter.smoothouse.com/2006/01/15/apple-creates-rss-the-microsoft-way/#comment-371</guid>
		<description>I don&#039;t think RFC822 is so much better than ISO8601. Personally I think all machine-to-machine formats should use UTC. (see &lt;a HREF=&quot;http://www.scit.wlv.ac.uk/rfc/rfc33xx/RFC3339.html#14&quot; rel=&quot;nofollow&quot;&gt;RFC-3339&lt;/A&gt;)
But the &lt;a HREF=&quot;http://blogs.law.harvard.edu/tech/rss&quot; rel=&quot;nofollow&quot;&gt;RSS&lt;/A&gt; specification says RFC-822. &quot;All date-times in RSS conform to the Date and Time Specification of RFC 822, with the exception that the year may be expressed with two characters or four characters (four preferred).&quot;</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think RFC822 is so much better than ISO8601. Personally I think all machine-to-machine formats should use UTC. (see <a HREF="http://www.scit.wlv.ac.uk/rfc/rfc33xx/RFC3339.html#14" rel="nofollow">RFC-3339</a>)<br />
But the <a HREF="http://blogs.law.harvard.edu/tech/rss" rel="nofollow">RSS</a> specification says RFC-822. &#8220;All date-times in RSS conform to the Date and Time Specification of RFC 822, with the exception that the year may be expressed with two characters or four characters (four preferred).&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blog.forret.com/2006/01/apple-creates-rss-the-microsoft-way/comment-page-1/#comment-370</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 18 Jan 2006 20:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://peter.smoothouse.com/2006/01/15/apple-creates-rss-the-microsoft-way/#comment-370</guid>
		<description>The date format is pretty standard ISO format. Why do you think the totally stupid computer format like &#039;Sun, 13 Jan ...&#039; is better then the ISO format? Not everyone in the world is speaking English and using this kind of displaying date.</description>
		<content:encoded><![CDATA[<p>The date format is pretty standard ISO format. Why do you think the totally stupid computer format like &#8216;Sun, 13 Jan &#8230;&#8217; is better then the ISO format? Not everyone in the world is speaking English and using this kind of displaying date.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Evans</title>
		<link>http://blog.forret.com/2006/01/apple-creates-rss-the-microsoft-way/comment-page-1/#comment-369</link>
		<dc:creator>John Evans</dc:creator>
		<pubDate>Mon, 16 Jan 2006 09:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://peter.smoothouse.com/2006/01/15/apple-creates-rss-the-microsoft-way/#comment-369</guid>
		<description>You know I would like to add something here. Flickr themselves are pretty guilty of not providing decent feeds. For example their Atom feeds are still on version 0.3, and they tend to do things like mess up the keywords i.e. they strip spaces and extra chars and put them in a space seperated list under DC-&gt;Subject when Atom has a perfectly good Category attribute, and they keywords could each be put in their own Category tag.

And I think Apple would have actually been better off going for Atom rather than RSS 2.0. It supports nearly everything they hacked into RSS 2.0 already. In fact I have made some perfectly valid Atom feeds that iPhoto will process happily that include all the dates and keywords etc.

If anyone wants to play around with my Flickr Atom feeds in iPhoto u can go here: http://phlikr.3xi.org/ Paste in the url of the flickr feed, hit the button and you will be asked by iphoto to subscribe to the feed. The main reason I am doing it this way is because they dont play nicly with each other really and I put a bit of glue in between to get the tags, comments, correct dates and image sizes into iPhoto</description>
		<content:encoded><![CDATA[<p>You know I would like to add something here. Flickr themselves are pretty guilty of not providing decent feeds. For example their Atom feeds are still on version 0.3, and they tend to do things like mess up the keywords i.e. they strip spaces and extra chars and put them in a space seperated list under DC-&gt;Subject when Atom has a perfectly good Category attribute, and they keywords could each be put in their own Category tag.</p>
<p>And I think Apple would have actually been better off going for Atom rather than RSS 2.0. It supports nearly everything they hacked into RSS 2.0 already. In fact I have made some perfectly valid Atom feeds that iPhoto will process happily that include all the dates and keywords etc.</p>
<p>If anyone wants to play around with my Flickr Atom feeds in iPhoto u can go here: <a href="http://phlikr.3xi.org/" rel="nofollow">http://phlikr.3xi.org/</a> Paste in the url of the flickr feed, hit the button and you will be asked by iphoto to subscribe to the feed. The main reason I am doing it this way is because they dont play nicly with each other really and I put a bit of glue in between to get the tags, comments, correct dates and image sizes into iPhoto</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Meyer</title>
		<link>http://blog.forret.com/2006/01/apple-creates-rss-the-microsoft-way/comment-page-1/#comment-368</link>
		<dc:creator>Mark Meyer</dc:creator>
		<pubDate>Mon, 16 Jan 2006 07:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://peter.smoothouse.com/2006/01/15/apple-creates-rss-the-microsoft-way/#comment-368</guid>
		<description>What we need is a disinterested third party. Apple is not going to use an RSS extension in its products with a yahoo.com namespace. It just won&#039;t happen at this stage. It would be nice if we could all just get along but, since apple and yahoo could end up fighting over the same turf, there is little chance that the path to standards begins with apple adopting yahoo&#039;s format.</description>
		<content:encoded><![CDATA[<p>What we need is a disinterested third party. Apple is not going to use an RSS extension in its products with a yahoo.com namespace. It just won&#8217;t happen at this stage. It would be nice if we could all just get along but, since apple and yahoo could end up fighting over the same turf, there is little chance that the path to standards begins with apple adopting yahoo&#8217;s format.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blog.forret.com/2006/01/apple-creates-rss-the-microsoft-way/comment-page-1/#comment-367</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 16 Jan 2006 07:12:00 +0000</pubDate>
		<guid isPermaLink="false">http://peter.smoothouse.com/2006/01/15/apple-creates-rss-the-microsoft-way/#comment-367</guid>
		<description>I sure wish the developers of aggregators would start supporting one of the photo extensions so people can stop putting the photos in the description element as html. In an ideal world the description would describe the attached photo without also including the photo so you could treat the photo and the description as individual pieces of data. As it is, if you want to create an interesting application that takes the photo from the extension and displays it with the description, you get two photos--the one from the attachment and the one from the description. In the end you either end up ignoring the photo rss extension or scrape out the html from the description. But people (naturally) want to see the photos in the aggregators which leaves the creator little choice other than the current bad practice.</description>
		<content:encoded><![CDATA[<p>I sure wish the developers of aggregators would start supporting one of the photo extensions so people can stop putting the photos in the description element as html. In an ideal world the description would describe the attached photo without also including the photo so you could treat the photo and the description as individual pieces of data. As it is, if you want to create an interesting application that takes the photo from the extension and displays it with the description, you get two photos&#8211;the one from the attachment and the one from the description. In the end you either end up ignoring the photo rss extension or scrape out the html from the description. But people (naturally) want to see the photos in the aggregators which leaves the creator little choice other than the current bad practice.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

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