2006/ws/policy ws-policy-primer.html,1.34,1.35

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

Modified Files:
	ws-policy-primer.html 
Log Message:
Completed Editors AI 127, implemented resolution of issue 4197 in the Primer

Index: ws-policy-primer.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer.html,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -d -r1.34 -r1.35
--- ws-policy-primer.html	22 Jan 2007 18:21:14 -0000	1.34
+++ ws-policy-primer.html	22 Jan 2007 20:57:24 -0000	1.35
@@ -823,12 +823,16 @@
           insignificant. Therefore, the order of combining these policy expressions is
           insignificant.</p></div><div class="div2">
 <h3><a name="extensibility-and-versioning"></a>3.8 Extensibility and Versioning</h3><p>Web Services Policy language is an extensible language by design. The
-            <code>Policy</code>, <code>ExactlyOne</code>, <code>All</code>
-          and <code>PolicyReference</code> elements are extensible. The <code>Policy</code>,
-            <code>ExactlyOne</code> and <code>All</code> elements allow child element and attribute
-          extensibility. Extensions must not use the policy language XML namespace name. 
-          A consuming processor processes known attributes and elements, ignores unknown attributes and treats unknown
-          elements as policy assertions.</p><p>The <code>PolicyReference</code> element allows element and attribute extensibility.</p><p>Web Services Policy language enables simple versioning practices that allow requesters to
+          <code>Policy</code>, <code>ExactlyOne</code>, <code>All</code>
+          and <code>wsp:PolicyReference</code> elements are extensible. The <code>Policy</code>
+          element allows child element and attribute extensibility, while the
+          <code>ExactlyOne</code> and <code>All</code> elements allow child element
+          extensibility. The <code>PolicyReference</code> child element allows element 
+          and attribute extensibility. Extensions must not use the policy language XML namespace name.
+          A consuming processor processes known attributes and elements, ignores unknown attributes 
+          and treats unknown children of the <code>Policy</code>, <code>ExactlyOne</code>, <code>All</code> 
+          elements as policy assertions. The child elements of <code>wsp:PolicyReference</code> are ignored. 
+          </p><p>The <code>PolicyReference</code> element allows element and attribute extensibility.</p><p>Web Services Policy language enables simple versioning practices that allow requesters to
           continue the use of any older policy alternatives in a backward compatible manner. This
           allows service providers, like Contoso, to deploy new behaviors using additional policy
           assertions without breaking compatibility with clients that rely on any older policy
@@ -872,7 +876,7 @@
           policy assertions. As discussed before, these requesters may continue to interact using
           old policy alternatives. New policy assertions will emerge to represent new behaviors and
           slowly become part of everyday interoperable interaction between requesters and providers.
-          Today, most tools use a practical tolerant strategy to process new or unrecognized policy
+          For example, most tools use a practical tolerant strategy to process new or unrecognized policy
           assertions. These tools consume such unrecognized assertions and designate these for user
           intervention. As you would recognize, there is nothing new in this practice. This is
           similar to how a proxy generator that generates code from WSDL creates code for all the
@@ -923,7 +927,9 @@
         </p><p>Over time, the Policy WG or third parties can version or extend the Policy Language with new or modified constructs.  These constructs may be compatible or incompatible with previous versions.  Some of the possible new constructs that have been mentioned previously are: new operators, operator cardinality, policy identification, compact syntax, Policy Inclusion, security, referencing, attachment points, alternative
           priority, effective dating, negotiation. </p><p>WS-Policy provides extensibility points on 6 elements with a combination of attribute and/or element extensibility.  
           The possible extensibility points with their current extensibility - including some outstanding issues related to extensibility - are:</p><ol><li><p>Policy: element from ##other namespace and any attribute</p></li><li><p>PolicyReference: any attribute and a proposal to add any element ExactlyOne, All: element from ##other namespace, no attribute extensibility</p></li><li><p>PolicyAttachment:  element from ##other namespace and any attribute</p></li><li><p>AppliesTo: any element and any attribute</p></li></ol><div class="div3">
