lack of GET support in SOAP conflicts with giving URIs to important resources

In the course of addressing a TAG issue
  http://www.w3.org/2001/tag/ilist#whenToUseGet-7

and in particular, in discussion of

  DRAFT Findings on when to use GET to make resources addressable
  ref. issue whenToUseGet-7

  DRAFT by Dan Connolly, for the TAG.
  in progress: update w.r.t. 5May discussion

  $Revision: 1.12 $ of $Date: 2002/05/17 20:06:35 $
  http://www.w3.org/2001/tag/doc/get7

at our 5 May meeting, we decided as follows:

RESOLVED.The TAG finds that the absence of a GET binding in SOAP is
incompatible with the architecture of the Web, in that it contravenes
the architectural principle that important information resources should
have URIs. The TAG appreciates the urgency in completing the SOAP 1.2
specifications and wants to work with those concerned to address this
problem with the least disruption possible.

ACTION to DC to send a message to the XML Protocol comments list to
point to this resolution.

  -- http://www.w3.org/2001/tag/2002/0505-agenda#L905


If you review the record of the meeting, you'll
see that the TAG discussed a number of specific ways to
address this conflict, but didn't come to consensus
on any of them. We invite you to review the options
we discussed and choose any of those, or suggest
some other way to resolve this conflict.

-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/

Received on Friday, 17 May 2002 16:51:11 UTC