<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Misunderstanding REST</title>
	<link>http://agylen.com/2007/02/14/misunderstanding-rest/</link>
	<description>Ugo Cei's Weblog</description>
	<pubDate>Mon, 01 Dec 2008 21:37:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: J Wynia</title>
		<link>http://agylen.com/2007/02/14/misunderstanding-rest/#comment-67716</link>
		<dc:creator>J Wynia</dc:creator>
		<pubDate>Sat, 10 Mar 2007 16:25:50 +0000</pubDate>
		<guid>http://agylen.com/2007/02/14/misunderstanding-rest/#comment-67716</guid>
		<description>Plus, citing Metaweblog API as any sort of positive example ought to disqualify someone. I mean, an API where you can save a post as a draft, but not retrieve it for editing. 

The whole POINT of a draft is that it needs further editing. Yet, you can retrieve published posts for editing and not drafts.

That it's so widely implemented speaks more to tragedy than to lend any weight to it as something to be held up as an example.

Contrast Metweblog API with the new Atom Publishing Protocol Draft, where you can do complete CRUD on any of the objects, with only the API and you get an actual, decent blogging API.

I've come to regard most of what Dave Winer does as purely proof of concept kind of stuff. Note that there's nothing wrong with that. In fact, it's the phase of software I most enjoy myself. 

The thing is that if you're doing a proof of concept, the result shouldn't be used as a "standard".</description>
		<content:encoded><![CDATA[<p>Plus, citing Metaweblog API as any sort of positive example ought to disqualify someone. I mean, an API where you can save a post as a draft, but not retrieve it for editing. </p>
<p>The whole POINT of a draft is that it needs further editing. Yet, you can retrieve published posts for editing and not drafts.</p>
<p>That it&#8217;s so widely implemented speaks more to tragedy than to lend any weight to it as something to be held up as an example.</p>
<p>Contrast Metweblog API with the new Atom Publishing Protocol Draft, where you can do complete CRUD on any of the objects, with only the API and you get an actual, decent blogging API.</p>
<p>I&#8217;ve come to regard most of what Dave Winer does as purely proof of concept kind of stuff. Note that there&#8217;s nothing wrong with that. In fact, it&#8217;s the phase of software I most enjoy myself. </p>
<p>The thing is that if you&#8217;re doing a proof of concept, the result shouldn&#8217;t be used as a &#8220;standard&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sephiroth_4</title>
		<link>http://agylen.com/2007/02/14/misunderstanding-rest/#comment-66524</link>
		<dc:creator>sephiroth_4</dc:creator>
		<pubDate>Thu, 01 Mar 2007 12:27:44 +0000</pubDate>
		<guid>http://agylen.com/2007/02/14/misunderstanding-rest/#comment-66524</guid>
		<description>but wrong article reply!!  How'd I get here?!  Sorry!</description>
		<content:encoded><![CDATA[<p>but wrong article reply!!  How&#8217;d I get here?!  Sorry!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sephiroth_4</title>
		<link>http://agylen.com/2007/02/14/misunderstanding-rest/#comment-66523</link>
		<dc:creator>sephiroth_4</dc:creator>
		<pubDate>Thu, 01 Mar 2007 12:26:42 +0000</pubDate>
		<guid>http://agylen.com/2007/02/14/misunderstanding-rest/#comment-66523</guid>
		<description>All these map services, I wish would get "synchronized".  It's not like construction of roads outpace technology or database updates!  Nice article.</description>
		<content:encoded><![CDATA[<p>All these map services, I wish would get &#8220;synchronized&#8221;.  It&#8217;s not like construction of roads outpace technology or database updates!  Nice article.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
