RE: [ws-rx] Groups - WS-RX TC Weekly Conference Call modified

["Patil, Sanjay" <sanjay.patil@sap.com>]

I am not sure if every body in the main TC is part of the interop
activities and whether it is a good idea to mix the agendas of the main
TC with the Implementation Subcommittee [1].

May I suggest that the interop related activities be first carried in
the Implementation Subcommittee and the main TC be contacted when there
is something significant to report which may affect the chartered
deliverables of the main TC, etc. Of course, there is nothing wrong in
keeping the main TC aware of the interop related activities by copying
on email  correspondences and soliciting feedback/input on important
documents such as the interop scenarios, etc. 

Thanks,
Sanjay

[1]
http://www.oasis-open.org/committees/sc_home.php?wg_abbrev=ws-rx-impleme
nt




> -----Original Message-----
> From: Paul Cotton [mailto:Paul.Cotton@microsoft.com] 
> Sent: Wednesday, Jan 18, 2006 14:07 PM
> To: Patil, Sanjay; ws-rx@lists.oasis-open.org
> Subject: RE: [ws-rx] Groups - WS-RX TC Weekly Conference Call modified
> 
> Shouldn't the interop document that Marc posted last Friday be on the
> agenda?
> http://lists.oasis-open.org/archives/ws-rx/200601/msg00084.html
> 
> 
> Paul Cotton, Microsoft Canada
> 17 Eleanor Drive, Nepean, Ontario K2E 6A3
> Tel: (613) 225-5445 Fax: (425) 936-7329
> mailto:Paul.Cotton@microsoft.com
> 
>  
> 
> 
> 
> > -----Original Message-----
> > From: sanjay.patil@sap.com [mailto:sanjay.patil@sap.com]
> > Sent: January 18, 2006 3:28 PM
> > To: ws-rx@lists.oasis-open.org
> > Subject: [ws-rx] Groups - WS-RX TC Weekly Conference Call modified
> > 
> > 
> > WS-RX TC Weekly Conference Call has been modified by Mr Sanjay Patil
> > 
> > Date:  Thursday, 19 January 2006
> > Time:  01:00pm - 02:30pm PT
> > 
> > Event Description:
> > Dial in:
> > Microsoft agreed to sponsor. Watch for an email from Microsoft.
> > 
> > IRC/Q Mgmt(thanks to DougD): 
> http://webconf.soaphub.org/conf/room/wsrx
> > 
> > Agenda:
> > 1) Roll Call
> > 
> > 2) Review and approval of the agenda
> > 
> > 3) Approval of the Jan 12, 2006 meeting minutes
> >    http://www.oasis-open.org/apps/org/workgroup/ws-
> > rx/download.php/16299/MinutesWSRX-011206.htm
> > 
> > 4) AI Review
> >    http://www.oasis-open.org/apps/org/workgroup/ws-
> > rx/members/action_items.php
> > 
> > 5) Administrative
> >  a> Open ballots
> >  b> Dates/Venue for the next F2F
> > 
> > 6> Namespace Versioning Policy
> > a>	Formal approval
> > b>	Scope (applicability to WD, CD, CS)
> > 
> > 7> RDDL document
> >  a> Formal approval
> >  b> Scope (applicability to WD, CD, CS)
> > 
> > 8) New issues since last conf-call
> >    Watch for Marcs email
> > 
> > 9) Issue Discussion:
> >  a> i082 Level of "response message" unclear, for SequenceResponse
> >    http://docs.oasis-open.org/ws-
> > rx/issues/ReliableMessagingIssues.xml#i082
> > 
> >  b> i086 Alternative approach for MaxMessage
> >    http://docs.oasis-open.org/ws-
> > rx/issues/ReliableMessagingIssues.xml#i086
> > 
> >  c> i087 Acknowledgement Interval in CreateSequenceResponse
> >    http://docs.oasis-open.org/ws-
> > rx/issues/ReliableMessagingIssues.xml#i087
> > 
> >  d> i075 Case of multiple RM Policies and DAs within an RMD scope
> >    http://docs.oasis-open.org/ws-
> > rx/issues/ReliableMessagingIssues.xml#i075
> > 
> >  e> i083 Tom Rutt Fault Messages for Terminated Sequence
> >
> http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssue
s.xml#i083
> > 
> > 10) Any other business
> > 
> > 
> > Minutes:
> > 
> > 
> > This event is one in a list of recurring events.
> > Other event dates in this series:
> > 
> > Thursday, 05 January 2006, 01:00pm to 02:30pm PT
> > Thursday, 12 January 2006, 01:00pm to 02:30pm PT
> > Thursday, 26 January 2006, 01:00pm to 02:30pm PT
> > 
> > View event details:
> >
> http://www.oasis-open.org/apps/org/workgroup/ws-rx/event.php?e
vent_id=87
> 68
> > 
> > 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.
> 
>