RE: [ws-tx] Groups - WS-TX Bi-Weekly Concall modified

["Ashok Malhotra" <ashok.malhotra@oracle.com>]

regrets for this call.

All the best, Ashok
 

> -----Original Message-----
> From: ian_robinson@uk.ibm.com [mailto:ian_robinson@uk.ibm.com] 
> Sent: Wednesday, May 17, 2006 9:14 AM
> To: ws-tx@lists.oasis-open.org
> Subject: [ws-tx] Groups - WS-TX Bi-Weekly Concall modified
> 
> Updated list of Action Items
> 
>  -- Dr Ian Robinson
> 
> 
> WS-TX Bi-Weekly Concall has been modified by Dr Ian Robinson
> 
> Date:  Thursday, 18 May 2006
> Time:  11:30am - 01:00pm ET
> 
> Event Description:
> US (toll free) 866-505-4412
> UK (toll free) 0800 279 9193
> Int'l (toll) +44-20-7019-0808
> Passcode: 268450
> 
> Chat room: http://webconf.soaphub.org/conf/room/wstx
> 
> Agenda:
> 1. Roll Call - chair
> 
> 2. Confirm Paul Knight as minute taker - chair
> 
> 3. Approve minutes of May 4 telecon - chair
> 
> 4. Call for AOB - chair
>    
> 5. Action Review - Paul K
> Max: Draft text for security composability for WS-AT. 
> Bob Freund: submit issue against banning Anonymous replyTo in 
> CreateCoordinationContext.
> Tom: submit issue on removing the designation of 
> notifications as faults.
> Ian: cover how the test plans will react to the resolution to 
> issue 30.
> Peter: consider submitting issue on pointing to fault 
> handling rules in WS-AT.
> Peter: restate proposed text addressing Issue 35.
> Editors of specs and interop docs: get drafts ready a week 
> before the F2F.
> 
> 
> 6.  Potential new issues to accept - Ram Brief statement of 
> each proposed new issue. There is no need to consider the 
> merit of any proposed resolution at this stage. In general 
> the TC will accept issues that are not reopening resolved 
> issues and that are in-scope. Accepted issues move from 
> "review" state to "active" state.
> 
> 7. Agenda and logistics for Dublin F2F - Eric.
> 
> 8. Issue resolution
> 
>       i035 - ws-tx: term "coordinator" overloaded
> i045 - WS-AT: Meaning of "wsp:Optional
> i039 - WS-AT: Coordinator should not distinguish protocol of 
> orphaned participants
> i043 - WS-AT: Invalid state inappropriate response to 
> orphaned volatile participants
> i052 - WS-AT: Replay message generates protocol errors
> i053 - WS-AT: Eliminate Replay message
> i055 - WS-AT: User Commit and User Rollback should not return 
> Aborted in None state
> i056 - WS-AT: User Commit and User Rollback row of CV state 
> table contradicts resolution of 010
> 
> 
> 9.  AOB
> 
> 10. Straggler Roll Call 
> 
> 11. Close
> 
> Minutes:
> 
> 
> This event is one in a list of recurring events.
> Other event dates in this series:
> 
> Thursday, 01 December 2005, 11:30am to 01:00pm ET Thursday, 
> 15 December 2005, 11:30am to 01:00pm ET Thursday, 12 January 
> 2006, 11:30am to 01:00pm ET Thursday, 26 January 2006, 
> 11:30am to 01:00pm ET Thursday, 09 February 2006, 11:30am to 
> 01:00pm ET Thursday, 23 February 2006, 11:30am to 01:00pm ET 
> Thursday, 09 March 2006, 11:30am to 01:00pm ET Thursday, 23 
> March 2006, 11:30am to 01:00pm ET Thursday, 06 April 2006, 
> 11:30am to 01:00pm ET Thursday, 20 April 2006, 11:30am to 
> 01:00pm ET Thursday, 04 May 2006, 11:30am to 01:00pm ET 
> Thursday, 01 June 2006, 11:30am to 01:00pm ET Thursday, 15 
> June 2006, 11:30am to 01:00pm ET Thursday, 29 June 2006, 
> 11:30am to 01:00pm ET Thursday, 13 July 2006, 11:30am to 
> 01:00pm ET Thursday, 27 July 2006, 11:30am to 01:00pm ET 
> Thursday, 10 August 2006, 11:30am to 01:00pm ET Thursday, 24 
> August 2006, 11:30am to 01:00pm ET Thursday, 07 September 
> 2006, 11:30am to 01:00pm ET Thursday, 21 September 2006, 
> 11:30am to 01:00pm ET Thursday, 05 October 2006, 11:30am to 
> 01:00pm ET Thursday, 19 October 2006, 11:30am to 01:00pm ET 
> Thursday, 02 November 2006, 11:30am to 01:00pm ET Thursday, 
> 16 November 2006, 11:30am to 01:00pm ET Thursday, 30 November 
> 2006, 11:30am to 01:00pm ET
> 
> View event details:
> http://www.oasis-open.org/apps/org/workgroup/ws-tx/event.php?e
> vent_id=8990
> 
> PLEASE NOTE:  If the above link does not work for you, your 
> email application may be breaking the link into two pieces.  
> You may be able to copy and paste the entire link address 
> into the address field of your web browser.
> 
> 
>