2006/ws/policy ws-policy-framework.xml,1.145,1.146 ws-policy-framework.html,1.119,1.120

Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv13608

Modified Files:
	ws-policy-framework.xml ws-policy-framework.html 
Log Message:
Incorporated the resoultion for Issue 4561 Editors AI 319

Index: ws-policy-framework.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.xml,v
retrieving revision 1.145
retrieving revision 1.146
diff -u -d -r1.145 -r1.146
--- ws-policy-framework.xml	12 Jun 2007 18:37:42 -0000	1.145
+++ ws-policy-framework.xml	13 Jun 2007 19:25:43 -0000	1.146
@@ -1734,14 +1734,22 @@
                     intersection: strict and lax. How the mode is selected or indicated for the policy 
                     intersection is outside the scope of this specification. 
                 </p>
-                <p>Because the set of behaviors indicated by a <termref def="policy_alternative"
-                        >policy alternative</termref> depends on the domain-specific semantics of
-                    the collected assertions, determining whether two policy alternatives are
-                    compatible generally involves domain-specific processing. If a domain-specific
-                    intersection processing algorithm is required this will be known from the QNames
-                    of the specific <termref def="policy_assertion_type">assertion types</termref>
-                    involved in the policy alternatives. As a first approximation, an algorithm is
-                    defined herein that approximates compatibility in a domain-independent manner: </p>
+                <p>
+                    As a first approximation, an intersection algorithm is defined below 
+                    that approximates compatibility of <termref def="policy_assertion">policy assertions</termref> 
+                    in a domain-independent manner. Mechanisms for determining 
+                    assertion parameter compatibility are not part of this domain-independent 
+                    policy intersection. Determining whether two policy assertions of the same 
+                    type are compatible may involve domain-specific processing for purposes of 
+                    determining assertion parameter compatibility. Domain-independent policy 
+                    intersection may be extended to include domain-specific processing. 
+                    If a domain-specific intersection processing algorithm is required this 
+                    will be known from the QName of the specific <termref def="policy_assertion_type">assertion type</termref> 
+                    involved in the <termref def="policy_alternative">policy alternative</termref>. 
+                    However, regardless of whether an assertion's 
+                    QName indicates domain-specific processing, an implementation of the 
+                    domain-independent intersection need not apply the domain-specific processing.
+                </p>
                 <ulist>
                     <item>
                         <p>Two <termref def="policy_assertion">policy assertions</termref> are
@@ -1756,9 +1764,13 @@
                             the nested policy expression of the other.</p>
                     </item>
                 </ulist>
-                <p><termref def="policy_assertion_parameter">Assertion parameters</termref> are not
-                    part of the compatibility determination defined herein but may be part of other,
-                    domain-specific compatibility processing. </p>
+                <p>
+                <termref def="policy_assertion_parameter">Assertion parameters</termref> 
+                are not part of the domain-independent compatibility 
+                determination defined herein but this domain-independent policy intersection 
+                may be extended to include domain-specific processing for purposes of 
+                determining assertion parameter compatibility.   
+                </p>
                 <ulist>
                     <item>
                         <p>If the mode is strict, two <termref def="policy_alternative">policy
@@ -3351,6 +3363,15 @@
                             <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/313">313</loc>.
                         </td>
                     </tr>
+                    <tr>
+                        <td>20070613</td>
+                        <td>PY</td>
+                        <td>Implemented the resolution
+                            for issue <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4561">4561</loc>. 
+                            Editors' action 
+                            <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/319">319</loc>.
+                        </td>
+                    </tr>
                 </tbody>
             </table>
         </inform-div1>

Index: ws-policy-framework.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.html,v
retrieving revision 1.119
retrieving revision 1.120
diff -u -d -r1.119 -r1.120
--- ws-policy-framework.html	12 Jun 2007 18:37:41 -0000	1.119
+++ ws-policy-framework.html	13 Jun 2007 19:25:43 -0000	1.120
@@ -285,9 +285,7 @@
          <a href="#ignorable_policy_assertion">ignorable policy assertion</a>
       </dt><dd><p>An
                             <b>ignorable policy assertion</b> is an assertion that may be
