Minutes WS Choreography WG conference call 30 August 2005

IRC: http://www.w3.org/2005/08/30-ws-chor-irc
Agenda: http://lists.w3.org/Archives/Public/public-ws-chor/2005Aug/att-0024/Agenda20050830-0.txt


Latest Editors Draft is at:
        http://www.w3.org/2002/ws/chor/edcopies/cdl/cdl.html

1. Role Call
------------
Nick, Steve, Gary, Monica, Yves, Charlton (on IRC)

Apologies:
        Martin, Charlton

2. Confirm scribe
-----------------
        Steve is scribe

3. Agenda Changes
-----------------
        No Changes

4. Minutes of last meeting
---------------------------
        25th August 2005
                http://lists.w3.org/Archives/Member/member-ws-chor/2005Aug/att-0041/minutes_20050825-1.txt
SRT: Objected to minutes on basis of lack of clarity
ACTION: Nick/Monica to review the minutes and add clarity

5. Action item review
---------------------
        1. ACTION:  To editors use this to make it consistent in the defs of roleType, participantType, relationshipType
        IN PROGRESS
        2. ACTION: for the group to review on the latest CDL editors draft (that is going to be sent by Greg to the member's list)
        SUSPENDED - Pending draft to review
        3. ACTION: Editors to change "MAY" to lower case "may"
        IN PROGRESS
08:30PM <charlton> I would like to ask if Item 3 can be clarified\
08:30PM <charlton> Because some "MAY"s are normative (and RFC 2119)\
08:32PM <charlton> it would be serendipitous to have this clarified as I have the pen :-)\
        4. ACTION: Editors to apply change above.
        IN PROGRESS
        5. ACTION: Note to editors, when putting text in (new, or from the proposals) always make it consistent with the text in the spec (like lower v in variable, roleType with no spacing, etc.)
        IN PROGRESS
        6. ACTION: Chairs to check next call to see if this was accepted
        It was reported that the text proposed in the last minutes was adopted
        DONE
        7. ACTION: Editors to make necessary changes as above.
        IN PROGRESS

Yves notes that the  updated latest edcopy at http://www.w3.org/2002/ws/chor/edcopies/cdl/cdl.html

6. Issues
-------------
        Modified text for Channel Types to agree upon:
                http://www.w3.org/2002/ws/chor/edcopies/cdl/cdl.html#ChannelType

        Normative language changes ....
        It was noted that the changes to normative language in http://lists.w3.org/Archives/Member/member-ws-chor/2005Aug/0043.html changes will be applied by Charlton. It makes sense because Charlton worked with Monica to do the normative text because they authored the reference above.
ACTION: On Editors: Nomative language changes is to be picked up and applied by the editors

Gary's comments are at: http://lists.w3.org/Archives/Member/member-ws-chor/2005Aug/0042.html
Gary:  Enforce that a passed channel instance is always distinct
       Can we find a better way of saying: "enforce that a passed channel instance is always distinct"
Steve: Perhaps "unique" In which case\
08:44PM > "The OPTIONAL attribute new within the passing element, when set to "true", enforces a passed channel instance to be always distinct. If the element passing is missing, then this channelType MAY be used for exchanging information, but MUST NOT be used for passing channel instances of any channelType."
08:44PM > Becomes:
08:47PM >  "The OPTIONAL attribute new within the passing element, when set to "true", enforces a passed channel instance to be always unique. If the element passing is missing, then this channelType MAY be used for exchanging information, but MUST NOT be used for passing channel instances of any channelType."
Part 2:
<nick> Enforce that a passed channel instance is unique
The 4th bullet before the syntax on 4.4 will need to be changed in accordance with this.
CHANGES ABOVE ARE AGREED (4th bullet and text in log above)

The paragraph starting: 
"The element reference is used to specify the type of a participant reference, conveying the information needed to address the participant being the target of an information exchange, which is used for dynamically"
Change: Insert a new line before the start of the text.
CHANGE AGREED

Exceptions discussion
Charlton's email is at: http://lists.w3.org/Archives/Public/public-ws-chor/2005Aug/0026.html
Chair note: 10 min discussion without reaching any conclusion
charlton: I'm working to get my example out by the end of this week, so as to facilitate discussion at next weeks call
Nick: Refers everyone to  http://www.w3.org/2002/ws/chor/edcopies/cdl/cdl.html#Interacting
Nick: Within the exchange element, the OPTIONAL faultName  attribute is used to identify this exchange element as a fault exchange with the specified name. If the faultName attribute is specified, then it will be used to identify the specific fault within the context of the operation. If the operation is defined using WSDL, this will occur in the following way:
Nick: In WSDL/CDL faultName always points to fault operation in WSDL. But in BPEL it is associated with a QName only. We could therefore say that the QName coming from anywhere could map to a faultName in CDL.
Gary: suggests that "causeException="qname"" in the exchange can be used to do this today

Binding of the qname to something specific is then a separate binding problem.
ACTION: Chair to send this fragment to the public list for further discussion.

7. AOB
Monica raised the issue for the next F2F.
ACTION: Next F2F on the agenda for the next week
ACTION: to editors: in section 5.6 all the examples should be in 'yellow'

There being no further business meeting adjourned

SUMMARY OF ACTION ITEMS

        1. ACTION:  To editors use this to make it consistent in the defs of roleType, participantType, relationshipType
        2. ACTION: for the group to review on the latest CDL editors draft (that is going to be sent by Greg to the member's list)
        SUSPENDED ...
        3. ACTION: Editors to change "MAY" to lower case "may"
        4. ACTION: Editors to apply change above.
        5. ACTION: Note to editors, when putting text in (new, or from the proposals) always make it consistent with the text in the spec (like lower v in variable, roleType with no spacing, etc.)
        6. ACTION: Editors to make necessary changes as above.
        7. NEW ACTION: Nick/Monica to review the minutes and add clarity
        8. NEW ACTION: On Editors: Nomative language changes is to be picked up and applied by the editors
        9. NEW ACTION: Chair to send this fragment to the public list for further discussion.
        10. NEW ACTION: Next F2F on the agenda for the next week
        11. NEW ACTION: to editors: in section 5.6 all the examples should be in 'yellow'