- From: Mark Baker <distobj@acm.org>
- Date: Sat, 25 Oct 2003 20:45:07 -0400
- To: Anne Thomas Manes <anne@manes.net>
- Cc: Savas Parastatidis <Savas.Parastatidis@newcastle.ac.uk>, "paul.downey@bt.com" <paul.downey@bt.com>, www-ws-desc@w3.org, Jim Webber <jimwebber@hotmail.com>, distobj@acm.org
On Sat, Oct 25, 2003 at 02:34:28PM -0400, Anne Thomas Manes wrote: > Savas, > > Thanks for providing an example to help us gel our thoughts. > > Case 1: If the dealer uses one form for both motorcycles and cars, one > would assume that from a Web services perspective, the dealer offers one > interface with one operation (SubmitOrder) which accepts as an input > message (OrderForm1). As you say, the dealer's service understands the > semantics of OrderForm1 and can determine based on the contents of an > attribute or an element whether the order is for a motorcycle or a car. > There's no need to specify the operation name on the wire because the > receiving SOAP node knows what to do when it receives an OrderForm1. Would that still work if the operation were "SubmitDocument" rather than "SubmitOrder"? Mark.
Received on Saturday, 25 October 2003 20:46:21 UTC