W3C home > Mailing lists > Public > public-ws-chor@w3.org > November 2004

Proposed Amendments to WS-CDL 10th November version used as input to last F2F

From: Steve Ross-Talbot <steve@enigmatec.net>
Date: Tue, 30 Nov 2004 13:57:28 +0000
Message-Id: <C5A94E4C-42D7-11D9-AE3E-000393D13C9A@enigmatec.net>
To: WS-Choreography List <public-ws-chor@w3.org>

URL to document reviewed:
http://lists.w3.org/Archives/Member/member-ws-chor/2004Nov/att-0011/ 
cdl_v1-editors-nov10-2004-XML.pdf
Taken from members mailing list:
http://lists.w3.org/Archives/Member/member-ws-chor/2004Nov/0011.html

Reviewed upto but not including section 2.4.2 and here are my proposed  
changed

Summary
	- 3 Questions
	- 1 Suggestion (no proposed text)
	- 24 specific changes


GLOBAL CHANGE
1) Replace "Choreography Language" with "Choreography Description  
Language" in all places.

SPECIFIC CHANGES:

Section: Status of this document
2) "This is the First Public Working Draft of the Web Services  
Choreography Description Language document. "
DIRECTION: Should read
"This is the Nth Public Working Draft of the Web Services Choreography  
Description Language document. "
Where Nth is the appropriate number for the working drafts of the  
working group.


3) "Although the Working Group agreed to request publication of this  
document, this document does not represent  consensus within the  
Working Group about Web Services Choreography description language."
DIRECTION: Should read
"This document represents consensus within the Working Group about the  
Web Services Choreography description language."

4) " It is an early stage document and major changes are expected in  
the near future."
DIRECTION: Delete

5) "This is a draft document and may be updated, replaced or obsoleted  
by other documents at any time. It is inappropriate to cite this  
document as other than work in progress."
DIRECTION: Not sure but this look like is ought to be modified given we  
shall seek to move to last call.

Section:  Revision Description

6) "This is the second editor's draft of the document. "
DIRECTION: Should be modified as above comments.

Section: 1. Introduction

7)"Business Process Languages layer: describes the execution logic of  
Web Services based applications by defining their control flows...."
SUGGESTION: Can we wordsmith the text for this section to bring out the  
end-point aspects of a BPL layer?

8) "The Web Services Choreography specification is targeted for  
composing  interoperable, collaborations between any type of party  
regardless of the supporting platform or programming model used by the  
implementation of the hosting environment."
DIRECTION: Replace as follows:
"The Web Services Choreography specification is aimed at the  
composition of interoperable, collaborations between any type of party  
regardless of the supporting platform or programming model used by the  
implementation of the hosting environment."

Section: 1.2 Purpose of a Choreography Language

9) "1.2 Purpose of a Choreography Language"
DIRECTION: Replace as follows:
"1.2  Purpose of the Choreography Description Language"

10) "The figure below demonstrates a possible usage of the Choreography  
Language."
DIRECTION: Replace as follows:
"The figure below demonstrates a possible usage of the Choreography  
Description Language."

11) "They then generate a Choreography Language based representation."
DIRECTION: Replace as follows:
"They then generate a Choreography Description Language based  
representation."

12) "Business or other activities that involve multiple different  
organizations"
DIRECTION: Replace as follows
"Business or other activities that involve different organizations"

13) "The Web Services Choreography specification is targeted for  
precisely describing collaborations between any type of party  
regardless of the"
DIRECTIONS: Replace as follows
"The Web Services Choreography specification is aimed at being able to  
precisely describe collaborations between any type of party regardless  
of the"

14) "Using the Web Services Choreography specification, a contract  
containing a "global" definition of the common ordering conditions and  
constraints under which messages are exchanged is produced that  
describes from a global viewpoint the common and complementary  
observable behavior of all the parties involved. Each party can then  
use the global definition to build and test solutions that conform to  
it."
DIRECTION: Replace as follows:
"Using the Web Services Choreography specification, a contract  
containing a "global" definition of the common ordering conditions and  
constraints under which messages are exchanged, is produced that  
describes, from a global viewpoint, the common and complementary  
observable behavior of all the parties involved. Each party can then  
use the global definition to build and test solutions that conform to  
it."

15) "The main advantage of a contract with a global definition approach  
is that it separates the process being followed by an individual  
business or system within a "domain of control" from the definition of  
the sequence in which each  business or system exchanges information  
with others. This means that, as  long as the "observable" sequence  
does not change, the rules and logic  followed within the domain of  
control can change at will."
DIRECTION: Replace as follows;
"The advantage of a contract based on a global viewpoint as opposed to  
anyone endpoint is that it separates the overall "global" process being  
followed by an individual business or system within a "domain of  
control" (an endpoint) from the definition of the sequences in which  
each  business or system exchanges information with others. This means  
that, as  long as the "observable" sequences do not change, the rules  
and logic  followed within a domain of control (endpoint) can change at  
will and interoperability is therefore guaranteed."

