ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> xml-dev
xml-dev
Re: [xml-dev] SOAP and the Web
by Didier PH Martin other posts by this author
May 2 2002 7:12PM messages near this date
Re: [xml-dev] SOAP and the Web | RE: [xml-dev] SOAP and the Web
Hi Paul,

Paul said:
>  Query parameters are NOT representations of resource. Query parameters
>  are part of the address for resources. The representation is the thing
>  that you get when you do a GET or the thing that you PUT or POST.

Didier replies:
Let's add that there is a one to one relationship between a URL and a
resource and a one to one relationship between a resource and a
representation. Therefore there is a one to one relationship between a URL
and a resource. Let's say also that the representation is the manifestation
of a particular URL.
So

URL <-(1,1)-> Resource <- (1,1)-> representation. => URL <- (1,1)->
representation.

It is easy then to see why for people, concretely a resource is what is
referred by a URL and that the resource is the outcome we get when GETting a
resource.

In REST, each URL is a different resource. A resource is unique. What we get
by performing an HTTP GET is a representation of this resource. Therefore we
can say that the representation is some sort of physical (OK, in bits and
bytes or encoded with characters) incarnation of an etherized monad named a
resource. People skip the etherized monad and make the direct connection
Resource <--->  URL (resource being - in that case - what I get with an HTTP
GET). So maybe we can say to make things clear:

a) The resource is an abstract entity representing something on the web. Its
a metaphysical monad, an abstarct thing associated to a concrete thing: the
representation.
b) A resource may be identified by a URI. More particularly its location
represented by a URL and its name by a URN.
c) The outcome of an HTTP GET operation on a particular resource identified
by a particular URI is its representation.

However, a resource has not:
a) several representations
b) several URIs.

cheers
Didier PH Martin


-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org> , an
initiative of OASIS <http://www.oasis-open.org> 

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl> 
Thread:
Bullard, Claude L (Len)
Didier PH Martin
Francis Norton
Thomas B. Passin
Thomas B. Passin
Didier PH Martin
Julian Reschke
Didier PH Martin
Jeff Greif
John Cowan
Francis Norton
Paul Prescod
Paul Prescod
Francis Norton
Paul Prescod
Andrew Dubinsky
Didier PH Martin

Privacy Policy | Email Opt-out | Feedback | Syndication
© 2004 ActiveState, a division of Sophos All rights reserved