+1
Totally agree.
Thanks,
Sanjay
>-----Original Message-----
>From: Christopher B Ferris [mailto:]
>Sent: Monday, Jul 18, 2005 13:17 PM
>To: Patil, Sanjay
>Cc: wsrx
>Subject: Re: [ws-rx] Proposed list of issues for discussion on
>7/21 conf-call
>
>Sanjay,
>
>With regards to these issues, I think that we should first
>focus on the
>requirements and usage scenarios
>rather than discuss any specifics as to how we might address
>them. I think
>I made this point on the last call.
>
>Cheers,
>
>Christopher Ferris
>STSM, Emerging e-business Industry Architecture
>email:
>blog: http://webpages.charter.net/chrisfer/blog.html
>phone: +1 508 377 9295
>
>"Patil, Sanjay" <> wrote on 07/18/2005 03:18:10 PM:
>
>>
>>
>> i006 Source based delivery QoS policy assertion
>>
>>
>http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php
>/13598/Re
>> liableMessagingIssues.xml#i006
>> Please see Tom's posting on 7/14 for use cases and motivations:
>> http://lists.oasis-open.org/archives/ws-rx/200507/msg00108.html
>>
>> i008 Policy assertions granularity
>>
>>
>http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php
>/13598/Re
>> liableMessagingIssues.xml#i008
>>
>> i009 Declaration of QoS policies
>>
>>
>http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php
>/13598/Re
>> liableMessagingIssues.xml#i009
>>
>> On the 7/14 conf-call, Tom kindly agreed to own the issue
>i006. He also
>> posted a set of use cases and motivation summary on 7/14 (before the
>> conf call - see link above). Please check this and other
>relevant email
>> discussion before the next conf-call.
>>
>> The above listed issues seem to be interrelated. It will be great to
>> have someone first present to the TC a wider context that
>highlights the
>> interrelationships, based on which we can set an order for discussing
>> these issues and avoid going in circles. Any volunteers?
>>
>> Thanks,
>> Sanjay
>
>
