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] Proposed list of issues for discussion on the 12/1 conf-call


I'm disappointed by that decision given the amount of work that went
into the discussion leading up to the proposal I have made. There have
been relatively few comments to the proposal. Considering the amount of
time it has been available for review and amount of previous discussion
it certainly seems like we should be ready to discuss this on today's
call.

Given commitments I have next week at this point I agree we should save
this issue for the F2F meeting. I ask that it be placed early in the
agenda.

-----Original Message-----
From: Patil, Sanjay [mailto:sanjay.patil@sap.com] 
Sent: Wednesday, November 30, 2005 1:19 PM
To: Marc Goodner; wsrx
Subject: RE: [ws-rx] Proposed list of issues for discussion on the 12/1
conf-call


Hi Marc,

I had deliberately left out any DA related issue for tomorrow's call.
Perhaps the upcoming F2F is a good time for scheduling all DA related
issues. Are you ok with that?

Thanks,
Sanjay 

> -----Original Message-----
> From: Marc Goodner [mailto:mgoodner@microsoft.com] 
> Sent: Monday, Nov 28, 2005 14:25 PM
> To: Patil, Sanjay; wsrx
> Subject: RE: [ws-rx] Proposed list of issues for discussion 
> on the 12/1 conf-call
> 
> What about i050? I submitted a proposal for that issue last week.
> Regards, Marc g
> 
> http://lists.oasis-open.org/archives/ws-rx/200511/msg00203.html
> Looking at this it appears Kavi ate the content though it did 
> show up in
> the mail from the list. I'll repost today.
> 
> -----Original Message-----
> From: Patil, Sanjay [mailto:sanjay.patil@sap.com] 
> Sent: Monday, November 28, 2005 2:10 PM
> To: wsrx
> Subject: [ws-rx] Proposed list of issues for discussion on the 12/1
> conf-call
> 
> 
> i066  Remove LastMessage
> http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssue
> s.xml#i066
> 
> i064  Create Sequence Refused Fault is too restrictive
> http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssue
> s.xml#i064
> 
> i070  Receive is defined twice in wsrm-1.1-spec-cd-01
> http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssue
> s.xml#i070
> 
> i057  Classification of References (normative vs. non-normative) is
> needed 
> http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssue
> s.xml#i057
> 
> i060  Definition for "Reliable Message"
> http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssue
> s.xml#i060
> 
> i061  Anonymous AcksTo
> http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssue
> s.xml#i061
> 
> i058  State Transition Table 
> http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssue
> s.xml#i058
> 
> 
> 


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