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

[Bug 3602] The absence of an assertion should not mean that the behavior is "explicitly prohibited"

From: <bugzilla@wiggum.w3.org>
Date: Thu, 14 Sep 2006 00:16:45 +0000
To: public-ws-policy-qa@w3.org
Message-Id: <E1GNeuL-0001Hw-Iy@wiggum.w3.org>


------- Comment #2 from ashok.malhotra@oracle.com  2006-09-14 00:16 -------
I was aked to supply text to clarify the cryptic statement in the text.
Here is suggested text to be added to section 3.2.

3.2 Policy Alternative
The vocabulary of a policy alternative is the set of all policy assertion types
within the alternative. [Definition: A policy vocabulary is the set of all
policy assertion types used in a policy.] An assertion whose type is part of
the policy's vocabulary but is not included in an alternative is explicitly
prohibited by the alternative.

<new text>
For example, if there is a policy with an assertion marked with
“optional=’true’” this puts the assertion in the vocabulary of the policy. 
When this policy is normalized the assertion appears in one alternative and not
in the other.  If the alternative that does not include the assertion is chosen
then it is explicitly prohibited to apply the assertion as the assertion is
part of the policy vocabulary.

Consider the following policy:

        <am:assertion1 …/>
        <am:assertion2 optional=’true’/> 

This normalizes to:


        <am:assertion1 …/>
        <am:assertion2  …/> 


        <am:assertion1 …/>

If ALTERNATIVE 2 is selected then applying Assertion2 is explicitly prohibited.
</new text>
Received on Thursday, 14 September 2006 00:16:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:02:09 UTC