Do RESTifarians want anything from the WSA that they don't alread y have?

> -----Original Message-----
> From: Mark Baker [mailto:distobj@acm.org]
> Sent: Thursday, August 01, 2002 11:51 AM
> To: Newcomer, Eric
> Cc: Mark Hapner; www-ws-arch@w3.org
> Subject: Re: A viewpoint on harvesting REST
> 
> 
> 
> IMO, REST is completely suitable for every use case and usage scenario
> (except for the ones that call out specific technologies) in our usage
> scenarios document.

[removing my Chair hat ...]

So, we're done?  :~)

Seriously, is there anything that a REST practicioner needs from the WSA
that isn't already in HTTP+XML+SOAP1.2?  A declarative description language?
A common security framework?  A way of grouping transactions that span a
single HTTP invocation?  

If the answer is "no", doesn't that mean you leave it up to the application
rather than the infrastructure to provide all that, and its just a "simple
matter of code"?

In my experience, "It's a simple matter of code" are famous last words in
many a career :~)