W3C home > Mailing lists > Public > public-ws-policy-eds@w3.org > May 2007

2006/ws/policy ws-policy-framework.html,1.111,1.112 ws-policy-framework.xml,1.135,1.136

From: David Orchard via cvs-syncmail <cvsmail@w3.org>
Date: Thu, 24 May 2007 18:59:38 +0000
To: public-ws-policy-eds@w3.org
Message-Id: <E1HrIXC-0002Rj-6I@lionel-hutz.w3.org>

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

Modified Files:
	ws-policy-framework.html ws-policy-framework.xml 
Log Message:
Fixed bug 4544

Index: ws-policy-framework.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.xml,v
retrieving revision 1.135
retrieving revision 1.136
diff -u -d -r1.135 -r1.136
--- ws-policy-framework.xml	14 May 2007 02:10:56 -0000	1.135
+++ ws-policy-framework.xml	24 May 2007 18:59:35 -0000	1.136
@@ -433,25 +433,13 @@
                             def="policy_assertion">policy assertions</termref>.</termdef> An
                     alternative with zero assertions indicates no behaviors. An alternative with one
                     or more assertions indicates behaviors implied by those, and only those
-                    assertions. <termdef id="policy_vocabulary" term="policy vocabulary">A
-                            <term>policy vocabulary</term> is the set of all <termref
-                            def="policy_assertion_type">policy assertion types</termref> used in a
-                        policy.</termdef>
-                    <termdef id="policy_alternative_vocabulary" term="policy alternative vocabulary"
-                        >A <term>policy alternative vocabulary</term> is the set of all <termref
-                            def="policy_assertion_type">policy assertion types</termref> within the
-                            <termref def="policy_alternative">policy
-                    alternative</termref>.</termdef> When an assertion whose type is part of the
-                    policy's vocabulary is not included in a policy alternative, the policy
-                    alternative without the assertion type indicates that the assertion will not be
-                    applied in the context of the attached policy subject. See the example in
-                    Section <specref ref="Optional_Policy_Assertions"/></p>
+                    assertions.</p>
 
                 <p>Assertions within an alternative are not ordered, and thus aspects such as the
                     order in which behaviors (indicated by assertions) are applied to a <termref
                         def="policy_subject">subject</termref> are beyond the scope of this
                     specification. However, authors can write assertions that control the order in
-                    which behaviours are applied.</p>
+                    which behaviors are applied.</p>
 
                 <p>A policy alternative <rfc2119>MAY</rfc2119> contain multiple assertions of the
                     same type. Mechanisms for determining the aggregate behavior indicated by the
@@ -522,11 +510,8 @@
                     alternative can be supported at the same time.</p>
 
                 <p>Note that an entity may be able to support a policy even if the entity does not
-                    understand the <termref def="policy_assertion_type">type</termref> of each
-                    assertion in the <termref def="policy_vocabulary">vocabulary of the
-                    policy</termref>; the entity only has to understand the type of each assertion
-                    in the vocabulary of a <termref def="policy_alternative">policy
-                    alternative</termref> the entity supports. This characteristic is crucial to
+                    understand the type of each assertion in the policy; the entity only has to understand the type of each assertion
+                    in a policy alternative that the entity supports. This characteristic is crucial to
                     versioning and incremental deployment of new assertions because this allows a
                     provider's policy to include new assertions in new alternatives while allowing
                     entities to continue to use old alternatives in a backward-compatible
@@ -1787,6 +1772,8 @@
                 <p>See Section <specref ref="rPolicy_Alternative"/> for mechanisms for determining
                     the aggregate behavior indicated by multiple assertions of the same <termref
                         def="policy_assertion_type">policy assertion type</termref>.</p>
+                        <p>An entity applies all the behaviors implied by a policy alternative when that policy alternative is chosen from the intersection result (see <specref ref="Web_services"/>).  If an entity includes a policy assertion type A in its policy, and this policy assertion type A does not occur in an intersected result, then that entity SHOULD not apply the behavior implied by assertion type A.  If a policy assertion type Z is not included in the input policies being intersected then the intersection result is silent about the behavior implied by the assertion type Z.
+</p>
                 <p>As an example of intersection, consider two input policies in normal form:</p>
                 <eg xml:space="preserve">(01) &lt;wsp:Policy
         xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702"
@@ -1842,8 +1829,8 @@
 (13)     &lt;/wsp:All&gt;
 (14)   &lt;/wsp:ExactlyOne&gt;
 (15) &lt;/wsp:Policy&gt;</eg>
