This is Volume 12 of This week in REST, for Apr 12 2010 – Apr 18 2010. For more information on this blog see this post. If I missed an interesting blog post, discussion or paper – just e-mail me the links, tweet or leave a comment on the latest blog post. Thanks!
Around the Web
REST maturity model – A 5-level revision of the 3-level Richardson REST maturity model. (by Guilherme Silveira)
Buying through REST: applying REST to the Enterprise – A video explanation of “REST applied”, a model that tries to answer the question of how to apply REST on contemporary concerns that enterprise have. (by Guilherme Silveira)
Constrained RESTful Environments WG (core) – Slides from the IETF77 meeting of the CoRE (Contrained RESTful Environments IETF working group, with an overview of the Constrained Application Protocol (CoAP), a RESTful (?) protocol to be used in constrained environments and devices.
On Web Applications, Web Architecture And Resource Identifiers – A critical dissection of the BBCiPlayer web application in order to answer fundamental questions about URIs and their usage in the modern Web architecture. (by T.V. Raman)
Minutes from the W3C TAG Meeting in Cambridge – Interesting notes from the recent W3C TAG face-to-face meeting.
Modified RPC over HTTP: old wine in a new bottle – Lets “create, not a RESTful interface, but a more typical HTTP interface that is too often labled RESTful when it is really a modified RPC interface over HTTP”. (by Mike Amundsen)
REST discussion group
The cache constraint – An interesting discussion on whether caching is a necessary constraint from an architerctural style point of view.
Bussiness layer error handling – On returning detailed error information to RESTful clients.
Class attribute usage vs. link relations – On what to do when links in representations “need to be machinereadable don’t necessarily have relationship that is easily qualifiedrelative to the “current” resource”.
Mikyung – Ruby REST client framework that “provides a layer of client generalization that gives you enough room to configure how your client should behave in different situations and make them work with different servers.”
@AndrewWahbe – “Don’t care about your new “RESTful service”. Create a new hypermedia format and/or a new kind of RESTful client/browser and I’m interested”