W3C home > Mailing lists > Public > www-ws-desc@w3.org > October 2003

Re: New issue [distobj@acm.org: Re: What does WSDL describe?]

From: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
Date: Thu, 23 Oct 2003 18:37:48 +0600
Message-ID: <00f101c39962$79e8cad0$36356a20@lankabook2>
To: "Mark Baker" <distobj@acm.org>, <www-ws-desc@w3.org>

Can you succinctly state the issue please? I don't to wade thru
this thread and figure out something else.

Sanjiva.

----- Original Message -----
From: "Mark Baker" <distobj@acm.org>
To: <www-ws-desc@w3.org>
Sent: Friday, October 24, 2003 4:56 PM
Subject: New issue [distobj@acm.org: Re: What does WSDL describe?]


>
> BTW, I'd like to raise the issue mentioned here as an official one
> with the WG.  Thanks.
>
> ----- Forwarded message from Mark Baker <distobj@acm.org> -----
>
> From: Mark Baker <distobj@acm.org>
> To: Savas Parastatidis <Savas.Parastatidis@newcastle.ac.uk>
> Cc: www-ws-desc@w3.org, Jim Webber <jim.webber@arjuna.com>
> Subject: Re: What does WSDL describe?
> Date: Thu, 23 Oct 2003 21:45:53 -0400
> User-Agent: Mutt/1.2.5.1i
> X-RegEx-Original-IP: 18.29.1.71
> X-Original-To: www-ws-desc@frink.w3.org
> Delivered-To: www-ws-desc@frink.w3.org
> Delivered-To: www-ws-desc@w3.org
> In-Reply-To: <BC28A9E979C56C44BCBC2DED313A4470021C388E@bond.ncl.ac.uk>;
from Savas.Parastatidis@newcastle.ac.uk on Fri, Oct 24, 2003 at 12:01:01AM
+0100
> X-Archived-At: http://www.w3.org/mid/20031023214553.A9730@www.markbaker.ca
> X-Mailing-List: <www-ws-desc@w3.org> archive/latest/2964
> List-Id: <www-ws-desc.w3.org>
> List-Help: <http://www.w3.org/Mail/>
> List-Unsubscribe: <mailto:www-ws-desc-request@w3.org?subject=unsubscribe>
> X-OriginalArrivalTime: 24 Oct 2003 01:45:42.0606 (UTC)
FILETIME=[88EE1EE0:01C399D0]
> X-Spam-Status: No, hits=-3.5 required=5.0
> tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_02_03,
>       USER_AGENT,USER_AGENT_MUTT,X_LOOP,X_MAILING_LIST
> version=2.43
> X-Spam-Level:
>
>
> Thanks for your response, Savas, it was very helpful.  I'll just cut
> to what appears to be the source of my confusion ...
>
> On Fri, Oct 24, 2003 at 12:01:01AM +0100, Savas Parastatidis wrote:
> > I wouldn't call the above description as a "document endpoint" but
> > effectively we are talking about exchange of documents (the messages).
>
> Ok, but you're really talking about the exchange of two very different
> kinds of documents; ones that contain only state (e.g. "12345"), and
> ones that contain an operation and state (e.g. "add(12345)").  My
> concern and confusion stems from the two apparently being treated the
> same.
>
> As a concrete example relevant to interoperability, consider the
> semantics of a successful SOAP response to each of those two example
> messages above.  For the first example, the response message can be
> interpreted to mean "that data is successfully processed", which could
> mean many things, but that's hidden from the client.  But in the
> second example, what does success mean?  Does it mean that the data was
> processed, or does it mean that the number 12345 was added to whatever
> the existing state was?  It could mean both.  And when you combine that
> with the issue Umit is talking about, it's even more ambiguous, as it
> could mean something else entirely because the operation may not be in
> the message. i.e. it could mean the same as "add(12345)", though only
> "12345" is on the wire.  Yikes!
>
> Mark.
> --
> Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
>
> ----- End forwarded message -----
>
> --
> Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
Received on Friday, 24 October 2003 08:35:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:27 GMT