<?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: What next?</title>
	<atom:link href="http://www.markbaker.ca/blog/2007/08/what-next/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.markbaker.ca/blog/2007/08/what-next/</link>
	<description>Celebrating the power of the Web</description>
	<lastBuildDate>Fri, 26 Aug 2011 20:00:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Mike Pittaro</title>
		<link>http://www.markbaker.ca/blog/2007/08/what-next/comment-page-1/#comment-272</link>
		<dc:creator>Mike Pittaro</dc:creator>
		<pubDate>Mon, 17 Dec 2007 18:46:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.markbaker.ca/blog/2007/08/08/what-next/#comment-272</guid>
		<description>Mark, I though about the &#039;whats next&#039; question for four months, and lo and behold, Amazon throws a wild pitch, just to see if we&#039;re watching !
http://www.dehora.net/journal/2007/12/16/amazon-simpledb-non-rest-api/

So, while the REST debate may be over and won, the reality is that even major players can get it wrong.

So, what next ?  Well, how about taking REST data services to the next level, where we could start to leverage the benefits of uniform interfaces, as opposed to just extolling the benefits ?</description>
		<content:encoded><![CDATA[<p>Mark, I though about the &#8216;whats next&#8217; question for four months, and lo and behold, Amazon throws a wild pitch, just to see if we&#8217;re watching !<br />
<a href="http://www.dehora.net/journal/2007/12/16/amazon-simpledb-non-rest-api/" rel="nofollow">http://www.dehora.net/journal/2007/12/16/amazon-simpledb-non-rest-api/</a></p>
<p>So, while the REST debate may be over and won, the reality is that even major players can get it wrong.</p>
<p>So, what next ?  Well, how about taking REST data services to the next level, where we could start to leverage the benefits of uniform interfaces, as opposed to just extolling the benefits ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henry Story</title>
		<link>http://www.markbaker.ca/blog/2007/08/what-next/comment-page-1/#comment-269</link>
		<dc:creator>Henry Story</dc:creator>
		<pubDate>Wed, 15 Aug 2007 14:39:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.markbaker.ca/blog/2007/08/08/what-next/#comment-269</guid>
		<description>Well the REST debate is over and won. But the Semantic Web debate, which is just the other side of the REST coin, needs some good evangelism. You won&#039;t find the space overcrowded here.  It is also great fun to be able to do battle with such powerful tools...</description>
		<content:encoded><![CDATA[<p>Well the REST debate is over and won. But the Semantic Web debate, which is just the other side of the REST coin, needs some good evangelism. You won&#8217;t find the space overcrowded here.  It is also great fun to be able to do battle with such powerful tools&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Mueller</title>
		<link>http://www.markbaker.ca/blog/2007/08/what-next/comment-page-1/#comment-271</link>
		<dc:creator>Patrick Mueller</dc:creator>
		<pubDate>Thu, 09 Aug 2007 04:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.markbaker.ca/blog/2007/08/08/what-next/#comment-271</guid>
		<description>Issues w/r/t &#039;partial updates&#039; and updates affecting multiple resources come up a lot.

Another issue is why some of these &#039;REST&#039; APIs we use, like Flickr, aren&#039;t following RESTy patterns, and how they could be redesigned to be RESTy interfaces.

Also, a lot of the RESTy examples are rather simplistic; what happens when my web &#039;application&#039; grows to supporting 20-30 services and data types; what sorts of tools / frameworks / libraries might we expect we&#039;ll need to both implement the app, and act as a client to the app.</description>
		<content:encoded><![CDATA[<p>Issues w/r/t &#8216;partial updates&#8217; and updates affecting multiple resources come up a lot.</p>
<p>Another issue is why some of these &#8216;REST&#8217; APIs we use, like Flickr, aren&#8217;t following RESTy patterns, and how they could be redesigned to be RESTy interfaces.</p>
<p>Also, a lot of the RESTy examples are rather simplistic; what happens when my web &#8216;application&#8217; grows to supporting 20-30 services and data types; what sorts of tools / frameworks / libraries might we expect we&#8217;ll need to both implement the app, and act as a client to the app.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew</title>
		<link>http://www.markbaker.ca/blog/2007/08/what-next/comment-page-1/#comment-270</link>
		<dc:creator>Matthew</dc:creator>
		<pubDate>Thu, 09 Aug 2007 02:27:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.markbaker.ca/blog/2007/08/08/what-next/#comment-270</guid>
		<description>Write posts of each kind just to mix things up.  They are all potentially interesting topics.</description>
		<content:encoded><![CDATA[<p>Write posts of each kind just to mix things up.  They are all potentially interesting topics.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

