W3C home > Mailing lists > Public > public-ws-chor@w3.org > April 2003

RE: Progressive Concreteness of Choreography binding

From: Patil, Sanjaykumar <sanjay.patil@iona.com>
Date: Wed, 2 Apr 2003 14:04:19 -0800
To: "Ricky Ho" <riho@cisco.com>, <public-ws-chor@w3.org>

This is good. With the example, we can now make the abstract discussion more concrete :-)

a> Do we need message definitions in the choreography? Wouldn't message properties be sufficient?
b> Is our model to define the choreography with POHandlingProcess at the center of the universe? Based on whether we define it as a collaboration or as individual role's process, the language will change. 
   For example, if we were to follow a collaboration model, the first statement in the Process construct will be something like 'Partner "seller" to receive "PO" from partner "purchaser"' instead of 'receive "PO" from partner "purchaser"'
c> What is the purpose of "Message binding" in the Implementation Binding? Perhaps this is related to question a> above. Wouldn't Message Property binding be sufficient?
d> Assuming that there is an individual Implementation Binding for each role involved in the shared collaboration, the Partner binding can be to identify the choreography interface of each partner. The choreography interface of "mySelf" may not be needed as it becomes part of the other roles' implementation binding.


Sanjay Patil
Distinguished Engineer
IONA Technologies
2350 Mission College Blvd. Suite 650
Santa Clara, CA 95054
Tel: (408) 350 9619
Fax: (408) 350 9501
Making Software Work Together TM

-----Original Message-----
From: Ricky Ho [mailto:riho@cisco.com]
Sent: Wednesday, April 02, 2003 1:07 PM
To: public-ws-chor@w3.org
Subject: Progressive Concreteness of Choreography binding

Continuing our discussion of "abstract message".  I want to show an how we 
can start with a very abstract definition at the choreography and 
progressively add concrete binding to that.

Lets define a orchestration flow that is independent of message type and 
only have the message properties concept.

At the very beginning, the process declares the "NAMES" of all messages 
that it may send or receive.  It also declares the "NAMES" and "TYPES" of 
message properties, but it doesn't say how the message properties is 
extracted from the message.

Within the process flow, it uses only the named "message" and "message 

Orchestration POHandlingProcess {
	Partner declaration {

	Message declaration { // all are "typeless"

	Message Property declaration { // all are "typed"
		float PO.dollarAmount
		Customer PO.cust
		Customer CreditCheckRequest.cust
		int CreditCheckResponse.rating

	Process {	
		receive "PO" from partner "purchaser"
		if ("PO.dollarAmount" > 100K) {
			assign "PO.cust" to "CreditCheckRequest.cust";
			send "CreditCheckRequest" to partner "creditCheckProvider";
			receive "CreditCheckResponse" from partner "creditCheckProvider";
			if ("CreditCheckResponse.rating" > 3) {
				send "POConfirmation" to partner "purchaser"
			} else {
				send "PORejection" to partner "purchaser"
		send "POConfirmation" to partner "purchaser"

The WSDL implementation binding basically map the partner into a particular 
WSDL PortType.  Then it maps each named message (defined in abstract 
process) into the WSDL PortType/Operation/Part (can be either the request 
or the response).  Finally, it defines the message properties in terms of 
XPATH which extract the data from the corresponding message.

Implementation Binding for "POHandlingProcess" {
	Partner binding {
		mySelf --> PortType POHandlingPT  // contains a one-way "submitPO" operation
		purchaser --> PortType POCallbackPT // contains 2 one-way "confirmPO", 
"rejectPO" operations
		creditCheckProvider --> CreditCheckPT // contains a request/reply "check" 

	Message binding {
		PO --> From request of (PortType = "POHandlingPT", Operation = 
"submitPO", Part="po")
		POConfirmation --> To request of (PortType = "POCallbackPT", Operation = 
"confirmPO", Part="poConfirmation");
		PORejection --> To request of (PortType = "POCallbackPT", Operation = 
"rejectPO", Part="poRejection");
		CreditCheckRequest --> To request of (PortType = "CreditCheckPT", 
Operation = "check", Part="customerInfo");
		CreditCheckResponse --> From response of (PortType = "CreditCheckPT", 
Operation = "check", Part="Return");

	Message Property binding {
		PO.dollarAmount = XPATH(//totalAmount/@amount);
		Customer PO.cust = XPATH(//customer);
		Customer CreditCheckRequest.cust = XPATH(//customer);
		int CreditCheckResponse.rating = XPATH("//rank");

This binding defines how the abstract message defined in WSDL is serialized 
on the wire, such as which parts goes to SOAP header and which goes to SOAP 
WSDL binding covers this.

For dynamic address resolution, this defines the service provider endpoint 
resolution mechanism.  For static address resolution, this defines the 
actual service endpoint location.


Received on Wednesday, 2 April 2003 17:04:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:00:58 UTC