-                <p>Because there is only one alternative (A2) in policy P1 with the same vocabulary
-                    &mdash; the assertions have the same type &mdash; as another alternative
+                <p>Because there is only one alternative (A2) in policy P1 with the same assertion
+                    type as another alternative
                     (A3) in policy P2, the intersection is a policy with a single alternative that
                     contains all of the assertions in A2 and in A3.</p>
                 <eg xml:space="preserve">(01) &lt;wsp:Policy
@@ -2375,6 +2362,7 @@
             <ulist>
                 <item>
                     <p>Editorial changes to align with the OASIS WS-SecurityPolicy specification.</p>
+                    <p>Updated meaning of intersection result and removed vocabulary terms, bug 4554</p>
                 </item>
             </ulist>
         </inform-div1>
@@ -3185,6 +3173,15 @@
                             Editors' action <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/259">259</loc>.
                         </td>
                     </tr>
+                   <tr>
+                        <td>20070524</td>
+                        <td>DBO</td>
+                        <td>Implemented the 
+                        <loc href="http://lists.w3.org/Archives/Public/public-ws-policy/2007May/0283.html">resolution</loc> 
+                            for issue <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4554">4554</loc>. 
+                            Editors' action <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/297">297</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.111
retrieving revision 1.112
diff -u -d -r1.111 -r1.112
--- ws-policy-framework.html	14 May 2007 02:10:56 -0000	1.111
+++ ws-policy-framework.html	24 May 2007 18:59:35 -0000	1.112
@@ -250,7 +250,6 @@
                             </td><td rowspan="1" colspan="1">[<cite><a href="#XMLSchemaPart1">XML Schema Structures</a></cite>]</td></tr></tbody></table><br><p>All information items defined by this specification are identified by the XML
                     namespace URI [<cite><a href="#XML-NS">XML Namespaces</a></cite>] <code>http://www.w3.org/ns/ws-policy</code>. A <a href="http://www.w3.org/2007/02/ws-policy.xsd">normative XML Schema</a> [<cite><a href="#XMLSchemaPart1">XML Schema Structures</a></cite>, <cite><a href="#XMLSchemaPart2">XML Schema Datatypes</a></cite>] document can be
                     obtained indirectly by dereferencing the namespace document at the WS-Policy 1.5
-
                     namespace URI.</p><p>It is the intent of the W3C Web Services Policy Working Group that the
                     Web Services Policy 1.5 - Framework and Web Services Policy 1.5 - Attachment XML namespace URI will not
                     change arbitrarily with each subsequent revision of the corresponding XML Schema
@@ -278,7 +277,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 policy intersection (as defined in <a href="http://www.w3.org/TR/ws-policy#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>
@@ -291,10 +290,6 @@
          <a href="#policy_alternative">policy alternative</a>
       </dt><dd><p>A <b>policy
                             alternative</b> is a potentially empty collection of <a title="policy assertion" href="#policy_assertion">policy assertions</a>.</p></dd><dt class="label">
-         <a href="#policy_alternative_vocabulary">policy alternative vocabulary</a>
-      </dt><dd><p>A <b>policy alternative vocabulary</b> is the set of all <a title="policy assertion type" href="#policy_assertion_type">policy assertion types</a> within the
-                            <a title="policy alternative" href="#policy_alternative">policy
-                    alternative</a>.</p></dd><dt class="label">
          <a href="#policy_assertion">policy assertion</a>
       </dt><dd><p>A <b>policy
                         assertion</b> represents a requirement, a capability, or other property
@@ -321,11 +316,7 @@
          <a href="#policy_subject">policy subject</a>
       </dt><dd><p>A <b>policy subject</b> is
                         an entity (e.g., an endpoint, message, resource, operation) with which a
-                            <a title="policy" href="#policy">policy</a> can be associated. </p></dd><dt class="label">
-         <a href="#policy_vocabulary">policy vocabulary</a>
-      </dt><dd><p>A
-                            <b>policy vocabulary</b> is the set of all <a title="policy assertion type" href="#policy_assertion_type">policy assertion types</a> used in a
-                        policy.</p></dd></dl></div></div><div class="div1">
+                            <a title="policy" href="#policy">policy</a> can be associated. </p></dd></dl></div></div><div class="div1">
 <h2><a name="Policy_Model" id="Policy_Model"></a>3. Policy Model</h2><p>This section defines an abstract model for policies and for operations upon policies.</p><p>The descriptions below use XML Infoset terminology for convenience of description.
                 However, this abstract model itself is independent of how it is represented as an
                 XML Infoset. </p><div class="div2">
@@ -373,19 +364,10 @@
                             alternative</b> is a potentially empty collection of <a title="policy assertion" href="#policy_assertion">policy assertions</a>.] An
                     alternative with zero assertions indicates no behaviors. An alternative with one
                     or more assertions indicates behaviors implied by those, and only those
