Fw: agenda for June 29

[Diane Jordan <drj@us.ibm.com>]

The next call of the WS BPEL TC will
be on Wed. June 29 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 June 22 call: 
- 190 amendment from last week withdrawn.
 friendly amendment from Alex's email of June 20 accepted:  
if "exitOnStandardFault" attribute of a particular
<process> or <scope> is set to "yes", a <catch>
fault handler construct which targets a WS-BPEL standard fault MUST not
be used. This condition MUST be detected by static analysis and the process
definition of this kind MUST be rejected. 
Original proposal with this amendment
passed 
- 92.4 proposal passed with friendly
amendment:  It is illegal to have 2 or more extension elements under
the extensions element that have the same namespace attribute value; this
requirement must be statically enforced.  
- 96.1 - passed with no objections,
revisitable flag to be set 
- 141 - proposal passed 
- 196 - proposal changed to:  Editors
should fix any elements that are not properly extensible.  passed.
- 160.1 - proposal passed.  
new issues:
209 - opened
214 - opened and closed - submitters
proposal in the issue description adopted
213 - opened and closed - submitters
proposal in the issue adopted
210 - opened and closed - submitters
proposal in the issue with amendment from 5/31 email adopted 
216 - opened
   
Proposed agenda for next meeting:  
- Nomination/volunteers to take minutes for this call   
- Roll call/determine quorum 
- Review/accept minutes from  previous meetings - May 25, June 1-3,
June 8 
- 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
–        92.6

-        139.1
–        111
 
-        169

-        209
-        should
212 be opened 
–        Other
motions to open new issues  
 
Long running issues 
-> 88 pending new proposal
-> 177 pending resolution of two
new issues (212 and 214)
-> 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 

Agenda for next meeting
New business 

Regards, 
John Evdemon and Diane Jordan 
WS-BPEL TC Co-chairs