- From: Prasad Yendluri via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 22 Jan 2007 20:54:19 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv22976
Modified Files:
ws-policy-primer.xml
Log Message:
Completed Editors AI 127, implemented resolution of issue 4197 in the Primer
Index: ws-policy-primer.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer.xml,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -d -r1.30 -r1.31
--- ws-policy-primer.xml 22 Jan 2007 18:18:43 -0000 1.30
+++ ws-policy-primer.xml 22 Jan 2007 20:54:16 -0000 1.31
@@ -1262,12 +1262,16 @@
<div2 id="extensibility-and-versioning">
<head>Extensibility and Versioning</head>
<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>
+ <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
@@ -1325,7 +1329,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
@@ -1401,7 +1405,9 @@
</olist>
<div3 id="versioning-policy-framework"><head>Policy Framework</head>
- <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>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>
<example><head>Policy containing 1.5 and 1.6 Policies.</head>
<eg><![CDATA[<wsp:Policy>
@@ -1550,7 +1556,8 @@
...]]></eg>
</example>
- <p>The PolicyReference element is attribute extensible. One example of an addition is a list of backup URIs for the PolicyReference:</p>
+ <p>The PolicyReference element is element or attribute extensible.
+ One example of an addition is a list of backup URIs for the PolicyReference:</p>
<example><head>WSDL containing 1.5 and 2.0 (compatible with 2.0) Policy References.</head>
<eg><![CDATA[<wsdl11:binding name="StockQuoteSoapBinding" type="fab:Quote" >
@@ -2051,7 +2058,14 @@
<td>Completed action item:
<loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/118">118</loc>
Resolution for issue <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4141">4141</loc></td>
- </tr>
+ </tr>
+ <tr>
+ <td>20070122</td>
+ <td>PY</td>
+ <td>Completed action item:
+ <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/127">127</loc>
+ Resolution for issue <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4197">4197</loc></td>
+ </tr>
</tbody>
</table>
</inform-div1>
Received on Monday, 22 January 2007 20:54:30 UTC