W3C home > Mailing lists > Public > public-awwsw@w3.org > February 2011

Re: hold up

From: Nathan <nathan@webr3.org>
Date: Sat, 26 Feb 2011 10:17:49 +0000
Message-ID: <4D68D34D.8090606@webr3.org>
CC: AWWSW TF <public-awwsw@w3.org>, Jonathan Rees <jar@creativecommons.org>
Nathan wrote:
> I've just been reading huge chunks of archived messages again, and 
> there's a consistent phrase coming out that's just flat out wrong.
>   "a representation of the resource"
> that's not what HTTP and the specs say, a representation is a 
> representation of the current or intended state of a resource. not a 
> representation of the resource.
> A resource is a stateful abstraction whose state is managed by an 
> abstract protocol, the abstract protocol is realized via various machine 
> protocols (such as http) which manage the state of the resource via 
> messages and pass full or partial representations of the 
> current/intended state in various lexical forms.
> Thus, an http/rest resource can *only* be something that has the 
> property of having it's state (even partially) managed via a transfer 
> protocol, something in the realm of the machine.
> the weather in london cannot be a rest resource, unless you can 
> represent or manipulate it's current state via HTTP, which you can't, 
> you can only represent or manipulate information about the weather in 
> london with a transfer protocol.

[[ the HTTP interface is a property of that resource ]]

an HTTP resource can only be a thing which can have the HTTP interface 
as one of its properties.
Received on Saturday, 26 February 2011 10:20:09 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:21:09 UTC