16) "Choreography as determined by the common view"
DIRECTION: Replace as follows:
"Choreography as determined by the common or global view"

17) "Company “B”, having greater legacy driven integration needs,  
relies on a J2EE [25] solution incorporating Java and Enterprise Java  
Bean Components or a .NET [26] solution incorporating C# to implement  
its own part of the Choreography"
DIRECTION: Replace as follows:
""Company “B”, having greater legacy driven integration needs, relies  
on a J2EE [25] solution incorporating Java and Enterprise Java Bean  
Components and a .NET [26] solution incorporating C# to implement its  
own part of the Choreography""

Section: 1.3 Goals

18) "The primary goal of a Choreography Language is to specify a  
declarative, XML based language that defines from a global viewpoint  
the common and  complementary observable behavior, where information  
exchanges occur,  and when the jointly agreed ordering rules are  
satisfied. "
DIRECTION: Replace as follows:
"The primary goal of a Choreography Description Language is to specify  
a declarative, XML based language that defines from a global viewpoint  
the common and  complementary observable behavior specifically where  
information exchanges may occur and  the jointly agreed ordering rules  
that need to be satisfied. "

19) "Some additional goals of this definition language are to permit"
DIRECTION: Replace as follows:
"More specifically the goals of Choreography Description Language are  
to permit"

20) "•  Information Driven Collaboration. Choreographies describe how  
parties make progress within a collaboration, when recordings of  
exchanged  information and observable information changes cause  
ordering  constraints to be fulfilled
•  Information Alignment. Choreographies allow the parties that take  
part  in Choreographies to communicate and synchronize their   
observable information changes and the actual values of the  exchanged  
information as well"
DIRECTION: Replace as follows:
"•  Information Driven Collaboration. Choreographies describe how  
parties make progress within a collaboration, through the recording of  
exchanged  information and changes to observable information that cause  
ordering  constraints to be fulfilled and progress made
•  Information Alignment. Choreographies allow the parties that take  
part  in Choreographies to communicate and synchronize their observable  
information"

21) "•  Transactionality. The processes or parties that take part in a  
Choreography can work in a "transactional" way with the ability to  
coordinate the outcome of the long-lived collaborations, which  include  
multiple, often recursive collaboration units, each with its  own  
business rules and goals."
DIRECTION: Replace as follows:
"•  Transactionality. The processes or parties that take part in a  
Choreography can work in a "transactional" way with the ability to  
coordinate the outcome of the long-lived collaborations, which  include  
multiple participant each with their  own business rules and goals."

Section: 1.5 Relationship with Business Process Languages

22) "A Choreography Language is not an "executable business process  
description language" or an implementation language."
DIRECTION: Replace as follows:
"A Choreography Description Language is not an "executable business  
process description language" or an implementation language."

Section: 2.1 The Model Overview

23) "A Participant Type is grouping together the parts of the  
observable behavior that must be implemented by the same entity or   
organization"
DIRECTION: Replace as follows:
"A Participant Type is a grouping together of those parts of the  
observable behavior that must be implemented by the same entity or   
organization"

24) "Initially, the collaboration is started at a specific business  
process,"
QUESTION: Do we mean "at a specific endpoint" or "at a specific role"  
or "at a specific participant playing a particular role"?
If we do mean something like this we would be better using this  
terminology rather than referring to "business process".

25) "•  Choreography Finalizer Block - A Finalizer Block describes what  
additional interactions should occur to reverse the effect of an  
earlier successfully completed Choreography"
QUESTION: I do not believe this to be correct any longer as a finalizer  
block is enacted when it has completed so it may be incorrect to tie it  
to the notion of "reversal". Am I correct in my understanding?

Section: 2.3.2 Relationship Types

26) "The syntax of the relationshipType construct is: "
QUESTION: What was the resolution on the use of 'role type="qname"'?  
I'm pretty sure there was a discussion.

Section 2.3.4 Channel Types

27) "The element passing allows only a Channel of “ConsumerChannel”  
Type to be passed in a request information  exchange thought a Channel  
of “RetailerChannel” Type."
DIRECTION: Replace as follows:
""The element passing allows only a Channel of “ConsumerChannel” Type  
to be passed in a request information  exchange through a Channel of  
“RetailerChannel” Type."

Section: 2.4  Information Driven Collaboration

28) "Parties make progress within a collaboration, when recordings of  
exchanged information and observable information changes cause ordering  
constraints to be fulfilled. A WS-CDL document allows defining  
information within a Choreography that can influence the observable  
behavior of the collaborating parties."
DIRECTION: Replace as follows:
"Parties make progress within a collaboration, when recordings of  
exchanged information are made and changes to observable information  
occur that then cause ordering constraints to be fulfilled. A WS-CDL  
document allows  the information within a Choreography that can  
influence the observable behavior of the collaborating parties to be  
described."

Section: 2.4.1 Information Types

29) "The type of information is of one of these types exclusively."
DIRECTION: Replace as follows:
"The type of information is exclusively one of the aforementioned."
Received on Tuesday, 30 November 2004 13:57:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 01:01:11 GMT