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

My comments on CDL on section 2.4.3 through 2.5.2

From: Charlton Barreto <charlton_b@mac.com>
Date: Tue, 7 Dec 2004 12:08:14 -0800
Message-Id: <BA02198A-488B-11D9-B7D9-000A95BD8B54@mac.com>
To: public-ws-chor@w3.org

 From the Nov 11 draft:

Section 2.4.3.1, page 24, paragraph 2:
"These functions can be used in any XPath expression as long as the 
types are compatible:xsd:time getCurrentTime(xsd:QName roleName)."
There should be a <CR> between "...compatible:" and "xsd:time 
getCurrentTime...".

Section 2.4.3.1, page 24, paragraph 7:
"xsd:boolean hasDeadlinePassed(xsd:dateTime deadlineTime, 
xsd:QNameroleName)"
This should be italicised to be consistent with the format of the 
preceding and following definitions.

Section 2.4.4, page 25, paragraph 4:
"A Token is an alias for a piece of data in a Variable or message...."
Can we change this to, "A Token is an alias for a data instance in a 
Variable or message..."?

Section 2.4.4, page 25, paragraph 5:
"Tokens types..." should be changed to "Token types...."

"...a Choreography definition avoid depending on specific message 
types, as described by WSDL, or a specific query string, as specified 
by XPATH, but instead the document part and the query string can change 
without affecting the Choreography definition."
Can we change this to, "..a Choreography definition avoids depending on 
specific message types, as described by WSDL, or a specific query 
string, as specified by XPATH.  Instead the document part and the query 
string can change without affecting the Choreography definition."

Section 2.4.5, page 26, paragraph 6:
"A Choreography. defines re-usable common rules..." should be changed 
to "A Choreography defines re-usable common rules...."

Section 2.4.6, page 30, paragraph 1:
"The optional repeat attribute allows, when the condition it specifies 
evaluates to "true", to make the current Work Unit that completed 
successfully to be considered again for matching...."
Can we change this to, "When evaluated to "true", the optional repeat 
attribute allows for making the current successfully completed Work 
Unit to be reconsidered for matching...."

Section 2.4.6. page 30, paragraph 2:
"The optional attribute block specifies whether the matching condition 
relies on the Variable that is currently available, or whether the Work 
Unit has to block waiting for the Variable to become available in the 
future if it is not currently available...."
Can we change this to, "The optional attribute block specifies whether:
- The matching condition relies on the currently available Variable, or,
- The Work Unit has to block waiting for the Variable to become 
available in the future...."

Section 2.4.8, page 32, paragraph 5:
"Two or more interactions MAY be marked as the Choreography 
initiator...."
Should this not be, ""One or more interactions MAY be marked as the 
Choreography initiator...." If so, then we should also change "In this 
case, the first action will initiate the Choreography and the other 
actions will enlist with the already initiated Choreography." to, 
"Where more than one interactions are marked as the initiator, the 
first action will initiate the Choreography and the other actions will 
enlist with the already initiated Choreography."
Received on Tuesday, 7 December 2004 20:08:22 GMT

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