This is Volume 33 of This week in REST, for Jan 29 2011 – Feb 8 2011. 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
Hypermedia is an Event Filter – “In this post, I will re-examine these alternatives, extending the analysis to the information flowing from client to server and the protocols used to exchange information. By doing so, I hope to clarify the advantages provided by REST for input event processing.” (by Andrew Wahbe)
REST and the Web as a Platform – (video) “In this interview, Subbu Allamaraju talks about real life issues of RESTful architectures. He also describes a pragmatic approach of adopting the Web as an integration platform and shares his opinion on OAuth.” (by Subbu Allamaraju)
Minting new Internet Media Type Identifiers – “… a recent discussion on twitter is triggering a quick and dirty run-through of how, when you create a new Internet Media Type (sometimes inaccurately call content type or MIME type), you should create a media type identifier. … A media type identifier is composed of three components: a content type, a content subtype and some parameters that can be specified.” (by Sebastien Lambla)
A proposal for REST and Verbs – “embedding verbs in URIs might not please the purists, but it can make for a highly accessible, practical API.”
CORS considered harmful – “there is no “cross-origin” on the Web. IT’S THE WEB DAMMIT! now, i understand that the common Web browser has problems; lots of them. but “the Web” is not one of them. instead of modeling the Web as the browser, it should be the other way ’round.” (by Mike Amundsen)
Being in a State of REST – Nice intro-level presentation. (by Aslam Khan)
Maze+XML media type approved! – “i got good news last week. my application to the IANA for registration of my Maze+XML media type was approved! yep, it’s official; i am ‘up on the big board'[grin]!” (by Mike Amundsen)
REST — What is State, anyway? – “REST stands for “Representational State Transfer”, which is kind of funny if you think about it, because it is an architectural style based on stateless communications. It says, use stateless communications to transfer state. … So what’s the state that we’re transferring, and at what point do we cross the line into non-stateless communication?”
Jargon in REST – “The REST uniform interface constraint is a specific guard against jargon. It sets the benchmark high: All services must express their unique capabilities in terms of a uniform contract composed of methods, media types, and resource identifier syntax. Service contracts in REST are transformed into tuples of (resource identifier template, method, media types, and supporting documentation). Service consumers take specific steps to decouple themselves from knowledge of the individual service contracts and instead increase their coupling on the uniform contract instead.” (by Benjamin Carlyle)
AWWSW Status Report – Status report from the Architecture of the World Wide Semantic Web members.
Hypermedia and the future of the integration over the web – “Restfulie’s first attempt to create a Ruby client for hypermedia services was in late 2009 with 100 lines of spaghetti ruby code. Eighteen months and lots of contributions later, Restfulie Ruby 1.0 is out: tackling both the server and client side on hypermedia based systems.” (by Guilherme Silveira)
REST discussion group and other mailing lists
The relation of Linked Data/Semantic Web to REST – “How are the principles of Linked Data as data publishing guide (independent of Semantic Web technology) and the Semantic Web as common, standardized technology stack for machine-processable knowledge representation and management in the Web related to the the principles of REST as an architectural style for distributed hypermedia systems?”
Link header is representation metadata? – “can I get a definitive answer (please :)) on whether the Link header is representation metadata (like Content-Type), or not?”
Loose coupling – a RESTful myth? – “is often stated, that RESTful services decouples client and server, as e.g. stated here :”Coupling between client and server is removed, server owners need not know about client particularities to evolve the servers without breaking clients.”But i think, the most server changes will break even the RESTfuls´ clients. At least in business scenarios.”
RESTful? – Interesting analysis of the RESTfulness of an HTTP API.
TAG work on registries (ACTION-511) – “It was an early principle of web architecture to try to avoid using registries and registry processes as a way of defining terms, but to rely on the power of the web itself for “distributed extensibility”. (You could say that before the web, the idea of hypertext was limited because the hypertext systems predating the web had a closed architecture for hypertext extensibility; this allowed referential integrity at the expense of an N-squared communication cost for web-content extensibility). In practice, though, there are situations where the overhead of using a full URI for extensibility (such as is done with XML namespaces) is deemed to be too cumbersome, and protocol designers prefer using registered shorter terms (or prefixes) instead.”
WS-9: The First Workshop on Adoption of REST and LinkedData (ARALD 2011) – Workshop as a part of the SAINT2011 : The 11th IEEE/IPSJ International Symposium on Applications and the Internet in Munich, GERMANY (July 18-22, 2011).
@AndrewWahbe – “The problem with conneg is that 2 event models (hypermedia is an event filter) yield 2 state machines (i.e. resources) for same app”
@dret – “URI as UI: URI opacity means that implementation design should not affect URI design; seize the opportunity and design them well.”