Hi, Peter,
(resend with correction in email addr)
Yes, we passed my formal (original) proposal - the explicit scope one.
The other proposal (implicit scope) has not become a formal proposal.
Thanks!
Regards,
Alex Yiu
Furniss, Peter wrote:
Perhaps Alex or someone could email the
effective amended resolution to the list and I'll copy it in.
Peter
The next call of the WS BPEL TC
will be on Wed. Aug 17 at 8 am Pacific. Dial in info is: USA &
Canada Toll Free Number: +1 866 500 6738, Pass code: 600345, All Others
(toll): +1 203 480 8000, Pass code: 600345. We will also have access
to LiveMeeting - see the calendar entry for more info on accessing it.
Here is a brief summary of
decisions from the Aug 10 call:
- wiki support is available.
Bernd and Alex plan to start work on a description of changes from
V1.1 to V2.0.
- issue 204: closed with adoption
of Alex's proposal of July 21 with friendly amendment to remove
statement: "(Note: <catch> also introduces
variable to hold fault related data without any explicit declaration.
However it is used in "backward" work, while <onEvent>,
<onAlarm> and <forEach> can be used in "forward" work.
Hence, this kind of clarification is not needed for <catch>.) "
- rewording of 82.2 issue
description accepted as described in email from Diane and Monica on
Aug. 8.
- issue 217: motion to open tabled
until issue description rewritten.
- we will try to close on
alternatives for location of next f2f Aug 17 and no later than Aug 24.
Proposed agenda for next meeting:
- Nomination/volunteers to take minutes for this call
- Roll call/determine quorum
- Review/accept minutes from previous meetings - Aug 10
- Review agenda
- Liaison subgroup report
- Use case subgroup report
- Requirements and Issues Coordination subgroup report
- Specification Editing subgroup report
- Implementation subgroup report
Issue discussion. Note we will follow the process agreed to at the
f2f: Discussions of any issue on calls be limited to no more than 30
minutes at the end of which the person who made the motion can choose
to table to next meeting or force a vote (without requiring 2/3
majority to stop discussion). Those who want to continue to discuss
need to go off line to work the issue. At next meeting progress should
be reported – or issue will go to vote with original proposal. If
issue goes to a vote process starts again as above. If results of
offline discussions result in amended proposal to vote, the new
proposal should be provided to the TC in advance of voting meeting.
– 157
– 88: pending input from
Chris and Alex on questions/clarifications and Paco's response
- 82.3: if Rania able to
contact Satish
Motions to open new issues
- 217 if description
rewritten
Long running issues
-> issue 9: deferred pending
inclusion of 84 in spec
-> issue 125: pending 51 (51
depends on 157)
-> 11: defer pending resolution
to 51, 157, maybe 125. Yaron to provide info on infoset.
-> 99: defer pending 82.3
-> 6.2
-> 169 requires Frank, Satish
Agenda for next meeting
New business
Regards,
John Evdemon and Diane Jordan
WS-BPEL TC Co-chairs
|