- From: Doug Davis <dug@us.ibm.com>
- Date: Tue, 2 Mar 2010 13:44:41 -0500
- To: public-ws-resource-access@w3.org
- Message-ID: <OF88FBA93D.76B2E4AA-ON852576DA.00660265-852576DA.0066FAB9@us.ibm.com>
There have been some discussion through email about the scope of nested assertions under Feature Policy Assertions. To help clarify this, I'd like to suggest changing MEX's section 9 wording. Change: When Feature Policy Assertions contain nested Policy Assertions (as show above in line 17), those assertions have Endpoint Policy Subject and apply to all message exchanges related to the feature. To: When Feature Policy Assertions contain nested Policy Assertions (as show above in line 17), those assertions are attached to the policy scope comprising of all the operations defined by the feature on this Endpoint, unless otherwise defined by the Feature Policy Assertion. Bob, I'd like to add two new agenda items before the MOAP topic for today's call: 1 - use and definition of extensions - what can an extension really do? 2 - use and definition of policy parameters - are they really ignorable? I think we need to make sure we're all on the same page on these high-level concepts before we go much further with MOAP. thanks -Doug ______________________________________________________ STSM | Standards Architect | IBM Software Group (919) 254-6905 | IBM 444-6905 | dug@us.ibm.com The more I'm around some people, the more I like my dog.
Received on Tuesday, 2 March 2010 18:45:33 UTC