W3C home > Mailing lists > Public > www-ws-arch@w3.org > December 2002

RE: WSA Properties (was RE: WSA constraints)

From: Champion, Mike <Mike.Champion@SoftwareAG-USA.com>
Date: Thu, 19 Dec 2002 10:03:25 -0700
Message-ID: <9A4FC925410C024792B85198DF1E97E404A7B8E7@usmsg03.sagus.com>
To: www-ws-arch@w3.org

> -----Original Message-----
> From: Mark Baker [mailto:distobj@acm.org]
> Sent: Thursday, December 19, 2002 11:57 AM
> To: Champion, Mike
> Cc: www-ws-arch@w3.org
> Subject: Re: WSA Properties (was RE: WSA constraints)
> I think all those you list are useful properties, but I'd be 
> happy just
> to focus on visibility, because I feel it's a required property, and
> that Web services don't have it.
> I wouldn't call the ability to create custom protocols a desirable
> property, because it sacrifices interoperability. 

I'm hoping we can avoid the normative judgments for now ... the point of the
exercise IMHO is to *describe* the extremes of a "pure" SOAP/WSDL
architecture on one hand and a pure REST architecture on the other hand.
Some of the properties will be the same for both, some will differ.
"Visibility" (although I'm not happy with the label) is certainly one on
which they differ. We can start with that, but I'd like to get a somewhat
larger list on the table.   For example, "Performance" was implicitly
mentioned in the discussion of the quote from Fielding that Chris dug up the
other day ... 

> Sorry for being dense.  I'm sure it was clearer on the call. 8-)

Uhh, no.  We know this is a rathole, and we are as confused as anyone. :-)
Received on Thursday, 19 December 2002 12:04:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:41:01 UTC