-                    assertions. [<a name="policy_vocabulary" id="policy_vocabulary" title="policy vocabulary">Definition</a>: A
-                            <b>policy vocabulary</b> is the set of all <a title="policy assertion type" href="#policy_assertion_type">policy assertion types</a> used in a
-                        policy.]
-                    [<a name="policy_alternative_vocabulary" id="policy_alternative_vocabulary" title="policy alternative vocabulary">Definition</a>: A <b>policy alternative vocabulary</b> is the set of all <a title="policy assertion type" href="#policy_assertion_type">policy assertion types</a> within the
-                            <a title="policy alternative" href="#policy_alternative">policy
-                    alternative</a>.] When an assertion whose type is part of the
-                    policy's vocabulary is not included in a policy alternative, the policy
-                    alternative without the assertion type indicates that the assertion will not be
-                    applied in the context of the attached policy subject. See the example in
-                    Section <a href="#Optional_Policy_Assertions"><b>4.3.1 Optional Policy Assertions</b></a></p><p>Assertions within an alternative are not ordered, and thus aspects such as the
+                    assertions.</p><p>Assertions within an alternative are not ordered, and thus aspects such as the
                     order in which behaviors (indicated by assertions) are applied to a <a title="policy subject" href="#policy_subject">subject</a> are beyond the scope of this
                     specification. However, authors can write assertions that control the order in
-                    which behaviours are applied.</p><p>A policy alternative <span class="rfc2119">MAY</span> contain multiple assertions of the
+                    which behaviors are applied.</p><p>A policy alternative <span class="rfc2119">MAY</span> contain multiple assertions of the
                     same type. Mechanisms for determining the aggregate behavior indicated by the
                     assertions (and their Post-Schema-Validation Infoset (PSVI) (See XML Schema Part
                     1 [<cite><a href="#XMLSchemaPart1">XML Schema Structures</a></cite>]) content, if any) are specific to the
@@ -434,11 +416,8 @@
                     the policy. Note that although policy alternatives are meant to be mutually
                     exclusive, it cannot be decided in general whether or not more than one
                     alternative can be supported at the same time.</p><p>Note that an entity may be able to support a policy even if the entity does not
-                    understand the <a title="policy assertion type" href="#policy_assertion_type">type</a> of each
-                    assertion in the <a title="policy vocabulary" href="#policy_vocabulary">vocabulary of the
-                    policy</a>; the entity only has to understand the type of each assertion
-                    in the vocabulary of a <a title="policy alternative" href="#policy_alternative">policy
-                    alternative</a> the entity supports. This characteristic is crucial to
+                    understand the type of each assertion in the policy; the entity only has to understand the type of each assertion
+                    in a policy alternative that the entity supports. This characteristic is crucial to
                     versioning and incremental deployment of new assertions because this allows a
                     provider's policy to include new assertions in new alternatives while allowing
                     entities to continue to use old alternatives in a backward-compatible
@@ -1117,7 +1096,8 @@
                             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.</p></li></ul><p>See Section <a href="#rPolicy_Alternative"><b>3.2 Policy Alternative</b></a> for mechanisms for determining
-                    the aggregate behavior indicated by multiple assertions of the same <a title="policy assertion type" href="#policy_assertion_type">policy assertion type</a>.</p><p>As an example of intersection, consider two input policies in normal form:</p><div class="exampleInner"><pre>(01) &lt;wsp:Policy
+                    the aggregate behavior indicated by multiple assertions of the same <a title="policy assertion type" href="#policy_assertion_type">policy assertion type</a>.</p><p>An entity applies all the behaviors implied by a policy alternative when that policy alternative is chosen from the intersection result (see <a href="#Web_services"><b>3.4 Policies of Entities in a Web Services Based System</b></a>).  If an entity includes a policy assertion type A in its policy, and this policy assertion type A does not occur in an intersected result, then that entity SHOULD not apply the behavior implied by assertion type A.  If a policy assertion type Z is not included in the input policies being intersected then the intersection result is silent about the behavior implied by the assertion type Z.
+</p><p>As an example of intersection, consider two input policies in normal form:</p><div class="exampleInner"><pre>(01) &lt;wsp:Policy
 &nbsp; &nbsp; &nbsp; &nbsp; xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702"
 &nbsp; &nbsp; &nbsp; &nbsp; xmlns:wsp="http://www.w3.org/ns/ws-policy" &gt;
 &nbsp; &nbsp; &nbsp; &nbsp;&lt;!-- Policy P1 --&gt;
