- From: David Orchard via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 23 Oct 2007 20:51:01 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv2593
Modified Files:
ws-policy-primer.html ws-policy-primer.xml
Log Message:
fixed bug 5188
Index: ws-policy-primer.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer.html,v
retrieving revision 1.73
retrieving revision 1.74
diff -u -d -r1.73 -r1.74
--- ws-policy-primer.html 17 Oct 2007 17:04:52 -0000 1.73
+++ ws-policy-primer.html 23 Oct 2007 20:50:59 -0000 1.74
@@ -1275,19 +1275,9 @@
</wsp:ExactlyOne>
</wsp:Policy></pre></div></div><p>Because the wsp16:Choice alternative isn't understood in either normalized form, it will not be chosen as one of the alternatives and will effectively be ignored. Policy intersection may be more difficult with such compatible extensions. For example, the previous will "look"
like it has a wsp16:Choice typed assertion. To determine intersection with a Policy that does not have the wsp16:Choice type assertion, domain specific processing would have to be done. However, there is an alternative that does not have the wsp16:Choice, so intersection would yield the expected result.
- </p><p>Note: it is possible to add new names to the existing namespace, such as: </p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 4-5. </span>Policy containing 1.5 and 1.6 Policies all in the 1.5 namespace</i></p><div class="exampleInner"><pre><wsp:Policy>
- <wsp:ExactlyOne>
- <wsp:Choice wsp:minOccurs="1" wsp:maxOccurs="2">
- ...
- </wsp:Choice>
- <wsp:All>
- ...
- </wsp:All>
- </wsp:ExactlyOne>
-</wsp:Policy></pre></div></div><p>Notice that using a new namespace can result in backwards and forwards compatibility if normalization results in an optional alternative. </p><p>Best practice: insert new elements in an optional alternative or mark with wsp:Optional="true". </p><p>Incompatible versions of the Policy language may be indicated by a new namespace name for at least the new and/or incompatible elements or attributes. Imagine that the Choice operator is required by a future version of Policy, then there will be a new namespace for the Policy element. We use the wsp20 prefix to indicate a hypothetical Policy Language 2.0 that is intended to be incompatible with Policy Language
+ </p><p>Best practice: insert new elements in an optional alternative or mark with wsp:Optional="true". </p><p>Incompatible versions of the Policy language may be indicated by a new namespace name for at least the new and/or incompatible elements or attributes. Imagine that the Choice operator is required by a future version of Policy, then there will be a new namespace for the Policy element. We use the wsp20 prefix to indicate a hypothetical Policy Language 2.0 that is intended to be incompatible with Policy Language
1.5:</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 4-6. </span>Policy containing 2.0 only Policies.</i></p><div class="exampleInner"><pre><wsp20:Policy>
+<p style="text-align: left" class="exampleHead"><i><span>Example 4-5. </span>Policy containing 2.0 only Policies.</i></p><div class="exampleInner"><pre><wsp20:Policy>
<wsp20:ExactlyOne>
<wsp20:Choice wsp:minOccurs="1" wsp:maxOccurs="2">
...
@@ -1296,13 +1286,13 @@
</wsp20:ExactlyOne>
</wsp20:Policy> </pre></div></div><p>The new Policy operator could be embedded inside an existing Policy
element:</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 4-7. </span>Policy containing 2.0 (incompatible with 1.5) Policies embedded in wsp 1.5 Policy.</i></p><div class="exampleInner"><pre><wsp:Policy>
+<p style="text-align: left" class="exampleHead"><i><span>Example 4-6. </span>Policy containing 2.0 (incompatible with 1.5) Policies embedded in wsp 1.5 Policy.</i></p><div class="exampleInner"><pre><wsp:Policy>
<wsp20:Choice wsp:minOccurs="1" wsp:maxOccurs="2">
...
</wsp20:Choice>
...
</wsp20:Policy> </pre></div></div><p>This will be treated as an Assertion for normalization and intersection computation. This will result in only one alternative that requires the wsp20:Choice, the intended behaviour for incompatible changes.</p><p>Best practice: use a new namespace for new incompatible construct and insert inside either: new Policy element OR existing All for future incompatible policy extensions.</p><p>A future version of WS-Policy could support the current operators in the existing namespace, such as:</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 4-8. </span>Policy containing 1.5 operator in 2.0 Policy</i></p><div class="exampleInner"><pre><wsp20:Policy>
+<p style="text-align: left" class="exampleHead"><i><span>Example 4-7. </span>Policy containing 1.5 operator in 2.0 Policy</i></p><div class="exampleInner"><pre><wsp20:Policy>
<wsp:ExactlyOne>
<wsp20:Choice wsp:minOccurs="1" wsp:maxOccurs="2">
...
@@ -1312,7 +1302,7 @@
</wsp20:Policy> </pre></div></div><p>It is difficult to predict whether this functionality would be useful. The future version of WS-Policy doesn't appear to be precluded from doing this.</p></div><div class="div2">
<h3><a name="versioning-policy-attachment" id="versioning-policy-attachment"></a>4.2 Policy Attachment</h3><p>Policy attachment provides WSDL 1.1 and UDDI attachment points. It appears that exchange of Policy will be in the context of WSDL or UDDI.
WRT WSDL, the policy model is an extension of the WSDL definition. As such, it is likely that future versions of Policy will be exchanged as multiple Policy expressions within a WSDL. One alternative is that there would be a separate WSDL for each version of Policy. The problem of how to specify and query for compound documents is very difficult, so it is more likely that each version of Policy will be exchanged within a WSDL. </p><p>We show an example of a new version of policy that allows QName reference to Policies in the PolicyReference:</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 4-9. </span>WSDL containing 1.5 and 2.0 (compatible with 2.0) Policy References.</i></p><div class="exampleInner"><pre><wsdl11:binding name="StockQuoteSoapBinding" type="fab:Quote" >
+<p style="text-align: left" class="exampleHead"><i><span>Example 4-8. </span>WSDL containing 1.5 and 1.6 (compatible with 1.5) Policy References.</i></p><div class="exampleInner"><pre><wsdl11:binding name="StockQuoteSoapBinding" type="fab:Quote" >
<wsoap12:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http" />
<wsp:Policy>
@@ -1324,9 +1314,9 @@
wsdl11:required="true" />
</wsp:All>
<wsp:All>
- <wsp:PolicyReferenceByQName ref="rmp:RMAssertion"
+ <wsp16:PolicyReferenceByQName ref="rmp:RMAssertion"
wsdl11:required="true" />
- <wsp:PolicyReferenceByQName ref="sp:AsymmetricBinding"
+ <wsp16:PolicyReferenceByQName ref="sp:AsymmetricBinding"
wsdl11:required="true" />
</wsp:All>
</wsp:ExactlyOne>
@@ -1334,7 +1324,7 @@
<wsdl11:operation name="GetLastTradePrice" > ....
...</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 4-10. </span>WSDL containing 1.5 and 2.0 (compatible with 2.0) Policy References.</i></p><div class="exampleInner"><pre><wsdl11:binding name="StockQuoteSoapBinding" type="fab:Quote" >
+<p style="text-align: left" class="exampleHead"><i><span>Example 4-9. </span>WSDL containing 1.5 and 1.6 (compatible with 1.5) Policy References.</i></p><div class="exampleInner"><pre><wsdl11:binding name="StockQuoteSoapBinding" type="fab:Quote" >
<wsoap12:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http" />
<wsp:Policy>
@@ -1521,7 +1511,7 @@
on public-ws-policy@w3.org</a> are also gratefully
acknowledged.
</p></div><div class="div1">
-<h2><a name="change-description" id="change-description"></a>E. Changes in this Version of the Document (Non-Normative)</h2><p>A list of editorial changes since the Working Draft dated 10 August, 2007 is below:</p><ul><li><p>Added another example to <a href="#compatible-policies"><b>3.4 Compatible Policies</b></a>.</p></li><li><p>Dropped the editorial note in <a href="#versioning-policy-language"><b>4. Versioning Policy Language</b></a>.</p></li><li><p>Updated references: [<cite><a href="#WS-AddressingMetadata">WS-Addressing Metadata</a></cite>], [<cite><a href="#WS-Policy">Web Services Policy Framework</a></cite>] and [<cite><a href="#WS-PolicyAttachment">Web Services Policy Attachment</a></cite>].</p></li></ul></div><div class="div1">
+<h2><a name="change-description" id="change-description"></a>E. Changes in this Version of the Document (Non-Normative)</h2><p>A list of editorial changes since the Working Draft dated 10 August, 2007 is below:</p><ul><li><p>Added another example to <a href="#compatible-policies"><b>3.4 Compatible Policies</b></a>.</p></li><li><p>Dropped the editorial note in <a href="#versioning-policy-language"><b>4. Versioning Policy Language</b></a>.</p></li><li><p>Updated references: [<cite><a href="#WS-AddressingMetadata">WS-Addressing Metadata</a></cite>], [<cite><a href="#WS-Policy">Web Services Policy Framework</a></cite>] and [<cite><a href="#WS-PolicyAttachment">Web Services Policy Attachment</a></cite>].</p></li><li><p>Removed the illegal wsp:Choice example and changed wsp to wsp16 prefix in <a href="#versioning-policy-language"><b>4. Versioning Policy Language</b></a>.</p></li></ul></div><div class="div1">
<h2><a name="change-log" id="change-log"></a>F. Web Services Policy 1.5 - Primer Change Log (Non-Normative)</h2><a name="ws-policy-primer-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">20060816</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Created first draft per action item <a href="http://www.w3.org/2006/07/12-ws-policy-minutes.html#action02">2</a> from the
Austin F2F. This draft is based on a <a href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Jul/0001.html">contribution</a> from Microsoft.</td></tr><tr><td rowspan="1" colspan="1">20060829</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Implemented the
<a href="http://www.w3.org/2006/08/23-ws-policy-minutes.html#action06">resolution</a>
@@ -1689,4 +1679,7 @@
</td></tr><tr><td rowspan="1" colspan="1">20071017</td><td rowspan="1" colspan="1">FJH</td><td rowspan="1" colspan="1">Implemented the resolution for issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=5204">5204</a>. Editors' action
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/370">370</a>.
+ </td></tr><tr><td rowspan="1" colspan="1">20071023</td><td rowspan="1" colspan="1">DBO</td><td rowspan="1" colspan="1">Implemented the resolution for issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=5188">5188</a>. Editors' action
+ <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/369">369</a>.
</td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
Index: ws-policy-primer.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer.xml,v
retrieving revision 1.79
retrieving revision 1.80
diff -u -d -r1.79 -r1.80
--- ws-policy-primer.xml 17 Oct 2007 17:04:53 -0000 1.79
+++ ws-policy-primer.xml 23 Oct 2007 20:50:59 -0000 1.80
@@ -1767,21 +1767,6 @@
<p>Because the wsp16:Choice alternative isn't understood in either normalized form, it will not be chosen as one of the alternatives and will effectively be ignored. Policy intersection may be more difficult with such compatible extensions. For example, the previous will "look"
like it has a wsp16:Choice typed assertion. To determine intersection with a Policy that does not have the wsp16:Choice type assertion, domain specific processing would have to be done. However, there is an alternative that does not have the wsp16:Choice, so intersection would yield the expected result.
</p>
- <p>Note: it is possible to add new names to the existing namespace, such as: </p>
- <example><head>Policy containing 1.5 and 1.6 Policies all in the 1.5 namespace</head>
- <eg><![CDATA[<wsp:Policy>
- <wsp:ExactlyOne>
- <wsp:Choice wsp:minOccurs="1" wsp:maxOccurs="2">
- ...
- </wsp:Choice>
- <wsp:All>
- ...
- </wsp:All>
- </wsp:ExactlyOne>
-</wsp:Policy>]]></eg>
- </example>
-
- <p>Notice that using a new namespace can result in backwards and forwards compatibility if normalization results in an optional alternative. </p>
<p>Best practice: insert new elements in an optional alternative or mark with wsp:Optional="true". </p>
@@ -1835,7 +1820,7 @@
<p>We show an example of a new version of policy that allows QName reference to Policies in the PolicyReference:</p>
- <example><head>WSDL containing 1.5 and 2.0 (compatible with 2.0) Policy References.</head>
+ <example><head>WSDL containing 1.5 and 1.6 (compatible with 1.5) Policy References.</head>
<eg><![CDATA[<wsdl11:binding name="StockQuoteSoapBinding" type="fab:Quote" >
<wsoap12:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http" />
@@ -1848,9 +1833,9 @@
wsdl11:required="true" />
</wsp:All>
<wsp:All>
- <wsp:PolicyReferenceByQName ref="rmp:RMAssertion"
+ <wsp16:PolicyReferenceByQName ref="rmp:RMAssertion"
wsdl11:required="true" />
- <wsp:PolicyReferenceByQName ref="sp:AsymmetricBinding"
+ <wsp16:PolicyReferenceByQName ref="sp:AsymmetricBinding"
wsdl11:required="true" />
</wsp:All>
</wsp:ExactlyOne>
@@ -1862,7 +1847,7 @@
<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>
+ <example><head>WSDL containing 1.5 and 1.6 (compatible with 1.5) Policy References.</head>
<eg><![CDATA[<wsdl11:binding name="StockQuoteSoapBinding" type="fab:Quote" >
<wsoap12:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http" />
@@ -2174,6 +2159,9 @@
<item><p>Added another example to <specref ref="compatible-policies"></specref>.</p></item>
<item><p>Dropped the editorial note in <specref ref="versioning-policy-language"/>.</p></item>
<item><p>Updated references: [<bibref ref="WS-AddressingMetadata"/>], [<bibref ref="WS-Policy"/>] and [<bibref ref="WS-PolicyAttachment"/>].</p></item>
+ <item>
+<p>Removed the illegal wsp:Choice example and changed wsp to wsp16 prefix in <specref ref="versioning-policy-language"/>.</p>
+</item>
</ulist>
</inform-div1>
<inform-div1 id="change-log">
@@ -2653,6 +2641,14 @@
<loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/370">370</loc>.
</td>
</tr>
+ <tr>
+ <td>20071023</td>
+ <td>DBO</td>
+ <td>Implemented the resolution for issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=5188">5188</loc>. Editors' action
+ <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/369">369</loc>.
+ </td>
+ </tr>
</tbody>
</table>
</inform-div1>
Received on Tuesday, 23 October 2007 20:51:45 UTC