<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: JSON as hypermedia</title>
	<atom:link href="http://eikonne.wordpress.com/2008/04/27/json-as-hypermedia/feed/" rel="self" type="application/rss+xml" />
	<link>http://eikonne.wordpress.com/2008/04/27/json-as-hypermedia/</link>
	<description>All and sundry</description>
	<lastBuildDate>Mon, 17 Aug 2009 03:35:06 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Recent Links Tagged With "hypermedia" - JabberTags</title>
		<link>http://eikonne.wordpress.com/2008/04/27/json-as-hypermedia/#comment-53</link>
		<dc:creator>Recent Links Tagged With "hypermedia" - JabberTags</dc:creator>
		<pubDate>Sat, 01 Nov 2008 21:35:02 +0000</pubDate>
		<guid isPermaLink="false">http://eikonne.wordpress.com/?p=35#comment-53</guid>
		<description>[...] public links &gt;&gt; hypermedia   JSON as hypermedia Saved by samicbc on Fri 31-10-2008   Many of the anti spam hypermedia programs are successful to [...]</description>
		<content:encoded><![CDATA[<p>[...] public links &gt;&gt; hypermedia   JSON as hypermedia Saved by samicbc on Fri 31-10-2008   Many of the anti spam hypermedia programs are successful to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Amundsen</title>
		<link>http://eikonne.wordpress.com/2008/04/27/json-as-hypermedia/#comment-28</link>
		<dc:creator>Mike Amundsen</dc:creator>
		<pubDate>Mon, 28 Apr 2008 16:45:42 +0000</pubDate>
		<guid isPermaLink="false">http://eikonne.wordpress.com/?p=35#comment-28</guid>
		<description>I posted a reply to your comments on my blog and thought to follow up here, too. I agree that standards need to precede clients in this case. I suspect that, like most standards efforts, this one might be driven by the existence of a few clients that - while starting out independently - cause a convergence on a standard way to express and interpret JSON as a hypermedia format.</description>
		<content:encoded><![CDATA[<p>I posted a reply to your comments on my blog and thought to follow up here, too. I agree that standards need to precede clients in this case. I suspect that, like most standards efforts, this one might be driven by the existence of a few clients that &#8211; while starting out independently &#8211; cause a convergence on a standard way to express and interpret JSON as a hypermedia format.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
