Agenda Start up admin: roll call, approve agenda, appoint minute takers, approve last meeting minutes Review and approve latest draft of spec Issue discussion: Issues with proposals to vote 6, 9, 52, 81, 103, 15, 87, 89, 110, 134, 137, 123, 129, 115, 2, 91, 97, 99, 107, 126 (note, this is ordered so that the issues that have been open for a while with the votes deferred will be done later). The last 5 issues will be done on Wed. issues with draft proposals: 135, 139 (I think these are the only ones left that haven't been "promoted" to proposals to vote - let me know if I missed any). Review all remaining issues by category (alphabetical order). Schedule Thurs morning we will discuss the schedule and proposed new checkpoints A suggestion has been made that we should require future proposals to vote to include all require spec language changes. We may also want to discuss the suggestion that at some point we will want to start closing issues that have aged to a certain point without any activity and when we might project putting something like that in effect. Note: As we've done in the past, we will break every 2 hours to take a checkpoint on the agenda, update roll on the phone, switch minute taker and hold votes as required.

Sept 21 Summary Latest working copy of spec approved. Monica, Danny and Vinky will send email with some minor comments Issue discussion: Issues with proposals to vote 6 – extensive discussion. Satish will continue to work the proposal 9 – Yaron will write a new proposal that reflects discussion 52 – closed with no change to the spec 129 – closed with the proposal from Chris 134 – proposal adopted Danny will open a new issue having to do with defining fault a for language problems. If received during the f2f, the vote on opening it will happen immediately. 137 – closed as an editing change. Spec editing team to work on final wording. 89 – closed: a static analysis requirement will be defined to insure that a process will be rejected if query or executiion language expressions are not supported (Yaron to send email with exact wording) Note: As we've done in the past, we will break every 2 hours to take a checkpoint on the agenda, update roll on the phone, switch minute taker and hold votes as required.

Agenda Sept 22 Start up admin: roll call, approve agenda, appoint minute takers Issue discussion: Issues with proposals to vote: 103, 12:30 pm: 115 Summarize 103, Summarize 6 91, 97, 99, 107, 126 (Abstract topic) Remaining issues with proposals: 81, 15, 87, 110, 123 2 issues with draft proposals: 135, 139 (I think these are the only ones left that haven't been "promoted" to proposals to vote - let me know if I missed any). Review all remaining issues by category (alphabetical order). Vote on whether to open new issue: 161, 163 May want to defer 161 until Tony is present Update from WS Choreography

Summary Sept 22 Issue discussion: 103: lengthy discussion and identification of suggested modifications. Yaron and Alex to summarize discussion and bring revision in on Sept. 23 or later meeting. 115: issue closed with no change to the spec. Subgroup will be formed for interested parties to work on a separate, non-normative document covering the information intended for Appendix c. If this group comes up with a document they agree to, they will bring it to the TC for endorsement. 91, 97, 99, 107, 126 (Abstract topic): Rania reviewed the paper that captures the agreements from the abstract subgroup and the outstanding issues. Much discussion. Work will continue to transform points made in the document into actionable issues.

Agenda Sept 23 Start up admin: roll call, approve agenda, appoint minute takers Schedule Next f2f: preferred location east coast US, preferred dates Dec. 14, 15, 16 7 votes vs 6 for Nov 30, Dec 1, Dec 2 – 6 votes, 17 for either (30 of 46 voters) Getting to committee draft Suggestion to require future proposals to vote to include all required spec language changes. We may also want to discuss the suggestion that at some point we will want to start closing issues that have aged to a certain point without any activity and when we might project putting something like that in effect. Other ideas Vote on whether to open new issue: 161, 163 May want to defer 161 until Tony is present Resume issue discussion Issues with proposals to vote: 103 update 81, 15, 87, 110, 123 2 Issues with draft proposals: 135, 139 (I think these are the only ones left that haven't been "promoted" to proposals to vote - let me know if I missed any). Review all remaining issues by category (alphabeticorder).