Minutes WS Choreography WG conference call 12 April 2005
See also IRC log: http://www.w3.org/2005/04/12-ws-chor-irc
Roll Call:
-------------
Steve Ross-Talbot (Co-Chair - Enigmatec), Abbie Barbir (Nortel)
Gary Brown (Enigmatec), Greg Ritzinger (Novell), Anthony Fletcher (Choreology Ltd)
Martin Chapman (Co-Chair - Oracle), Nickolas Kavantzas (Oracle),
Monica Martin (Sun), Charlton Barreto (webMethods), Yves Lafon (W3C staff)
Admin
---------
Scribe: Gary is apointed
Agenda:
http://lists.w3.org/Archives/Public/public-ws-chor/2005Apr/att-0003/Agenda-04122005-0.txt
Adding item 6.a - Issues and status review
Minutes:
5th April 2005: http://lists.w3.org/Archives/Member/member-ws-chor/2005Apr/att-0003/MeetingMinutes20050405-0.txt
Minutes approved
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
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
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
IN PROGRESS
13. ACTION: Charlton, Gary and Nick to discuss 1008 off line to resolve
(leaving 1008 on the agenda)
IN PROGRESS
14. ACTION: Greg List 1166 as dependent on 1128.
DONE
15. ACTION: Editors Role should be role type in this example.
Tony believes this is done - but marked as in progress for now
IN PROGRESS
16. ACTION: Editors The corresponding text should refer to role type.
IN PROGRESS
17. ACTION: SRT Confirm with G. Brown his issue is resolved.
issue was not resolved but action item DONE.
Agenda item 6a - issues report review
-----------------------------------------------------
Stock take of all open Last Call Comment issues
http://lists.w3.org/Archives/Public/public-ws-chor/2005Apr/att-0005/IssuesReport.txt
** RESOLVED AND OR CLOSED **
999 RESOLVED LATER
1002 RESOLVED WONTT FIX
1007 RESOLVED LATER
1023 RESOLVED LATER
1027 RESOLVED WON'T FIX
1074 DUPLICATE
1099 RESOLVED LATER
1108 RESOLVED LATER
RESOLVED LATER equates to EDITORIAL and will be CLOSED once relevant Editor's draft is adopted.
** ISSUES OUTSTANDING **
967 OPEN - SHOULD BE RESOLVED LATER AND ASSIGNED TO Yves
968 OPEN - SHOULD BE RESOLVED LATER AND ASSIGNED TO Yves
971 OPEN - Chairs suggest to group to either do it (need volunteers) or
CLOSE WON'T FIX
973 OPEN - Chairs believe this should be RESOLVED LATER
996 OPEN - Chairs believe this should be RESOLVED WON'T FIX
998 OPEN - Chairs believe this should be RESOLVED WON'T FIX
1000 OPEN - WAITING PROPOSAL
1001 OPEN - WAITING PROPOSAL
1003 OPEN - ON AGENDA TONIGHT
1004 OPEN - WAITING PROPOSAL
1005 OPEN - Chairs suggest CLOSE FIXED (based on structural clarity)
1008 OPEN - ON AGENDA TONIGHT
1018 OPEN - Chairs believe this should be RESOLVED FIXED
1026 OPEN - WAITING PROPOSAL
1039 OPEN - Chairs ask group WHO is doing this?
1055 OPEN - Chairs ask group to move to RESOLVE LATER
1075 OPEN - WAITING PROPOSAL
1079 OPEN - Chairs ask group to CLOSE WON'T FIX
1100 OPEN - Chairs ask group to CLOSE FIXED (based on structural clarity)
1110 OPEN - Need clarification from group as to what should happen when
variables are not available
1126 OPEN - WAITING PROPOSAL
1128 OPEN - WAITING PROPOSAL
1129 OPEN - Chairs ask group to CLOSE WON'T FIX
971 - chairs don't believe important enough related to the amount of work
required
Unless volunteer, this will be closed tonight
<nick> +1
Group agrees
NEW ACTION: Close 971 as Resolved, won't fix
996 - choice of response message in WSDL
Tony: WSDL2 will be able to define multiple normal response messages
... describe how could be done, in primer
Martin: does not believe that multiple normal responses can be returned
Nick: WSDL spec seems to suggest it can be done
SRT: can it be modelled with multiple interactions in a choice
Gary: yes - although if two responses have same type, then may only be able to
distinguish by name
SRT: no mechanism to define choice in interact
Nick: implicit choice in interact
Martin: in the interact would need to express different response types that
could be received
SRT concerned about how we model multiple exchanges based on multiple responses
SRT: may need to get an official response from WSDL group to resolve this
Martin: might need to look at the * for output responses in the WSDL spec
SRT: proposes to resolve won't fix
Suggestion is to remove the bullet that restricts the number of normal responses
- which would then need to be handled when dealing with endpoints
<nick> When two or more respond exchanges are specified, one respond exchange
MAY be of normal informationType and all others MUST be of Exception Type. There
is an implicit choice between two or more respond exchanges
<charlton> +1 to removing the restriction
+1
proposal to remove restriction, issue 996, is adopted
<nick> When two or more respond exchanges are specified There is an implicit
choice between two or more respond exchanges
PROPOSAL FOR 996 is to replace "When two or more respond exchanges are
specified, one respond exchange MAY be of normal informationType and all others
MUST be of Exception Type. There is an implicit choice between two or more
respond exchanges" WITH "When two or more respond exchanges are specified There
is an implicit choice between two or more respond exchanges"
<SRT> +1
Group agrees to proposal
NEW ACTION: Record 996 as resolved fixed with text in minutes (12 apr)
Group agrees to closing 998 as resolved won't fix
NEW ACTION: Record 998 as resolved won't fix
1001 - needs to be reviewed and group needs to provide feedback
1000 - previous proposal on a past conference call, to make roles optional and
standard text
NEW ACTION Chairs to search previous minutes for proposal on optional roles
1003 - on agenda
1004 and 1005 should be closed fixed based on the structural clarity
[ was this agreed by the group?]
1008 - on agenda
SRT: believes 1018 has been fixed
Tony: updated in spec already
NEW ACTION: Record 1018 as resolved fixed
1026: SRT: related to 1001
1039 - section on comformance - who is doing this?
Tony: will have a go at drafting something
NEW ACTION: Tony to draft conformance section
1055 Nick: nice for language to have mechanism for creating new ids
Tony: usecase- workunit repeating can create new id on each iteration
SRT: How would it be implemented in distributed environment
Gary: need to have example in spec or primer to show its usage
Nick: its a utility function, can miss it or not, could have many other
functions
... origin was WSCI or BPML
SRT: As primer editor, would prefer to remove the function
as cannot think of suitable example - then can be re-added if example found
NEW ACTION: Record1055 as RESOLVED LATER so is editorial
1075 - awaiting proposal
1079 - proposal to move to CLOSE WON'T FIX - adopted
NEW ACTION: Record 1079 as CLOSE WON'T FIX
1100 - proposal to move to CLOSE WON'T FIX based on structural clarity - adopted
NEW ACTION: Record 1100 as CLOSE WON'T FIX
1110 - Nick: was discussed at Boston f2f
no decision was made, awaiting proposal
SRT: could say not handled, and if worried about it, have a guard condition
leave as awaiting proposal - possibly could be described in primer
1126 - awaiting a proposal
1129 - need to look back in minutes for decision
NEW ACTION: Chairs to look back in minutes for decision on issue 1129
1128 - was discussed last week - awaiting proposal
AOB
------
None.
Meeting closed.
Summary of New Action Items
-------------------------------------------
NEW ACTION: Close 971 as Resolved, won't fix
NEW ACTION: Record 996 as resolved fixed with text in minutes (12 apr)
NEW ACTION: Record 998 as resolved won't fix
NEW ACTION Chairs to search previous minutes for proposal on optional roles
NEW ACTION: Record 1018 as resolved fixed
NEW ACTION: Tony to draft conformance section
NEW ACTION: Record1055 as RESOLVED LATER so is editorial
NEW ACTION: Record 1079 as CLOSE WON'T FIX
NEW ACTION: Record 1100 as CLOSE WON'T FIX
NEW ACTION: Chairs to look back in minutes for decision on issue 1129