<?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: RESTful Web Services</title>
	<atom:link href="http://blog.jonudell.net/2007/05/24/restful-web-services/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jonudell.net/2007/05/24/restful-web-services/</link>
	<description>Strategies for Internet citizens</description>
	<lastBuildDate>Tue, 16 Mar 2010 06:42:47 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Major REST book now available! &#171; Noelios Technologies</title>
		<link>http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-125397</link>
		<dc:creator>Major REST book now available! &#171; Noelios Technologies</dc:creator>
		<pubDate>Wed, 24 Sep 2008 08:55:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-125397</guid>
		<description>[...] book review by Jon Udell (Microsoft) [...]</description>
		<content:encoded><![CDATA[<p>[...] book review by Jon Udell (Microsoft) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The World Bank&#8217;s web of data could be webbier &#171; Jon Udell</title>
		<link>http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-125243</link>
		<dc:creator>The World Bank&#8217;s web of data could be webbier &#171; Jon Udell</dc:creator>
		<pubDate>Fri, 05 Sep 2008 12:12:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-125243</guid>
		<description>[...] my review of the Leonard Richardson and Sam Ruby book RESTful Web Services I summarized their best practices [...]</description>
		<content:encoded><![CDATA[<p>[...] my review of the Leonard Richardson and Sam Ruby book RESTful Web Services I summarized their best practices [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 103.5 soma dinle</title>
		<link>http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-124571</link>
		<dc:creator>103.5 soma dinle</dc:creator>
		<pubDate>Sat, 28 Jun 2008 07:27:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-124571</guid>
		<description>&lt;strong&gt;soma...&lt;/strong&gt;

soma pay by check...</description>
		<content:encoded><![CDATA[<p><strong>soma&#8230;</strong></p>
<p>soma pay by check&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: .aspx considered harmful &#171; Jon Udell</title>
		<link>http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-122186</link>
		<dc:creator>.aspx considered harmful &#171; Jon Udell</dc:creator>
		<pubDate>Thu, 17 Jan 2008 16:32:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-122186</guid>
		<description>[...] in that genre. So does the Richardson and Ruby book RESTful Web Services which, as I noted in my review, recommends that URIs use forward slashes to encode hierarchy (/parent/child), commas to encode [...]</description>
		<content:encoded><![CDATA[<p>[...] in that genre. So does the Richardson and Ruby book RESTful Web Services which, as I noted in my review, recommends that URIs use forward slashes to encode hierarchy (/parent/child), commas to encode [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A conversation with Dick Hardt about British Columbia&#8217;s digital identity initiative &#171; Jon Udell</title>
		<link>http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-81218</link>
		<dc:creator>A conversation with Dick Hardt about British Columbia&#8217;s digital identity initiative &#171; Jon Udell</dc:creator>
		<pubDate>Mon, 12 Nov 2007 13:45:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-81218</guid>
		<description>[...] The equivalence between URIs and identity claims seems crucial here. Although I hadn&#8217;t made this connection before, I suspect it will enable a compositional approach to identity management which has much in common with the principles of RESTful web services. [...]</description>
		<content:encoded><![CDATA[<p>[...] The equivalence between URIs and identity claims seems crucial here. Although I hadn&#8217;t made this connection before, I suspect it will enable a compositional approach to identity management which has much in common with the principles of RESTful web services. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Smith</title>
		<link>http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-40673</link>
		<dc:creator>Alex Smith</dc:creator>
		<pubDate>Tue, 17 Jul 2007 12:30:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-40673</guid>
		<description>Hey buddy!  Nice blog that you maintain here.. I just chanced upon your blog surfing the blogosphere. I was thinking.. you could try out some interesting widgets on your page and spice it up with more relevant information. E.g try out the new widget on http://www.widgetmate.com with your relevant keywords</description>
		<content:encoded><![CDATA[<p>Hey buddy!  Nice blog that you maintain here.. I just chanced upon your blog surfing the blogosphere. I was thinking.. you could try out some interesting widgets on your page and spice it up with more relevant information. E.g try out the new widget on <a href="http://www.widgetmate.com" rel="nofollow">http://www.widgetmate.com</a> with your relevant keywords</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vasudev Ram</title>
		<link>http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-32744</link>
		<dc:creator>Vasudev Ram</dc:creator>
		<pubDate>Sat, 23 Jun 2007 21:00:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-32744</guid>
		<description>Thanks for the review of the book. I just heard about it somewhere else a few days back, Googled some more today and came across your review of it. (I&#039;ve been reading your articles right from the BYTE column days and think they&#039;re very good. Also your book &quot;Practical Internet Groupware&quot;.) I think REST is a good architectural style, and though, as you say, it may not fulfil all of the goals of SOA, it definitely has its place as a useful way of developing Web applications. I agree that the existing Net resources on REST leave out some details; had started doing some work on a RESTful product (in Python, later might port it to Java and Ruby) and think I should find the book useful to fill in those details and give me some guidance. For anyone else reading this comment, one of the co-authors of the RESTful book, Leonard Richardson, also co-wrote The Ruby Cookbook (published by O&#039;Reilly), a very good book, IMO.

- Vasudev Ram
Dancing Bison Enterprises
http://www.dancingbison.com</description>
		<content:encoded><![CDATA[<p>Thanks for the review of the book. I just heard about it somewhere else a few days back, Googled some more today and came across your review of it. (I&#8217;ve been reading your articles right from the BYTE column days and think they&#8217;re very good. Also your book &#8220;Practical Internet Groupware&#8221;.) I think REST is a good architectural style, and though, as you say, it may not fulfil all of the goals of SOA, it definitely has its place as a useful way of developing Web applications. I agree that the existing Net resources on REST leave out some details; had started doing some work on a RESTful product (in Python, later might port it to Java and Ruby) and think I should find the book useful to fill in those details and give me some guidance. For anyone else reading this comment, one of the co-authors of the RESTful book, Leonard Richardson, also co-wrote The Ruby Cookbook (published by O&#8217;Reilly), a very good book, IMO.</p>
<p>- Vasudev Ram<br />
Dancing Bison Enterprises<br />
<a href="http://www.dancingbison.com" rel="nofollow">http://www.dancingbison.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RESTful Live Contacts for Internet-scale social networking &#171; Jon Udell</title>
		<link>http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-31731</link>
		<dc:creator>RESTful Live Contacts for Internet-scale social networking &#171; Jon Udell</dc:creator>
		<pubDate>Thu, 21 Jun 2007 13:54:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-31731</guid>
		<description>[...] Jon Udell @ 8:53 am    It&#8217;s been an interesting couple of weeks for folks who care about RESTful web services. Dare Obasanjo kicked things off with a couple of items about the Atom Publishing Protocol (APP) [...]</description>
		<content:encoded><![CDATA[<p>[...] Jon Udell @ 8:53 am    It&#8217;s been an interesting couple of weeks for folks who care about RESTful web services. Dare Obasanjo kicked things off with a couple of items about the Atom Publishing Protocol (APP) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Udell</title>
		<link>http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-28618</link>
		<dc:creator>Jon Udell</dc:creator>
		<pubDate>Wed, 13 Jun 2007 20:46:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-28618</guid>
		<description>&quot;Am I missing something, or doesn’t this run counter to the often-voiced argument that REST builds upon what makes the web what it is today?&quot;

I thought this was a good question. I invited the authors to respond. Leonard did, here:

http://www.crummy.com/2007/06/12/0</description>
		<content:encoded><![CDATA[<p>&#8220;Am I missing something, or doesn’t this run counter to the often-voiced argument that REST builds upon what makes the web what it is today?&#8221;</p>
<p>I thought this was a good question. I invited the authors to respond. Leonard did, here:</p>
<p><a href="http://www.crummy.com/2007/06/12/0" rel="nofollow">http://www.crummy.com/2007/06/12/0</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul H.</title>
		<link>http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-28226</link>
		<dc:creator>Paul H.</dc:creator>
		<pubDate>Tue, 12 Jun 2007 04:31:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-28226</guid>
		<description>&lt;i&gt;My goal in this book is not to make the programmable web bigger. That’s almost impossible: the programmable web already encompasses nearly everything with an HTTP interface. My goal is to help make the programmable web &lt;/i&gt;better:&lt;i&gt; more uniform, better structured, and using the features of HTTP to greatest advantage.&lt;/i&gt;

This quote seems to be missing a bit of context.  In the preface, the authors&#039; goal is stated as being one &quot;to reunite the programmable web with the human web.  We envision a single interconnected network: a World Wide Web that runs on one set of servers, uses one set of protocols, and obeys one set of design principles.  A network that you can use whether you&#039;re serving data to human beings or computer programs.&quot;  Yet the paragraphs that immediately precede the quote about making the programmable web &lt;i&gt;better&lt;/i&gt; establish the position that the &quot;RESTful&quot; space of today&#039;s Web essentially encompasses read-only sites (e.g., static web pages and search engines), and that the bulk of today&#039;s Web &lt;i&gt;Applications&lt;/i&gt; do &lt;i&gt;not&lt;/i&gt; meet the criteria for RESTfulness.  The unstated assertion here then is that in order to meet the authors&#039; stated goals, the majority of today&#039;s Web Applications will need to be re-architected and re-written in order to conform to a RESTful style!  Stated another way: the RESTful approach is essentially unproven outside of the read-only Web, yet the authors assert not only that RESTfulness will make the Programmable Web &lt;i&gt;better&lt;/i&gt; but also that we should discard the proven ways of constructing Web Applications in favor of the RESTful approach!  (I.e., the only way to have RESTful Web Services &lt;i&gt;and&lt;/i&gt; unification of the human and programmable webs is for human-oriented web applications to adhere to the rules of RESTfulness as well!)  Am I missing something, or doesn&#039;t this run &lt;i&gt;counter&lt;/i&gt; to the often-voiced argument that REST builds upon what makes the web what it is today?</description>
		<content:encoded><![CDATA[<p><i>My goal in this book is not to make the programmable web bigger. That’s almost impossible: the programmable web already encompasses nearly everything with an HTTP interface. My goal is to help make the programmable web </i>better:<i> more uniform, better structured, and using the features of HTTP to greatest advantage.</i></p>
<p>This quote seems to be missing a bit of context.  In the preface, the authors&#8217; goal is stated as being one &#8220;to reunite the programmable web with the human web.  We envision a single interconnected network: a World Wide Web that runs on one set of servers, uses one set of protocols, and obeys one set of design principles.  A network that you can use whether you&#8217;re serving data to human beings or computer programs.&#8221;  Yet the paragraphs that immediately precede the quote about making the programmable web <i>better</i> establish the position that the &#8220;RESTful&#8221; space of today&#8217;s Web essentially encompasses read-only sites (e.g., static web pages and search engines), and that the bulk of today&#8217;s Web <i>Applications</i> do <i>not</i> meet the criteria for RESTfulness.  The unstated assertion here then is that in order to meet the authors&#8217; stated goals, the majority of today&#8217;s Web Applications will need to be re-architected and re-written in order to conform to a RESTful style!  Stated another way: the RESTful approach is essentially unproven outside of the read-only Web, yet the authors assert not only that RESTfulness will make the Programmable Web <i>better</i> but also that we should discard the proven ways of constructing Web Applications in favor of the RESTful approach!  (I.e., the only way to have RESTful Web Services <i>and</i> unification of the human and programmable webs is for human-oriented web applications to adhere to the rules of RESTfulness as well!)  Am I missing something, or doesn&#8217;t this run <i>counter</i> to the often-voiced argument that REST builds upon what makes the web what it is today?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2007-06-09 &#171; Mike Does Tech</title>
		<link>http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-27186</link>
		<dc:creator>links for 2007-06-09 &#171; Mike Does Tech</dc:creator>
		<pubDate>Sat, 09 Jun 2007 00:41:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-27186</guid>
		<description>[...] RESTful Web Services « Jon Udell Udell gives the dirt on what is promising about RESTful web services with his usual grace. (tags: REST webservices) [...]</description>
		<content:encoded><![CDATA[<p>[...] RESTful Web Services « Jon Udell Udell gives the dirt on what is promising about RESTful web services with his usual grace. (tags: REST webservices) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: REST, dove vogliamo andare a parare? at GoTo 10 - blog italiano sulla programmazione</title>
		<link>http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-26979</link>
		<dc:creator>REST, dove vogliamo andare a parare? at GoTo 10 - blog italiano sulla programmazione</dc:creator>
		<pubDate>Fri, 08 Jun 2007 11:39:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-26979</guid>
		<description>[...] c&#8217;è questo movimento controrivoluzionario di formalizzare REST, che a me non piace granché. Esempio. Non fatevi fregare dal fatto che chi propone una cosa è lo stesso che l&#8217;ha [...]</description>
		<content:encoded><![CDATA[<p>[...] c&#8217;è questo movimento controrivoluzionario di formalizzare REST, che a me non piace granché. Esempio. Non fatevi fregare dal fatto che chi propone una cosa è lo stesso che l&#8217;ha [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WS-JustRight revisited &#171; Jon Udell</title>
		<link>http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-25083</link>
		<dc:creator>WS-JustRight revisited &#171; Jon Udell</dc:creator>
		<pubDate>Tue, 05 Jun 2007 16:00:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-25083</guid>
		<description>[...] Filed under: Uncategorized &#8212; Jon Udell @ 11:00 am    The audio interview mentioned in my review of the new Leonard Richard and Sam Ruby book, RESTful Web Services, is now available at [...]</description>
		<content:encoded><![CDATA[<p>[...] Filed under: Uncategorized &#8212; Jon Udell @ 11:00 am    The audio interview mentioned in my review of the new Leonard Richard and Sam Ruby book, RESTful Web Services, is now available at [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bruno</title>
		<link>http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-21883</link>
		<dc:creator>bruno</dc:creator>
		<pubDate>Thu, 31 May 2007 15:02:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-21883</guid>
		<description>Either I can put/post/get/delete accounts, or transactions, but modeling both it seems like there&#039;s one too many. Posting on a transaction leads to a side effect, and deprecates post on accounts (to perform what?); would GET on an account still work?

That said, this approach gives an view on an important matter.

BTW, finally got the book today! Will read it carefully!</description>
		<content:encoded><![CDATA[<p>Either I can put/post/get/delete accounts, or transactions, but modeling both it seems like there&#8217;s one too many. Posting on a transaction leads to a side effect, and deprecates post on accounts (to perform what?); would GET on an account still work?</p>
<p>That said, this approach gives an view on an important matter.</p>
<p>BTW, finally got the book today! Will read it carefully!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex James</title>
		<link>http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-21659</link>
		<dc:creator>Alex James</dc:creator>
		<pubDate>Thu, 31 May 2007 05:20:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/2007/05/24/restful-web-services/#comment-21659</guid>
		<description>..The point is that we simply state our intent and ship all state necessary for that intent to the server. (BTW this is analogous to database LOG files... that store INTENT, not results).

The key to implementing something like this is to understand that physical HTTP Endpoints for our REST service are just wrappers around an internal endpoints that have URIs too…</description>
		<content:encoded><![CDATA[<p>..The point is that we simply state our intent and ship all state necessary for that intent to the server. (BTW this is analogous to database LOG files&#8230; that store INTENT, not results).</p>
<p>The key to implementing something like this is to understand that physical HTTP Endpoints for our REST service are just wrappers around an internal endpoints that have URIs too…</p>
]]></content:encoded>
	</item>
</channel>
</rss>
