REST / ROA / Astoria / SOA
Jon Udell, rightly so, is getting excited about the new book RESTful Web Services, by Leonard Richardson and Sam Ruby - a book I myself got excited about in November (REST Web Services and ROA) when I wrote at the time:
"My bet is that this project, the book and the concept of ROA as an effort to standardize aspects of RESTful architecture design is going to do very well, because I agree this is needed. Example provided:
- ""REST" is an abused term. Many alleged REST services (such as Flickr's, which says REST right on the website) are actually HTTP+POX: service-oriented APIs that happen to use nothing more the basic technologies of the web. Classifying services as resource-oriented or service-oriented makes it easy to see which ones are more and which less RESTful, without wasting time on minutiae.""
(more links to reviews here)
I don't know if John, Leonard or Sam have spent any time to look at the Astoria project (think - RESTful data services) - see links here, but would love to know what they think - in particular regarding the query syntax (good? bad? too complex? too simple?) and where it sits on the ROA (WOA?) to SOA continuum (WOA links) they discussed.