I agree with other's that we should focus on the use cases for these
scenarios. I also agree that these issues are related and note that in
particular i006 is dependent upon i009, and in the examples being
provided i008 as well.
I will make an effort to update the schema for the issue list to capture
dependent issues. This will likely take the form of two optional fields,
i.e.
<issue
i006...>...<dependent>i009</dependent><dependent>i008</dependent>...
<issue i009...>...<blocks>i006</blocks>....
We should be able to then draw up a dependency tree as we raise
additional issues.
Regards,
Marc g
-----Original Message-----
From: Patil, Sanjay [mailto:]
Sent: Monday, July 18, 2005 12:18 PM
To: wsrx
Subject: [ws-rx] Proposed list of issues for discussion on 7/21
conf-call
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
