<?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"
	>
<channel>
	<title>Comments on: REST: is RSS the HTML for data?</title>
	<atom:link href="http://www.megginson.com/blogs/quoderat/2005/03/31/rest-and-rss/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.megginson.com/blogs/quoderat/2005/03/31/rest-and-rss/</link>
	<description>what was</description>
	<pubDate>Fri, 19 Mar 2010 15:36:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Quoderat &#187; More on RSS as the HTML for data &#8230;</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/03/31/rest-and-rss/#comment-16293</link>
		<dc:creator>Quoderat &#187; More on RSS as the HTML for data &#8230;</dc:creator>
		<pubDate>Thu, 09 Nov 2006 12:19:16 +0000</pubDate>
		<guid isPermaLink="false">/?p=36#comment-16293</guid>
		<description>[...] A short while ago, I reluctantly acknowledged that RSS 2.0 will likely fill the same role for data that HTML fills for documents, providing a single, shared format across the web (the big missing piece of the puzzle for REST apps). Now, it appears that someone a lot smarter than I am &#8212; no one less than Adam Bosworth &#8212; is suggesting exactly the same thing. [...]</description>
		<content:encoded><![CDATA[<p>[...] A short while ago, I reluctantly acknowledged that RSS 2.0 will likely fill the same role for data that HTML fills for documents, providing a single, shared format across the web (the big missing piece of the puzzle for REST apps). Now, it appears that someone a lot smarter than I am &#8212; no one less than Adam Bosworth &#8212; is suggesting exactly the same thing. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Read/Write Web</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/03/31/rest-and-rss/#comment-770</link>
		<dc:creator>Read/Write Web</dc:creator>
		<pubDate>Mon, 09 May 2005 08:48:46 +0000</pubDate>
		<guid isPermaLink="false">/?p=36#comment-770</guid>
		<description>&lt;strong&gt;Web 2.0 Weekly Wrap-up, 2-8 May 2005&lt;/strong&gt;
This week: business folk getting interested in Web 2.0, Adam Curry podcasting
from 2.0 perspective, cool Web 2.0 'mini-apps', wrap-up of the adverts in RSS debate,
Bosworth's Web of Data...</description>
		<content:encoded><![CDATA[<p><strong>Web 2.0 Weekly Wrap-up, 2-8 May 2005</strong><br />
This week: business folk getting interested in Web 2.0, Adam Curry podcasting<br />
from 2.0 perspective, cool Web 2.0 &#8216;mini-apps&#8217;, wrap-up of the adverts in RSS debate,<br />
Bosworth&#8217;s Web of Data&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/03/31/rest-and-rss/#comment-508</link>
		<dc:creator>Danny</dc:creator>
		<pubDate>Fri, 01 Apr 2005 16:42:41 +0000</pubDate>
		<guid isPermaLink="false">/?p=36#comment-508</guid>
		<description>What exactly does using RSS 2.0 gain you over using an arbitrary XML language? 

If there is to be a more widely used common data format for the Web, the barest minimum I would expect is a means to identify the identifiers of the Web, i.e. URIs. Personally I'd opt for something semantically richer ;-)</description>
		<content:encoded><![CDATA[<p>What exactly does using RSS 2.0 gain you over using an arbitrary XML language? </p>
<p>If there is to be a more widely used common data format for the Web, the barest minimum I would expect is a means to identify the identifiers of the Web, i.e. URIs. Personally I&#8217;d opt for something semantically richer <img src='http://www.megginson.com/blogs/quoderat/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Megginson</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/03/31/rest-and-rss/#comment-507</link>
		<dc:creator>David Megginson</dc:creator>
		<pubDate>Fri, 01 Apr 2005 12:20:14 +0000</pubDate>
		<guid isPermaLink="false">/?p=36#comment-507</guid>
		<description>Atom may be too little, too late -- something that does 10-20% more than RSS isn't enough to make people switch when RSS 2.0 is already so well established.  I'd prefer POX+XLink+xml:id, personally, but to continue the HTML analogy, remember that HTML came first, and the W3C came much later.</description>
		<content:encoded><![CDATA[<p>Atom may be too little, too late &#8212; something that does 10-20% more than RSS isn&#8217;t enough to make people switch when RSS 2.0 is already so well established.  I&#8217;d prefer POX+XLink+xml:id, personally, but to continue the HTML analogy, remember that HTML came first, and the W3C came much later.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anne</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/03/31/rest-and-rss/#comment-506</link>
		<dc:creator>Anne</dc:creator>
		<pubDate>Fri, 01 Apr 2005 10:24:41 +0000</pubDate>
		<guid isPermaLink="false">/?p=36#comment-506</guid>
		<description>I sure hope some specified, official format, like Atom, will do this instead of RSS 2.0.</description>
		<content:encoded><![CDATA[<p>I sure hope some specified, official format, like Atom, will do this instead of RSS 2.0.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken MacLeod</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/03/31/rest-and-rss/#comment-496</link>
		<dc:creator>Ken MacLeod</dc:creator>
		<pubDate>Thu, 31 Mar 2005 23:26:04 +0000</pubDate>
		<guid isPermaLink="false">/?p=36#comment-496</guid>
		<description>I'm seeing the growth of POX, with AJAX and XMLHttpRequest currently doing the most pushing.  If ECMAScript for XML (E4X) starts getting traction, it'll be a slam dunk (and hopefully similar grammars will make it into other favorite languages).</description>
		<content:encoded><![CDATA[<p>I&#8217;m seeing the growth of POX, with AJAX and XMLHttpRequest currently doing the most pushing.  If ECMAScript for XML (E4X) starts getting traction, it&#8217;ll be a slam dunk (and hopefully similar grammars will make it into other favorite languages).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
