RE: Caveats for Web-friendly service description

Well, I asked the WS-RF folks to think about using HTTP for doing GETs
on the state of web service resources at their inaugural meeting in Apr
2004 [1], which I called WS-REST. 

They decided that they couldn't come up with new bindings, aka how to
take a SOAP message and use HTTP GET but not the soap 1.2 soap-response
mep.  I've noodled a bit on how to do this [2] but I'm thinking more and
more that SOAP folks are just in a different world, and so beit.  

Cheers,
Dave

[1] http://lists.oasis-open.org/archives/wsrf/200405/msg00018.html
[2]
http://www.pacificspirit.com/blog/2005/03/01/wsrest_continued_do_we_need
_an_http_transfer_soap_binding_and_simplified_wsdl


> -----Original Message-----
> From: public-web-http-desc-request@w3.org
[mailto:public-web-http-desc-
> request@w3.org] On Behalf Of Danny Ayers
> Sent: Wednesday, June 01, 2005 11:56 AM
> To: Mark Baker
> Cc: public-web-http-desc@w3.org
> Subject: Re: Caveats for Web-friendly service description
> 
> 
> On 6/1/05, Mark Baker <distobj@acm.org> wrote:
> 
> [snip]
> 
> You've reminded me of another set of specs around this space that I
> don't think have been mentioned yet : the Web Service Resource
> Framework [1] (OASIS), as used by the Grid folks amongst others. (I
> had a crack at making sense of the WS-Resource part at [2], a key
> aspect seems to be adding descriptions of state).
> 
> Cheers,
> Danny.
> 
> [1] http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrf
> [2] http://gridreporter.com/entry/1234000493034122/
> 
> --
> 
> http://dannyayers.com