Minutes WS Choreography WG conference call 19 July 2005
IRC: http://www.w3.org/2005/07/19-ws-chor-irc
Role:
-------
Monica Martin, Martin Chapman, Nick Kavantzas, Gary Brown, Charlton
Barreto, Yves Lafon, Greg Ritzinger
Scribe: Charlton Barreto
Agenda:
------------
http://lists.w3.org/Archives/Member/member-ws-chor/2005Jul/att-0007/agenda_20050719.txt
martin: goal to address all LC issues
no comments on the agenda. Approved.
minutes of last week:
-------------------------------
http://lists.w3.org/Archives/Member/member-ws-chor/2005Jul/att-0006/MeetingMinutes20050712-0.txt
no comments on the minutes
minutes from 2005-Jul-12 adopted
Action Items:
-------------------
1. ACTION: Martin to do UML diagram from scratch for CDL
in progress
2. ACTION: chairs to respond to issue raiser for closed issues
STANDING ITEM
Some emails sent to external issue raisers. in progress
3. ACTION: Steve to suggest a W3C Web Services Activity coordination group primer.
http://lists.w3.org/Archives/Member/w3c-ws-cg/2005Jul/0008.html
DONE
4. ACTION: SRT to craft exit criteria based on decisions at F2F to send to editors to fold in to document.
On agenda below.
DONE
5. ACTION: Editors to reword section on Relationships to be a section on Interoperability (same content)
DONE
6. ACTION - LOG ISSUE FOR ITEM 16 [Editors to reword section on Relationships to be a section
on Interoperability (same content)]
charlton to do when gets pen
In progress
7. ACTION: EDITORS TO IMPLEMENT 1092 RESOLUTION AND CORRECT 6/27/2005 SPECIFICATION DRAFT.
(SEE SUPPORTING INFO ENCLOSED IN MINUTES)
DONE
8. ACTION: MONICA/BUSINESS ANALYSTS NEEDS - WHAT ARE THEY? - MONICA TO ELABORATE
In progress
9. ACTION: SRT/ADD ENTERPRISE DOMAIN EXAMPLE FOR PRIMER.
In progress
10. NEW ACTION: mark 1496 as resolved later and mark as editorial [1]
DONE
11. NEW ACTION: charlton to propose wording on finalise and async choreos [2]
In progress.
Open Issues
------------------
1166: http://www.w3.org/Bugs/Public/show_bug.cgi?id=1166
Charlton to have 1166 text proposed to group and ready for discussion by next
conference call
martin: should we see the whole set of editorial issues of finalize addressed
after 1166 text is provided?
no strong opinions against this
1176: http://www.w3.org/Bugs/Public/show_bug.cgi?id=1176
martin: relabelled it as LC comment, raised by Gary, not sure if still an
issue or not
Gary: Not a major issue, I'd just as soon close it
martin: ok, close, no action (no objections)
NEW ACTION: Close 1176 as wontfix
1001: http://www.w3.org/Bugs/Public/show_bug.cgi?id=1001
martin: next issue: 1001 - what is the status of this one?
and
1003: http://www.w3.org/Bugs/Public/show_bug.cgi?id=1003
gary: as far as I'm concerned both of these have been closed - resolved at the
London F2F (2005)
charlton: as far as i've seen they've both been done by tony
19:24:45 [scribe]
martin: we'll update bugzilla and cross-check to close these ones out
NEW ACTION: Close out 1001 and 1003 and cross check with editors
957: http://www.w3.org/Bugs/Public/show_bug.cgi?id=957
doc is now in xhtml so close fixed
NEW ACTION: close out issue 957
Exit Criteria:
-----------------
martin: exit criteria - srt had an item to address exit criteria wording -
email sent out by srt on this:
http://lists.w3.org/Archives/Public/public-ws-chor/2005Jul/0015.html
change exhibits to exhibit
change b from Cover more than one role
to
"b.. Involve more than one role"
nick: so does this mean two or three?
martin: yes
agreed above "involve..."
19:32:14 [scribe]
martin: two or three
Gary: Change "demonstration" to "interoperability" in "Where the demonstration
of "key features" based on alignment protocol,
coordination protocol and addressing are implementation decisions."
from: Where the demonstration of "key features" based on alignment protocol,
coordination protocol and addressing are implementation decisions.
to: where the interoperability of features such as alignment protocol,
coordination protocol and adressing are implementation details
afetr discussion agreed the following change:
"Interoperability concerns such as alignment protocol, coordination protocol
and adressing are implementation details."
martin: with the three changes, listed above, we have the exit criteria,
editors can incorporate
NEW ACTION: Editors to incorporate updated exit criteria into the specification
Editorial Issues
----------------------
Issue 1496: http://www.w3.org/Bugs/Public/show_bug.cgi?id=1496
greg,you resolved this, correct?
yes
ok, let's mark it as resolved fixed
martin: mark it resolved fixed
already done in bugzilla
martin: in bugzilla it is reflecting that it is still resolved later
NEW ACTION: martin to update issue 1496 in bugzilla to mark resolved fixed and close out
Issue 967: http://www.w3.org/Bugs/Public/show_bug.cgi?id=967
yves: will do some minor edits for this during the week
Issue 966: http://www.w3.org/Bugs/Public/show_bug.cgi?id=966
yves: has been done
yves: you s/receive email now
NEW ACTION: martin to update issue 966 as resolved fixed in bugzilla
Closed Issues
------------------------
http://lists.w3.org/Archives/Member/member-ws-chor/2005Jul/0004.html
martin: sent email out last week - agreed issues raised by group members that
we should have already resolved - take a couple of days for final review,
after which i will change to close confirmed
martin, please note that issue 1496 was commented w.r.t. the resolution, but
the status just wasn't changed to resolved fixed
no objection to leaving this list open for couple of days to review
monica: editorial comment on 1086 per my email
http://lists.w3.org/Archives/Member/member-ws-chor/2005Jul/0008.html
Note, the TypeRef complex type definitions contain the same tag name. Each has
different local
elements, and describes different attributes and child elements.
rolereftype first introduced in Example 1
CB: i'm happy with the changes
m2: rolereftype used in choice in 2.5.1.3
suggest somewhere before 2.5.1.3 although I am uncertain about including with
Example 1
Martin: ok - reopen 1086, add editorial changes, and mark it editorial
NEW ACTION: reopen 1086, add editorial changes, and mark it editorial
gary: issue 1063
gary: want to clarify which situation the specified termination conditions for
a choreography are correct
nick: finalizer only called when chor completes successfully - one that
completes abnormally will not reach a finalizer
gary: I just want to clarify that this was the correct view - fine with
leaving the language as is. 1063 therefore remains closed.
AOB
-------
martin: i think we should go to a CR vote in two weeks time
martin: let's talk next week, clear up all issues, then in 2 weeks time, go to
CR vote
Summary of outstanding Actions
----------------------------------------------
1. ACTION: Martin to do UML diagram from scratch for CDL
2. ACTION: chairs to respond to issue raiser for closed issues
STANDING ITEM
6. ACTION - LOG ISSUE FOR ITEM 16 [Editors to reword section on Relationships to be a section
on Interoperability (same content)]
7. ACTION: EDITORS TO IMPLEMENT 1092 RESOLUTION AND CORRECT 6/27/2005 SPECIFICATION DRAFT.
(SEE SUPPORTING INFO ENCLOSED IN MINUTES)
8. ACTION: MONICA/BUSINESS ANALYSTS NEEDS - WHAT ARE THEY? - MONICA TO ELABORATE
9. ACTION: SRT/ADD ENTERPRISE DOMAIN EXAMPLE FOR PRIMER.
11. ACTION: charlton to propose wording on finalise and async choreos [2]
NEW Actions:
ACTION: Close 1176 as wontfix
ACTION: Close out 1001 and 1003 and cross check with editors
ACTION: close out issue 957
ACTION: Editors to incorporate updated exit criteria into the specification
ACTION: martin to update issue 1496 in bugzilla to mark resolved fixed and close out
ACTION: martin to update issue 966 as resolved fixed in bugzilla
ACTION: reopen 1086, add editorial changes, and mark it editorial