Re: New issue: Representing safe operations (was: [TAG] how to use GET to make resources addressable)

This sounds reasonnable. (Being a member of the XMLP GET TF, though, I
don't think this particular issue will go away.)

Jean-Jacques.

Paul Cotton wrote:

> I suggest you wait until we see the solution that the XML Protocol WG
> supplies for making GET work with SOAP 1.2.  The TAG will be evaluating
> this in the very near future (e.g. when the work is done).
>
> /paulc
>
> Paul Cotton, Microsoft Canada
> 17 Eleanor Drive, Nepean, Ontario K2E 6A3
> Tel: (613) 225-5445 Fax: (425) 936-7329
> <mailto:pcotton@microsoft.com>
>
> > -----Original Message-----
> > From: Sanjiva Weerawarana [mailto:sanjiva@watson.ibm.com]
> > Sent: Tuesday, June 04, 2002 3:49 PM
> > To: Web Service Description
> > Subject: Re: New issue: Representing safe operations (was: [TAG] how
> to
> > use GET to make resources addressable)
> >
> >
> > Can we wait until they explicitly raise it against us or do
> > we need to preempt that?
> >
> > Sanjiva.
> >
> > ----- Original Message -----
> > From: "Jean-Jacques Moreau" <moreau@crf.canon.fr>
> > To: "Web Service Description" <www-ws-desc@w3.org>
> > Sent: Tuesday, May 21, 2002 2:56 PM
> > Subject: New issue: Representing safe operations (was: [TAG] how to
> use
> > GET
> > to make resources addressable)
> >
> >
> > > I think the TAG has implicitely raised the following issue:
> > >
> > > <quote href="http://www.w3.org/2001/tag/doc/get7">
> > > WSDL 1.1 provides a binding to HTTP GET, which makes it possible
> > > to respect the principle of using GET for safe operations, but to
> > > more straightforwardly represent safety, it should be a property
> > > of operations themselves, not just a feature of bindings.
> > > </quote>
> > >
> > > Sanjiva, it looks like this is a Part 1 issue.
> > >
> > > Jean-Jacques.
> > >

Received on Wednesday, 5 June 2002 08:35:06 UTC