@@ -1166,8 +1146,8 @@
 (12)&nbsp; &nbsp; &nbsp; &nbsp;&lt;/sp:SignedElements&gt;
 (13)&nbsp; &nbsp; &nbsp;&lt;/wsp:All&gt;
 (14)&nbsp; &nbsp;&lt;/wsp:ExactlyOne&gt;
-(15) &lt;/wsp:Policy&gt;</pre></div><p>Because there is only one alternative (A2) in policy P1 with the same vocabulary
-                    — the assertions have the same type — as another alternative
+(15) &lt;/wsp:Policy&gt;</pre></div><p>Because there is only one alternative (A2) in policy P1 with the same assertion
+                    type as another alternative
                     (A3) in policy P2, the intersection is a policy with a single alternative that
                     contains all of the assertions in A2 and in A3.</p><div class="exampleInner"><pre>(01) &lt;wsp:Policy
 &nbsp; &nbsp; &nbsp; &nbsp; xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702"
@@ -1455,7 +1435,7 @@
     acknowledged.
   </p></div><div class="div1">
 <h2><a name="change-description" id="change-description"></a>D. Changes in this Version of the Document (Non-Normative)</h2><p>A list of major editorial changes since the Working Draft dated 30 March, 2007 is
-                below:</p><ul><li><p>Editorial changes to align with the OASIS WS-SecurityPolicy specification.</p></li></ul></div><div class="div1">
+                below:</p><ul><li><p>Editorial changes to align with the OASIS WS-SecurityPolicy specification.</p><p>Updated meaning of intersection result and removed vocabulary terms, bug 4554</p></li></ul></div><div class="div1">
 <h2><a name="change-log" id="change-log"></a>E. Web Services Policy 1.5 - Framework Change Log (Non-Normative)</h2><a name="ws-policy-framework-changelog-table"></a><table border="1"><tbody><tr><th rowspan="1" colspan="1">Date</th><th rowspan="1" colspan="1">Author</th><th rowspan="1" colspan="1">Description</th></tr><tr><td rowspan="1" colspan="1">20060712</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Updated the list of editors. Completed action items <a href="http://www.w3.org/2006/07/12-ws-policy-minutes.html#action12">12</a>, <a href="http://www.w3.org/2006/07/12-ws-policy-minutes.html#action16">16</a> and <a href="http://www.w3.org/2006/07/12-ws-policy-minutes.html#action20">20</a> from the Austin F2F.</td></tr><tr><td rowspan="1" colspan="1">20060718</td><td rowspan="1" colspan="1">DBO</td><td rowspan="1" colspan="1">Completed action items: RFC2606 for domain names <a href="http://www.w3.org/2006/07/12-ws-policy-minutes.html#action09">09</a> (note: PLH had already done but it ddn't show up in the
                             change log) </td></tr><tr><td rowspan="1" colspan="1">20060726</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Incorporated the <a href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Jul/0107.html">XML namespace URI versioning policy</a> adopted by the WG. </td></tr><tr><td rowspan="1" colspan="1">20060803</td><td rowspan="1" colspan="1">PY</td><td rowspan="1" colspan="1">Completed Issue: <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3551">3551</a>
                             Misc updates throughout. </td></tr><tr><td rowspan="1" colspan="1">20060808</td><td rowspan="1" colspan="1">PY</td><td rowspan="1" colspan="1">Completed action item: <a href="http://www.w3.org/2006/07/13-ws-policy-minutes.html#action20">20</a> to highlight infoset terms uniformly. </td></tr><tr><td rowspan="1" colspan="1">20060808</td><td rowspan="1" colspan="1">DBO</td><td rowspan="1" colspan="1">Completed action items: <a href="http://www.w3.org/2006/07/12-ws-policy-minutes.html#action15">15</a> as early as possible in the doc, use the definition that
@@ -1517,4 +1497,8 @@
                         <a href="http://lists.w3.org/Archives/Public/public-ws-policy/2007May/0005.html">resolution</a> 
                             for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4479">4479</a>. 
                             Editors' action <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/259">259</a>.
-                        </td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
+                        </td></tr><tr><td rowspan="1" colspan="1">20070524</td><td rowspan="1" colspan="1">DBO</td><td rowspan="1" colspan="1">Implemented the 
+                        <a href="http://lists.w3.org/Archives/Public/public-ws-policy/2007May/0283.html">resolution</a> 
+                            for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4554">4554</a>. 
+                            Editors' action <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/297">297</a>.
+                            </td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
Received on Thursday, 24 May 2007 18:59:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:03 GMT