Proposal to support WSDL2

Proposed changes to support any WSDL2 MEPs:



2.5.2 Interacting

Current text:

An Interaction is initiated when a party playing the requesting Role sends a 
request message, through a common Channel, to a party playing the accepting 
Role that receives the message. The Interaction is continued when the 
accepting party, sends zero or one response message back to the requesting 
party that receives the response message. This means an Interaction can be 
one of two types:

· A <emph>One-Way Interaction </emph>that involves the exchanging of a 
single message

· A <emph>Request-Response Interaction </emph>when two messages are 
exchanged



Change to:

An Interaction is initiated when one of the Roles participating in the 
interaction sends a message, through a common Channel, to the other Role 
that is participating in the interaction, that receives the message. If the 
initial message is a request, then the accepting Role can optionally respond 
with a normal response message or a fault message, which will be received by 
the initiating Role.



2.5.2.2

Current text:

The one-way, request or response messages in an Interaction may also be 
implemented using a <emph>Protocol Based Exchange </emph>where a series 
of....

Change to:

The messages in an Interaction may also be implemented using a 
<emph>Protocol Based Exchange </emph>where a series of......





2.5.2.4

Current text:

The operation attribute specifies a one-way or a request-response operation. 
The specified operation belongs to the interface, as identified by the role 
and behavior elements of the Channel Type of the Channel Variable used in 
the Interaction activity.

Change to:

The operation attribute specifies the name of the operation that is 
associated with the interaction. The specified operation belongs to the 
interface, as identified by the role and behavior elements of the Channel 
Type of the Channel Variable used in the Interaction activity.

Received on Tuesday, 19 October 2004 15:00:08 UTC