Skip navigation

This is Volume 30 of This week in REST, for Nov 21 2010 – Dec 12 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

URI Identity and Web Architecture Revisited – “This document reexamined the URI’s identity issue and the debate regarding the nature of “information resource”. By making emphasis on the abstract nature of resource and the role of URI as an interface to the web, this article presented an alternative viewpoint about the architecture of the web that would allow us to objectively and consistently treat all kinds of resources.” (by Xiaoshu Wang)

Web of Things Core Concepts Paper – “In this paper, we begin by describing the Web of Things architecture and best-practices based on the RESTful principles that have already contributed to the popular success, scalability, and modularity of the traditional Web. We then discuss several prototypes designed in accordance with these principles to connect environmental sensor nodes and an energy monitoring system to the WorldWideWeb. We finally show how Web-enabled smart things can be used in lightweight ad-hoc applications called “physical mashups”.” (by Dominique Guinard, Vlad Trifa and Erik Wilde)

Registering A Media Type, Part I – “as part of my ongoing work to learn about how MIME media types are used w/ HTTP and other app-level protocols, i am going through the process of designing and registering a media type with the IANA standards body. along the way, i’m going to blog my experience. hopefully this will be helpful to others when they want to register their own custom media types.” (by Mike Amundsen)

Web Linking – “A couple months ago, Mark Nottingham’s Web Linking internet draft made its way to RFC status. This is a pretty significant specification for the web. It does three key things: It provides a generic definition of a “link”; It establishes a registry for link relations; and It defines the HTTP link header.” (by Andrew Wahbe)

API for RDF? don’t do it! – “There is little doubt that that RDF is powerful and valuable. but i predict RDF will continue to suffer slow adoption rates and limited use (as it has for the last ten years) until work is done to bring the expressive power of the the full set of Hypermedia Factors to an RDF-based media type.” (by Mike Amundsen)

Hypermedia-Driven RESTful Service Composition – “We explore RESTful service composition as it is driven by the hypermedia net that is dynamically created while a client interacts with a server resulting in a light-weight approach. We based our proposal on a hypermedia-centric REST service description, the Resource Linking Language (ReLL) and Petri Nets as a mechanism for describing the machine-client navigation.” (by Rosa Alarcon, Erik Wilde, and Jesus Bellido)

The domain model as REST anti-pattern – “The point that all of these types of articles miss is the HATEOAS part, the hyperlinking of resources. If you expose your domain model, basically saying “here’s all I got, use as you see fit”, there is no sensible way to create links between resources that expose the application state. There is no sensible way to tell the client “here’s what you can do next”, because the “REST” API allows anything at any time.” (by Rickard Öberg)

Back to Basics with Linked Data and HTTP – “I’ve always been of the opinion that this debate could have been avoided by keeping the responsibilities of each component of the Web separate and clean. The seperation should be: identify things using URIs, transfer information using HTTP, encode meaning in the data formats used in the transfer. Instead, we have special interpretations of certain parts of URIs and special interpretations of certain HTTP status codes to infer special meaning on the information being transferred. I think it’s time to stop blurring those responsibilities so I’m going back to basics.” (by Ian Davis)

JSON, XML and the Web – “There are still plenty of use cases for ‘documents’ of XML, but APIs on the web is not one of them.” (by Joe Gregorio)

Generic Media Types Potentially Leak The Model – “… He was worried that an MVC based approach to creating representations exposes the model to the service consumer. Interestingly, this is only possible if the service uses generic media types. Specific media types sufficiently limit the kind of information that can be expressed in the representations and prevent the service specific model to be visible to the outside.” (by Jan Algermissen)

Repurposing the Hash Sign for the New Web – W3C Working Draft, Putative TAG Finding: “The goal of this finding is to initially collect the various usage scenarios that are leading to innovative uses of client-side URI parameters, along with the solutions that have been developed by the Web community and make some architectural recommendations.” (by T.V. Raman and Ashok Malhotra)

REST versus SOAP for the Public Cloud – “For services tageted for the public cloud, REST is a better option than SOAP based Web Services.” (by Herbjörn Wilhelmsen)

Hypermedia APIs (“The rest of REST”) – Slides for a short presentation on REST APIs held at Oredev. (by Jon Moore)

SOAP and REST are not interchangeable – “Comparing the performance of REST to SOAP is like asking: “What tastes better? ‘Stir fried’ or ‘zucchini’?” or “Which one is better? ‘Darth Vader’ or ‘Star Trek’?” Those question just don’t make any sense. People who think that they do are probably the same who think that REST is nothing but “RPC via URI”, which of course it is not.” (by Juergen Brendel)


WS-REST 2011 – WS-REST 2011 is ON! The workshop was accepted by the WWW2011 so start dumping and shaping your RESTish thoughts into papers. You can follow the WSREST2011 twitter stream here.


Web of Things Cook-book! – “Meanwhile please enjoy the draft of our chapter, which is basically something we wanted to come up with for a long time: a cook-book on how to implement the Web of Things in your daily prototypes and/or products. This chapter was written in a way that it is accessible to a broad range of people not necessarily familiar with the core of modern Web-technologies.” (by Dominique Guinard, Vlad Trifa, Friedemann Mattern, Erik Wilde)

REST discussion group

A media type for case files, dossiers and documents – “Can anybody help with some inspiration for a media type for case files, dossiers and documents? This is for a project where we are going to exposethose kinds of govermental data.”

REST (Richardson) Maturity Model – missing “media types” level? – “In the richardson maturity model is explained by fowler. I´ve already seenthis in the recently published book “REST in practice”. I´m missing “mediatypes” between level 2 and 3. I think, before you may think about linkrel´s youshould think about proper media types…”

Representation Format in Hypertext – “I’m designing a REST API which support html and JSON. (might support XML later) It said that REST API should be hypertext-driven, so shall I put the format inURL of collection resource?”

HTML REST API example [was: Link relations] – Another “epic” (long) thread about link relations, m2m, media types and basically everything RESTful.

Interesting tweets

@Grumpydev – “@ryansroberts it’s not ReST unless someone is telling you you’re doing it completely wrong ;-)”

@dret – “hackable URIs are nice for debugging and ad-hoc navigation. when their patterns creep into code, they unnecessarily increase coupling. #REST

@AndrewWahbe – “It is the client that turns linked data into hypermedia. Without an appropriate client, data is just data.”

@dret – “the web isn’t great because it is an application platform. it’s great and unique because it is an information and service platform.”

@dret – “@mamund for loose coupling you need both data models and service models.#RDF is a data model, #REST is a service model.”

@mamund – “@dret#REST is a service model.” REST is arch model. #HTTP is representation-based app protocol that, used properly, offers low coupling.”

@ryah – “http clients are much harder than http servers”


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: