W3C home > Mailing lists > Public > public-ws-policy@w3.org > July 2006

NEW ISSUE: Policy Compatibility Check must account for level of N esting of Policy Alternatives

From: Prasad Yendluri <prasad.yendluri@webmethods.com>
Date: Wed, 26 Jul 2006 19:10:22 -0400
Message-ID: <A3E375FA108EF94496269A5A96AFCAC10645B6E0@mailwest-e0b>
To: public-ws-policy@w3.org
Title: Policy Compatibility Check must account for level of Nesting of
Policy Alternatives


Description: Section 4.4 of the WS-Policy 1.5 - Framework specification


*       "Two policies
?content-type=text/html;%20charset=utf-8#policy#policy>  are compatible if
an alternative in one is compatible with an alternative in the other. If two
policies are compatible, their intersection is the set of the intersections
between all pairs of compatible alternatives, choosing one alternative from
each policy. If two policies are not compatible, their intersection has no
policy alternatives."


However, per section 4.3.2 (Policy Assertion Nesting), a policy Assertion
may contain a nested Policy. 


The intent of the above text is to check compatibility of alternatives at
the top level of the subject policies only. There is scope however for
interpretation, that if an alternative (at any nesting level) in one matches
the alternative (at any nesting level) in the other, the two policies can be
considered compatible.


In addition section 2.3 terminology defines a policy to be "collection of
policy alternatives
ve>  "only. 

No further constraints on the origin of alternatives in the collection.


Similarly section 3.3 (Policy) defines a policy to be: "a policy
?content-type=text/html;%20charset=utf-8#policy#policy>  is a potentially
empty collection of policy alternatives
ve> "



There is scope for interpretation that needs to be eliminated. 


Target: WS-Policy 1.5 - Framework


Proposal - 


1. Tighten up the definition of policy to be specific about the (nesting
level / origin of) "collection" of alternatives it groups. 

     I am Opening a separate new issue for it. If that is properly resolved,
this issue is automatically resolved.

2.  Rephrase the policy compatibility statement to say "Two policies
?content-type=text/html;%20charset=utf-8#policy#policy>  are compatible if a
top level alternative in one is compatible with a top level alternative in
the other."



Prasad Yendluri
Received on Wednesday, 26 July 2006 23:11:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:38:26 UTC