Web Things, by Mark Baker

“Scraping, mashups, and RSS mean that your site is already a service […]”. Amen, Doug.
(link) [del.icio.us/distobj]

Eric writes, in the context of discussing the coupling of client and server via interface (getStockQuote) semantics;

No, it doesn’t need to understand the semantics. It’s enough to define the data and associate it with a service name.

A pretty thorough critique of Rails from a REST perspective, including Dan Kubb’s proposed extensions. Peter, take this to the microformats-rest list.
(link) [del.icio.us/distobj]

The analogue of the previous RESTful service access code (for a different example). Again, that’s awfully complex for such a simple task. Yikes.
(link) [del.icio.us/distobj]

Wow, that’s pretty complex coding for such a simple task, no? I’d opt for java.net (bugs, quirks, and all), or other Java client HTTP APIs (the two HTTPClient projects come to mind).
(link) [del.icio.us/distobj]

Seems to make a lot of the same mistakes as the Amazon API (e.g. http://…/?CallName=GetSearchResults), and confuses HTTP with REST, but at least it’s ok for data retrieval
(link) [del.icio.us/distobj]

To re-read later …
(link) [del.icio.us/distobj]

A nicely designed RESTful API. Not so sure why ‘?query=”is:unread”‘ is better than ‘?is=unread’ though. The latter would make the interface more usable via HTML forms, as well as more easily handled by server-side libraries (slightly).
(link) [del.icio.us/distobj]

That’s how you do it, more or less. I wonder if hierarchy isn’t used properly though, i.e. having “tag” as subordinate to “item”; if you DELETE the item, does the tag go too? Maybe it does.
(link) [del.icio.us/distobj]

“Absolutes do not apply”. Never? 8-)
(link) [del.icio.us/distobj]