OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-rx message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


Matthew

At the last call we discussed having issue 8 first on this week's call. 
However, I am very happy with this proposed ordering if there are no 
objections. In general we seem to be more productive on the calls if we 
start on simpler issues and work our way up to the thornier ones.  also 
agree that while we have been assuming that issue 8 depends on 21, I 
think we agreed on the last call that it doesn't. I hope we can make 
more progress by addressing 8 before 21.

Paul

Matthew Lovett wrote:
>
> Hi Paul,
>
> I'd quite like to try and clean up some of the issues that affect the 
> core spec early in this call. Issues i078, i083, i084 seem to have 
> clear proposals. Would it be possible to move them to the top of the 
> issue discussions?
>
> Following those, issue i075 has a concrete proposal on list (thanks 
> Dug, Umit), so perhaps it's a good candidate for the first of the 
> policy debates? The description of i008 says that it depends on the 
> outcome of i021, but I'm not sure that is true, as the proposal seems 
> OK as it is. Given that, I think we should keep those two in the 
> current order.
>
> Finally, i058 doesn't seem to have any proposed resolution. I think it 
> makes more sense to complete the state table (hopefully with the 
> outcome of the core issues we are discussing early on the call) and 
> then come up with a concrete proposal on this list.
>
> I think that gives us:
>
> > i078 Lost TerminateSequence
> http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i078
>
> > i083                 Tom Rutt                 Fault Messages for 
> Terminated Sequence
> http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i083
>
> > i084                 Matthew Lovett                 RMS state table 
> and SequenceClosedFault
> http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i084
>
> > i075 Case of multiple RM Policies and DAs within an RMD scope
> http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i075
>
> > i008 Policy assertions granularity
> http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i008
>
> > i021 An RM Policy applies two-way
> http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i021
>
> > i058 State Transition Table
> http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i058
>
> I appreciate that this note comes out at short notice, so it the 
> chairs/TC don't have time to adopt these suggestions than that's fine.
>
> Thanks,
>
> Matt

-- 

Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

http://bloglines.com/blog/paulfremantle
paul@wso2.com

"Oxygenating the Web Service Platform", www.wso2.com



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]