Hi Jan, all: Jan wrote: > So, is this an order? > > receiver.cancel( > > <ns:order xmls:ns="[xsd-target-namespace]> > <item1>...</item1> > <item2>...</item2> > <item3>...</item3> > <shippingAddress>...</shippingAddress> > <billingAddress>...</billingAddress> > </ns:order> > ) > > > > > And how would you ever be sure that cancel() had the same > semantics by the time you invoke it as it had when you read > the WSDL?
The same way you're sure that POSTing "<cancel>" to http://RESTsvc.com/PO5432 has the same semantics as it had when you read the... um, I guess the human-readable web page describing the purchase order setup and semantics at RESTsvc.com? Is that any different, really? As Steve and others have noted, agreement MUST be there at ALL levels of the stack (incl semantics and interpretation of particular data serializations) for a successful interaction. That seems to me to be a truism of computing in general, as much for REST as it is for SOA as it is for in-process usage of third-party code libraries. Thus I'm having trouble understanding what you're getting at here? --Glen