-                            ignored for purposes of determining the compatibility of alternatives 
-                            in policy intersection in a lax mode
-                           (as defined in <a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-framework.html?content-type=text/html;charset=utf-8#Policy_Intersection">4.5 Policy
+                        ignored for policy intersection (as defined in <a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-framework.html?content-type=text/html;charset=utf-8#Policy_Intersection">4.5 Policy
                             Intersection</a>).</p></dd><dt class="label">
          <a href="#nested_policy_expression">nested policy expression</a>
       </dt><dd><p>A <b>nested policy expression</b>
@@ -1102,19 +1100,32 @@
                     it does not imply formal set intersection semantics). There are two modes for 
                     intersection: strict and lax. How the mode is selected or indicated for the policy 
                     intersection is outside the scope of this specification. 
-                </p><p>Because the set of behaviors indicated by a <a title="policy alternative" href="#policy_alternative">policy alternative</a> depends on the domain-specific semantics of
-                    the collected assertions, determining whether two policy alternatives are
-                    compatible generally involves domain-specific processing. If a domain-specific
-                    intersection processing algorithm is required this will be known from the QNames
-                    of the specific <a title="policy assertion type" href="#policy_assertion_type">assertion types</a>
-                    involved in the policy alternatives. As a first approximation, an algorithm is
-                    defined herein that approximates compatibility in a domain-independent manner: </p><ul><li><p>Two <a title="policy assertion" href="#policy_assertion">policy assertions</a> are
+                </p><p>
+                    As a first approximation, an intersection algorithm is defined below 
+                    that approximates compatibility of <a title="policy assertion" href="#policy_assertion">policy assertions</a> 
+                    in a domain-independent manner. Mechanisms for determining 
+                    assertion parameter compatibility are not part of this domain-independent 
+                    policy intersection. Determining whether two policy assertions of the same 
+                    type are compatible may involve domain-specific processing for purposes of 
+                    determining assertion parameter compatibility. Domain-independent policy 
+                    intersection may be extended to include domain-specific processing. 
+                    If a domain-specific intersection processing algorithm is required this 
+                    will be known from the QName of the specific <a title="policy assertion type" href="#policy_assertion_type">assertion type</a> 
+                    involved in the <a title="policy alternative" href="#policy_alternative">policy alternative</a>. 
+                    However, regardless of whether an assertion's 
+                    QName indicates domain-specific processing, an implementation of the 
+                    domain-independent intersection need not apply the domain-specific processing.
+                </p><ul><li><p>Two <a title="policy assertion" href="#policy_assertion">policy assertions</a> are
                             compatible if they have the same <a title="policy assertion type" href="#policy_assertion_type">type</a> and</p></li><li><p>If either assertion contains a nested <a title="policy expression" href="#policy_expression">policy expression</a>, the two assertions are compatible if
                             they both have a nested policy expression and the alternative in the
                             nested policy expression of one is compatible with the alternative in
-                            the nested policy expression of the other.</p></li></ul><p><a title="policy assertion parameter" href="#policy_assertion_parameter">Assertion parameters</a> are not
-                    part of the compatibility determination defined herein but may be part of other,
-                    domain-specific compatibility processing. </p><ul><li><p>If the mode is strict, two <a title="policy alternative" href="#policy_alternative">policy
+                            the nested policy expression of the other.</p></li></ul><p>
+                <a title="policy assertion parameter" href="#policy_assertion_parameter">Assertion parameters</a> 
+                are not part of the domain-independent compatibility 
+                determination defined herein but this domain-independent policy intersection 
+                may be extended to include domain-specific processing for purposes of 
+                determining assertion parameter compatibility.   
+                </p><ul><li><p>If the mode is strict, two <a title="policy alternative" href="#policy_alternative">policy
                                 alternatives</a> A and B are compatible: </p><ul><li><p>if each assertion in A is compatible with an assertion in B,
                                         and</p></li><li><p>if each assertion in B is compatible with an assertion in
                                     A.</p></li></ul><p>If the mode is lax, two <a title="policy alternative" href="#policy_alternative">policy
@@ -1611,4 +1622,8 @@
                             for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4592">4592</a>. 
                             Editors' action 
                             <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/313">313</a>.
+                        </td></tr><tr><td rowspan="1" colspan="1">20070613</td><td rowspan="1" colspan="1">PY</td><td rowspan="1" colspan="1">Implemented the resolution
+                            for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4561">4561</a>. 
+                            Editors' action 
+                            <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/319">319</a>.
                         </td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file

Received on Wednesday, 13 June 2007 19:25:48 UTC