-<h4><a name="versioning-policy-framework"></a>3.10.1 Policy Framework</h4><p>WS-Policy Framework 1.5 specifies that any element that is not known inside a Policy, ExactlyOne or All will be treated as an assertion.  The default value for wsp:Optional="false", which means after normalization it will be inside an ExactlyOne/All operator.  </p><p>Let us show an example with a hypothetical new operator that is a Choice with a minOccurs and a maxOccurs attributes, ala XSD:Choice, in a new namespace.  We use the wsp16 prefix to indicate a hypothetical Policy Language 1.6 that is intended to be compatible with Policy Language 1.5:</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><i><span>Example 3-13. </span>Policy containing 1.5 and 1.6 Policies.</i></p><div class="exampleInner"><pre>&lt;wsp:Policy&gt;
+<h4><a name="versioning-policy-framework"></a>3.10.1 Policy Framework</h4><p>WS-Policy Framework 1.5 specifies that any child element that is not known inside a Policy, 
+          ExactlyOne or All will be treated as an assertion. The default value for wsp:Optional="false". 
+          After normalization, such an element will be inside an ExactlyOne/All operator.  </p><p>Let us show an example with a hypothetical new operator that is a Choice with a minOccurs and a maxOccurs attributes, ala XSD:Choice, in a new namespace.  We use the wsp16 prefix to indicate a hypothetical Policy Language 1.6 that is intended to be compatible with Policy Language 1.5:</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><i><span>Example 3-13. </span>Policy containing 1.5 and 1.6 Policies.</i></p><div class="exampleInner"><pre>&lt;wsp:Policy&gt;
   &lt;wsp:ExactlyOne&gt;
     &lt;wsp16:Choice wsp16:minOccurs="1" wsp16:maxOccurs="2"&gt;
       ...
@@ -1014,7 +1020,8 @@
 	 &lt;/wsp:ExactlyOne&gt;
 	&lt;/wsp:Policy&gt;
   &lt;wsdl11:operation name="GetLastTradePrice" &gt; ....
-  ...</pre></div></div><p>The PolicyReference element is attribute extensible.  One example of an addition is a list of backup URIs for the PolicyReference:</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><i><span>Example 3-22. </span>WSDL containing 1.5 and 2.0 (compatible with 2.0) Policy References.</i></p><div class="exampleInner"><pre>&lt;wsdl11:binding name="StockQuoteSoapBinding" type="fab:Quote" &gt;
+  ...</pre></div></div><p>The PolicyReference element is element or attribute extensible.  
+          One example of an addition is a list of backup URIs for the PolicyReference:</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><i><span>Example 3-22. </span>WSDL containing 1.5 and 2.0 (compatible with 2.0) Policy References.</i></p><div class="exampleInner"><pre>&lt;wsdl11:binding name="StockQuoteSoapBinding" type="fab:Quote" &gt;
        &lt;wsoap12:binding style="document"
           transport="http://schemas.xmlsoap.org/soap/http" /&gt;
 	&lt;wsp:Policy&gt;
@@ -1266,4 +1273,6 @@
               Editors' action <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/143">143</a>.
             </td></tr><tr><td rowspan="1" colspan="1">20070122</td><td rowspan="1" colspan="1">PY</td><td rowspan="1" colspan="1">Completed action item:
               <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/118">118</a>
-              Resolution for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4141">4141</a></td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
+              Resolution for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4141">4141</a></td></tr><tr><td rowspan="1" colspan="1">20070122</td><td rowspan="1" colspan="1">PY</td><td rowspan="1" colspan="1">Completed action item:
+              <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/127">127</a>
+              Resolution for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4197">4197</a></td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file

Received on Monday, 22 January 2007 20:57:31 UTC