Minutes WS Choreography WG conference call 5 April 2005
IRC log: logging to http://www.w3.org/2005/04/05-ws-chor-irc
Agenda: http://lists.w3.org/Archives/Public/public-ws-chor/2005Apr/att-0001/Agenda-04042005-0.txt
1. Role Call:
-------------
Charlton, Martin, Greg, Nick, Tony, Monica, SRT, Yves
2. Scribe:
----------
Monica
4. Approval of minutes:
-----------------------
Approved minutes 29 March 2005
http://lists.w3.org/Archives/Member/member-ws-chor/2005Mar/att-0007/minutes_20050329_-_0.txt
5. Action item review:
----------------------
1. ACTION: Martin to do UML diagram from scratch for CDL
IN PROGRESS
2. ACTION: SRT Check 1027 for issues pertaining to identity
IN PROGRESS
3. ACTION: Add text in primer or spec to clarify participant relationship/role pertaining to issue 1027
IN PROGRESS
4. ACTION: Chairs to talk with the XPath 2.0 WG to determine the direction of three-valued
logic and existential qualifiers
IN PROGRESS
5. ACTION: SRT to create a new issue about accessory pertaining to issue 1128.
SRT to investigate - IN PROGRESS
6. ACTION: SRT to rewrite the exit criteria.
IN PROGRESS
7. ACTION: chairs to respond to issue raiser for closed issues
STANDING ITEM
8. ACTION: Steve to ask Anders and Monica to address issue pertaining to 1092
Anders to take Charlton's text to meeting and to return with proposal
IN PROGRESS, Charlton submitted proposed change text to list
9. ACTION: Steve to learn about this issue from Nick for the Primer (issue 1079)
IN PROGRESS
10. ACTION: Yves will sort out a list of normative references [1]
DONE
11. ACTION: Yves to define what is meant by correctness - see above [2]
IN PROGRESS
12. ACTION: Yves to define the MIME type [3]
DONE
Fletcher: Put in the document by Yves or point
us to one.
Lafon: Name MIME type in document via agreement with IETF and W3C.
Appendix text is written.
13. ACTION: Towards the end of the face-to-face a question was raised regarding the need to provide
clarity on Channel passing. Kohei has sent an e-mail and now folk need to respond to that.
Put on agenda - DONE (see latest agenda too 12th April)
14. ACTION: All in the group to respond to public messages for March 05 numbers 28, 29, 30 and 33.
SRT to re-validate this action
Issues raised by editors:
March 05 number 28:
http://lists.w3.org/Archives/Public/public-ws-chor/2005Mar/0028.html
March 05 number 29:
http://lists.w3.org/Archives/Public/public-ws-chor/2005Mar/0029.html
March 05 number 30:
http://lists.w3.org/Archives/Public/public-ws-chor/2005Mar/0030.html
March 05 number 33:
http://lists.w3.org/Archives/Public/public-ws-chor/2005Mar/0033.html
IN PROGRESS
15. ACTION: Greg to remove comment 2 from 1002 and place it as a comment to 1102
Put that comment doesn't apply (comment in 1002 that belongs in 1102).
DONE
16. ACTION: SRT to close issue 1002 and take action to add 1002-addressing
17. ACTION: Nick to clarify in an email to the group that Kohei understands particular aspects on a
channel which enforce linearity per Kohei's concept - and that we'd be delighted to see
him at the next conf call to discuss further
DONE
Email sent to Kohei. SRT will ask Kohei re: this item 6 April 2005.
Try to get Kohei H. on a conference call.
18. ACTION: Charlton, Gary and Nick to discuss 1008 off line to resolve
(leaving 1008 on the agenda)
IN PROGRESS
6. Editor issues:
-----------------
Issues raised by editors:
March 05 number 28:
http://lists.w3.org/Archives/Public/public-ws-chor/2005Mar/0028.html
March 05 number 29:
http://lists.w3.org/Archives/Public/public-ws-chor/2005Mar/0029.html
March 05 number 30:
http://lists.w3.org/Archives/Public/public-ws-chor/2005Mar/0030.html
March 05 number 33:
http://lists.w3.org/Archives/Public/public-ws-chor/2005Mar/0033.html
7. Issues requiring clarification
---------------------------------
1003 http://www.w3.org/Bugs/Public/show_bug.cgi?id=1003
Summary: RELINGUISHING CONTROL OF PASSED OUTPUT CHANNELS
URL: http://lists.w3.org/Archives/Public/public-ws-chor-comments/2005Jan/0007.html
ADDITIONAL URL: http://lists.w3.org/Archives/Public/public-ws-chor/2005Mar/0005.html
REMAINS OPEN
1008 http://www.w3.org/Bugs/Public/show_bug.cgi?id=1008
Summary: FAULT HANDLING
URL: http://lists.w3.org/Archives/Public/public-ws-chor-comments/2005Jan/0012.html
GB: http://lists.w3.org/Archives/Public/public-ws-chor/2005Feb/0035.html
REMAIN OPEN
1128 http://www.w3.org/Bugs/Public/show_bug.cgi?id=1128
Summary: Accessing and modifying members of lists and arrays
URL: http://www.w3.org/TR/2004/WD-ws-cdl-10-20041217/
GB: http://lists.w3.org/Archives/Public/public-ws-chor/2005Mar/0013.html
Fletcher: Neither resolve what is in the document.
Kavantzas: Are we adding another activity?
Chapman: Have to do this or modifying existing semantics.
SRT: Must also deal with concurrency issues.
Chapman: Do we want to go down this road?
Fletcher: XQuery may give us these capabilities. It is worth considering if a proposal can be developed.
Otherwise, we can't deal sensibly with arbitrary aspects of the choreography.
SRT: Dependency - Multiple concurrent instances is dependent on this issue.
Kavantzas: Are these really related?
Chapman: With parallel threads, you need list accessors.
Martin: See #1166.
Kavantzas: Agreed. Don't confuse issues. Modifying a list and array, and modifying XML documents are two
different tasks of varying level of effort.
http://lists.w3.org/Archives/Public/public-ws-chor/2005Mar/0005.html
Introduce index and how to modify an array or list. I am uncomfortable for the latter item.
Problem may not be that of WS-CDL.
Fletcher: XQuery is a non-XML language (there is one XQuery-X). This requires another processor however.
Chapman: Need a concrete proposal first.
SRT: Will have to establish priorities on what proposals Enigmatic will complete.
NEW ACTION: Greg List 1166 as dependent on 1128.
STATUS: REMAIN OPEN
1107 http://www.w3.org/Bugs/Public/show_bug.cgi?id=1107
Summary: Mapping of roles and binding of variables (needs clarification)
URL: http://lists.w3.org/Archives/Public/public-ws-chor-comments/2005Feb/0001.html
(On agenda at request of Greg R)
Fletcher: A variable only an existence and value at a single role.
Need to text updates if this assumption is true.
Performs maps to roleType not role.
SRT: Bug filed by G. Brown.
Fletcher: Can't a role have more than one channel?
SRT: Yes.
Fletcher: Role A can talk to Role B and C then.
Variables talk about roles (must assure semantics are correct).
Kavantzas: Variable can live in different roles but the value is currently
on each role (i.e. the variable has the same name).
Role type maps to an interface.
Chapman: Why are we discussing this if we don't have concept of role?
Kavantzas: Role doesn't exist in the specification.
Chapman: Shouldn't we change to role type?
SRT: I am more concerned about this comment from G. Brown:
<< also think we need to have text and example to explain why binding roles is
relevant. I guess it is to make the performed choreography more re-usable - but
the only situation I can see this happening is if two separate participant
types, with their own role types, use a common interface - and then the
performed choreography references a third role type (possibly participant
independent) that also uses that same interface.>>
Kavantzas: You are saying variables are related.
Chapman: Change role to role type in specification and query G. Brown to see if the question is resolved.
Kavantzas: when you want to reuse a choreography (and the variable), you have different interfaces
in different namespaces even though the name is the same. You use this alias.
NEW ACTION: Editors Role should be role type in this example.
NEW ACTION: Editors The corresponding text should refer to role type.
NEW ACTION: SRT Confirm with G. Brown his issue is resolved.
8. Review
----------
Chapman: There are no more outstanding proposals.
Get checkpoint draft at this time.
Kavantzas: Working draft by 12 April 2005.
What other issues are outstanding should be provided.
Chapman: Query Bugzilla.
Kavantzas: When do we stop taking proposals?
Chapman: Aim for mid-May 2005 - 15 May 2005. Any proposal has to have precise
editing instructions.
9. AOB
-------
NONE
SUMMARY OF OUTSTANDING ACTIONS
------------------------------
1. ACTION: Martin to do UML diagram from scratch for CDL
IN PROGRESS
2. ACTION: SRT Check 1027 for issues pertaining to identity
IN PROGRESS
3. ACTION: Add text in primer or spec to clarify participant relationship/role pertaining to issue 1027
IN PROGRESS
4. ACTION: Chairs to talk with the XPath 2.0 WG to determine the direction of three-valued
logic and existential qualifiers
IN PROGRESS
5. ACTION: SRT to create a new issue about accessory pertaining to issue 1128.
SRT to investigate - IN PROGRESS
6. ACTION: SRT to rewrite the exit criteria.
IN PROGRESS
7. ACTION: chairs to respond to issue raiser for closed issues
STANDING ITEM
8. ACTION: Steve to ask Anders and Monica to address issue pertaining to 1092
Anders to take Charlton's text to meeting and to return with proposal
IN PROGRESS, Charlton submitted proposed change text to list
9. ACTION: Steve to learn about this issue from Nick for the Primer (issue 1079)
IN PROGRESS
10. ACTION: Yves to define what is meant by correctness - see above [2]
IN PROGRESS
11. ACTION: All in the group to respond to public messages for March 05 numbers 28, 29, 30 and 33.
SRT to re-validate this action
Issues raised by editors:
March 05 number 28:
http://lists.w3.org/Archives/Public/public-ws-chor/2005Mar/0028.html
March 05 number 29:
http://lists.w3.org/Archives/Public/public-ws-chor/2005Mar/0029.html
March 05 number 30:
http://lists.w3.org/Archives/Public/public-ws-chor/2005Mar/0030.html
March 05 number 33:
http://lists.w3.org/Archives/Public/public-ws-chor/2005Mar/0033.html
IN PROGRESS
12. ACTION: SRT to close issue 1002 and take action to add 1002-addressing
13. ACTION: Charlton, Gary and Nick to discuss 1008 off line to resolve
(leaving 1008 on the agenda)
IN PROGRESS
14. NEW ACTION: Greg List 1166 as dependent on 1128.
15. NEW ACTION: Editors Role should be role type in this example.
16. NEW ACTION: Editors The corresponding text should refer to role type.
17. NEW ACTION: SRT Confirm with G. Brown his issue is resolved.