- From: Steve Ross-Talbot <steve@enigmatec.net>
- Date: Tue, 29 Jun 2004 11:12:55 +0100
- To: WS-Choreography List <public-ws-chor@w3.org>
Summary: Why specify a message type in the interaction? Description: Why specify a message type in the interaction? Why not in the associated WSDL? Could they be different? How do you guaranty that they cannot be different if specified in two different places? ------- Additional Comment #1 From Martin Chapman 2004-05-18 16:16 ------- think that there is no type in interact but needs tobe verified Discussion: You can guarantee that they are the same by design when generating end-points (which are WSDL), since the CDL describes a global model - it will not permit types to vary. The types in an interaction can or should be abstract and only at binding time should these become concrete types. At binding time if they do vary then it should result in some error or warning from a type perspective in CDL for some CDL based tool. Of course if the two services attempt to interact without CDL then some conformance error should be thrown anyway - so we have two levels of conformance checking one end-point based and one contextual (the CDL). Abstract types in CDL are just names. Proposal: Please can we discuss this in order to clarify and then resolve.
Received on Tuesday, 29 June 2004 06:13:06 UTC