- From: Toufic Boubez via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 13 Dec 2006 19:12:33 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv24268
Modified Files:
ws-policy-primer.html ws-policy-primer.xml
Log Message:
Implemented the resolution for issue 3965
Editors' action 94
Index: ws-policy-primer.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -d -r1.28 -r1.29
--- ws-policy-primer.html 7 Dec 2006 16:54:57 -0000 1.28
+++ ws-policy-primer.html 13 Dec 2006 19:12:30 -0000 1.29
@@ -60,7 +60,7 @@
complete normative description of the Web Services Policy language. </p></div><div>
<h2><a name="status">Status of this Document</a></h2><p><strong>This document is an editors' copy that has
no official standing.</strong></p><p></p></div><hr><div class="toc">
-<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#introduction">Introduction</a><br>2. <a href="#basic-concepts-policy-expression">Basic Concepts: Policy Expression</a><br> 2.1 <a href="#web-services-policy">Web Services Policy</a><br> 2.2 <a href="#simple-message">Simple Message</a><br> 2.3 <a href="#secure-message">Secure Message</a><br> 2.4 <a href="#other-assertions">Other Assertions</a><br> 2.5 <a href="#combining-policy-assertions">Combining Policy Assertions</a><br> 2.6 <a href="#optional-policy-assertion">Optional Policy Assertion</a><br> 2.7 <a href="#nested-policy-expressions">Nested Policy Expressions</a><br> 2.8 <a href="#Referencing_Policy_Expressions">Referencing Policy Expressions</a><br> 2.9 <a href="#attaching-policy-expressions-to-wsdl">Attaching Policy Expresions to WSDL</a><br> 2.10 <a href="#policy-automates-web-services-interaction">Policy Automates Web Services Interaction</a><br>3. <a href="#advanced-concepts-policy-expression">Advanced Concepts: Policy Expression</a><br> 3.1 <a href="#policy-expression">Policy Expression</a><br> 3.2 <a href="#normal-form-for-policy-expressions">Normal Form for Policy Expressions</a><br> 3.3 <a href="#policy-data-model">Policy Data Model</a><br> 3.4 <a href="#compatible-policies">Compatible Policies</a><br> 3.5 <a href="#attaching-policy-expressions-to-wsdl2">Attaching Policy Expressions to WSDL</a><br> 3.6 <a href="#combine-policies">Combine Policies</a><br> 3.7 <a href="#extensibility-and-versioning">Extensibility and Versioning</a><br> 3.8 <a href="#parts-of-a-policy-assertion">Parts of a Policy Assertion</a><br>&nbp; 3.9 <a href="#versioning-policy-language">Versioning Policy Language</a><br> 3.9.1 <a href="#versioning-policy-framework">Policy Framework</a><br> 3.9.2 <a href="#versioning-policy-attachment">Policy Attachment</a><br>4. <a href="#conclusion">Conclusion</a><br></p>
+<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#introduction">Introduction</a><br>2. <a href="#basic-concepts-policy-expression">Basic Concepts: Policy Expression</a><br> 2.1 <a href="#web-services-policy">Web Services Policy</a><br> 2.2 <a href="#simple-message">Simple Message</a><br> 2.3 <a href="#secure-message">Secure Message</a><br> 2.4 <a href="#other-assertions">Other Assertions</a><br> 2.5 <a href="#combining-policy-assertions">Combining Policy Assertions</a><br> 2.6 <a href="#optional-policy-assertion">Optional Policy Assertion</a><br> 2.7 <a href="#nested-policy-expressions">Nested Policy Expressions</a><br> 2.8 <a href="#Referencing_Policy_Expressions">Referencing Policy Expressions</a><br> 2.9 <a href="#attaching-policy-expressions-to-wsdl">Attaching Policy Expresions to WSDL</a><br> 2.10 <a href="#policy-automates-web-services-interaction">Policy Automates Web Services Interaction</a><br>3. <a href="#advanced-concepts-policy-expression">Advanced Concepts: Policy Expression</a><br> 3.1 <a href="#policy-expression">Policy Expression</a><br> 3.2 <a href="#normal-form-for-policy-expressions">Normal Form for Policy Expressions</a><br> 3.3 <a href="#policy-data-model">Policy Data Model</a><br> 3.4 <a href="#compatible-policies">Compatible Policies</a><br> 3.5 <a href="#attaching-policy-expressions-to-wsdl2">Attaching Policy Expressions to WSDL</a><br> 3.6 <a href="#policy-retrieval">Policy Retrieval</a><br> 3.7 <a href="#combine-policies">Combine Policies</a><br> 3.8 <a href="#extensibility-and-versioning">Extensibility and Versioning</a><br> 39 <a href="#parts-of-a-policy-assertion">Parts of a Policy Assertion</a><br> 3.10 <a href="#versioning-policy-language">Versioning Policy Language</a><br> 3.10.1 <a href="#versioning-policy-framework">Policy Framework</a><br> 3.10.2 <a href="#versioning-policy-attachment">Policy Attachment</a><br>4. <a href="#conclusion">Conclusion</a><br></p>
<h3><a name="appendix" id="appendix">Appendices</a></h3><p class="toc">A. <a href="#security-considerations">Security Considerations</a><br>B. <a href="#xml-namespaces">XML Namespaces</a><br>C. <a href="#references">References</a><br>D. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>E. <a href="#change-description">Changes in this Version of the Document</a> (Non-Normative)<br>F. <a href="#change-log">Web Services Policy 1.5 - Primer Change Log</a> (Non-Normative)<br></p></div><hr><div class="body"><div class="div1">
<h2><a name="introduction"></a>1. Introduction</h2><p>This document, <em>Web Services Policy 1.5 - Primer</em>, provides an introductory description of the
Web Services Policy language and should be read alongside the formal descriptions contained
@@ -556,18 +556,8 @@
with a nested policy expression that has multiple policy alternatives converts to multiple
policy alternatives where the assertion contains a nested policy expression that has at
most one policy alternative.</p><p>The <code>PolicyReference</code> element is replaced with its referenced policy
- expression. Just as other service metadata languages, Web Services Policy does not mandate
- any specific policy retrieval mechanism. Any combination of any retrieval mechanisms in
- any order may be used for referencing policy expressions. Example retrieval mechanisms
- are:</p><ul><li><p>Do nothing. A policy expression with the referenced IRI is already known to be
- available in a local cache or chip (embedded systems).</p></li><li><p>Use the referenced IRI and retrieve an existing policy expression from the containing
- XML document: a policy element with an XML ID.</p></li><li><p>Use the referenced IRI and retrieve a policy expression from some policy repository
- (local or remote) or catalog. Policy tools may use any protocols (say Web Services
- Metadata Exchange) for such metadata retrieval. These protocols may require additional
- out of band information.</p></li><li><p>Attempt to resolve the referenced IRI on the Web. This may resolve to a policy
- element or a resource that contains a policy element.</p></li></ul><p>If the referenced policy expression is in the same XML document as the reference, then
- the policy expression should be identified using the <code>wsu:Id</code> (XML ID)
- attribute and referenced using an IRI reference to this XML ID value.</p></div><div class="div2">
+ expression. See section <a href="#policy-retrieval"><b>3.6 Policy Retrieval</b></a> for more details on how to
+ retrieve referenced policy expressions.</p></div><div class="div2">
<h3><a name="policy-data-model"></a>3.3 Policy Data Model</h3><p>In the previous section, we considered the normal form for policy expressions. As we
discussed, the normal form represents a policy as a collection of policy alternatives. In
this section, let us look at the policy data model.</p><p>Contoso uses a policy to convey the conditions for an interaction. Policy-aware clients,
@@ -696,7 +686,28 @@
port. Let us consider how to combine policy expressions in the next section.</p><p>Most of the policy assertions are designated for the endpoint, operation or message
policy subject. The commonly used WSDL attachment points are:</p><a name="Table2"></a><table border="1" cellspacing="0" cellpadding="5"><tbody><tr><th rowspan="1" colspan="1">Policy Subject</th><td rowspan="1" colspan="1">Commonly used attachment point (s)</td></tr><tr><th rowspan="1" colspan="1">Endpoint</th><td rowspan="1" colspan="1"><code>binding</code> element</td></tr><tr><th rowspan="1" colspan="1">Operation</th><td rowspan="1" colspan="1"><code>binding/operation</code> element</td></tr><tr><th rowspan="1" colspan="1">Message</th><td rowspan="1" colspan="1"><code>binding/operation/input</code> and <code>binding/operation/output</code>
elements</td></tr></tbody></table><br></div><div class="div2">
-<h3><a name="combine-policies"></a>3.6 Combine Policies</h3><p>Multiple policy expressions may be attached to WSDL constructs. Let us consider how
+<h3><a name="policy-retrieval"></a>3.6 Policy Retrieval</h3><p>
+ Just as other service metadata languages, Web Services Policy does not mandate
+ any specific policy retrieval mechanism. Any combination of any retrieval mechanisms in
+ any order may be used for referencing policy expressions. Example retrieval mechanisms
+ are:</p><ul><li><p>Do nothing. A policy expression with the referenced IRI is already known to be
+ available in a local cache or chip (embedded systems).</p></li><li><p>Use the referenced IRI and retrieve an existing policy expression from the containing
+ XML document: a policy element with an XML ID.</p></li><li><p>Use the referenced IRI and retrieve a policy expression from some policy repository
+ (local or remote) or catalog. Policy tools may use any protocols (say Web Services
+ Metadata Exchange) for such metadata retrieval. These protocols may require additional
+ out of band information.</p></li><li><p>Attempt to resolve the referenced IRI on the Web. This may resolve to a policy
+ element or a resource that contains a policy element.</p></li></ul><p>If the referenced policy expression is in the same XML document as the reference, then
+ the policy expression should be identified using the <code>wsu:Id</code> (XML ID)
+ attribute and referenced using an IRI reference to this XML ID value.</p><p>
+ WSDL 1.1 [<cite><a href="#WSDL11">WSDL 1.1</a></cite>] section 2.1 and WSDL 2.0 [<cite><a href="#WSDL20">WSDL 2.0 Core Language</a></cite>] chapter 4
+ allow to import or include WSDL documents into another WSDL document with the
+ wsdl11:import, wsdl20:import, and wsdl20:include statements. The importing and
+ imported WSDL documents constitute separate XML documents each. If e.g. the
+ importing WSDL document references a policy in the imported WSDL document, the
+ rules for policy references between separate XML documents apply as described
+ in <a href="#Referencing_Policy_Expressions"><b>2.8 Referencing Policy Expressions</b></a>.
+ </p></div><div class="div2">
+<h3><a name="combine-policies"></a>3.7 Combine Policies</h3><p>Multiple policy expressions may be attached to WSDL constructs. Let us consider how
Contoso could have used multiple policy expressions in a WSDL document. In the example
below, there are two policy expressions <code>#common2</code> and <code>#secure2</code>
attached to the <code>SecureBinding</code> WSDL binding and <code>RealTimeDataPort</code>
@@ -755,7 +766,7 @@
unordered collection of policy alternatives. That is, the order of policy alternatives is
insignificant. Therefore, the order of combining these policy expressions is
insignificant.</p></div><div class="div2">
-<h3><a name="extensibility-and-versioning"></a>3.7 Extensibility and Versioning</h3><p>Web Services Policy language is an extensible language by design. The
+<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
@@ -811,7 +822,7 @@
similar to how a proxy generator that generates code from WSDL creates code for all the
known WSDL constructs and allows Web service developers to fill in code for custom or
unknown constructs in the WSDL.</p></div><div class="div2">
-<h3><a name="parts-of-a-policy-assertion"></a>3.8 Parts of a Policy Assertion</h3><p>As we discussed, a policy assertion identifies a domain specific behavior or requirement
+<h3><a name="parts-of-a-policy-assertion"></a>3.9 Parts of a Policy Assertion</h3><p>As we discussed, a policy assertion identifies a domain specific behavior or requirement
or condition. A policy assertion has a QName that identifies its behavior or requirement
or condition. A policy assertion may contain assertion parameters and a nested policy.</p><p>Let us look at the anatomy of a policy assertion from the security domain. The policy
expression in the diagram below uses the <code>sp:IssuedToken</code> policy assertion.
@@ -849,14 +860,14 @@
by a third party. Service providers, like Contoso, must convey this usage and all the
necessary information to obtain this security token for Web service developers. This is a
key piece of metadata for a successful interaction with Contoso’s Web services.</p></div><div class="div2">
-<h3><a name="versioning-policy-language"></a>3.9 Versioning Policy Language</h3><p>
+<h3><a name="versioning-policy-language"></a>3.10 Versioning Policy Language</h3><p>
<table border="1" summary="Editorial note"><tr><td align="left" valign="top" width="50%"><b>Editorial note</b></td><td align="right" valign="top" width="50%"> </td></tr><tr><td colspan="2" align="left" valign="top">
The WG is contemplating moving some or all of this material into a non-normative appendix of the framework or attachment document. User feedback is solicited
</td></tr></table>
</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.9.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><wsp:Policy>
+<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><wsp:Policy>
<wsp:ExactlyOne>
<wsp16:Choice wsp16:minOccurs="1" wsp16:maxOccurs="2">
...
@@ -926,7 +937,7 @@
...
</wsp:ExactlyOne>
</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="div3">
-<h4><a name="versioning-policy-attachment"></a>3.9.2 Policy Attachment</h4><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.
+<h4><a name="versioning-policy-attachment"></a>3.10.2 Policy Attachment</h4><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 3-21. </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" >
<wsoap12:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http" />
@@ -1179,4 +1190,8 @@
<a href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Dec/0018.html">as outlined</a>
(with editorial correction replacing "for as" with "as"),
Editors' action <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/92">92</a>.
+ </td></tr><tr><td rowspan="1" colspan="1">20061213</td><td rowspan="1" colspan="1">TIB</td><td rowspan="1" colspan="1">Implemented the resolution for
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3965">issue 3965</a>
+ <a href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Dec/0016.html">as outlined.</a>
+ Editors' action <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/94">94</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.24
retrieving revision 1.25
diff -u -d -r1.24 -r1.25
--- ws-policy-primer.xml 7 Dec 2006 16:35:51 -0000 1.24
+++ ws-policy-primer.xml 13 Dec 2006 19:12:30 -0000 1.25
@@ -844,33 +844,8 @@
policy alternatives where the assertion contains a nested policy expression that has at
most one policy alternative.</p>
<p>The <code>PolicyReference</code> element is replaced with its referenced policy
- expression. Just as other service metadata languages, Web Services Policy does not mandate
- any specific policy retrieval mechanism. Any combination of any retrieval mechanisms in
- any order may be used for referencing policy expressions. Example retrieval mechanisms
- are:</p>
- <ulist>
- <item>
- <p>Do nothing. A policy expression with the referenced IRI is already known to be
- available in a local cache or chip (embedded systems).</p>
- </item>
- <item>
- <p>Use the referenced IRI and retrieve an existing policy expression from the containing
- XML document: a policy element with an XML ID.</p>
- </item>
- <item>
- <p>Use the referenced IRI and retrieve a policy expression from some policy repository
- (local or remote) or catalog. Policy tools may use any protocols (say Web Services
- Metadata Exchange) for such metadata retrieval. These protocols may require additional
- out of band information.</p>
- </item>
- <item>
- <p>Attempt to resolve the referenced IRI on the Web. This may resolve to a policy
- element or a resource that contains a policy element.</p>
- </item>
- </ulist>
- <p>If the referenced policy expression is in the same XML document as the reference, then
- the policy expression should be identified using the <code>wsu:Id</code> (XML ID)
- attribute and referenced using an IRI reference to this XML ID value.</p>
+ expression. See section <specref ref="policy-retrieval"/> for more details on how to
+ retrieve referenced policy expressions.</p>
</div2>
<div2 id="policy-data-model">
<head>Policy Data Model</head>
@@ -1086,6 +1061,46 @@
</tbody>
</table>
</div2>
+ <div2 id="policy-retrieval">
+ <head>Policy Retrieval</head>
+ <p>
+ Just as other service metadata languages, Web Services Policy does not mandate
+ any specific policy retrieval mechanism. Any combination of any retrieval mechanisms in
+ any order may be used for referencing policy expressions. Example retrieval mechanisms
+ are:</p>
+ <ulist>
+ <item>
+ <p>Do nothing. A policy expression with the referenced IRI is already known to be
+ available in a local cache or chip (embedded systems).</p>
+ </item>
+ <item>
+ <p>Use the referenced IRI and retrieve an existing policy expression from the containing
+ XML document: a policy element with an XML ID.</p>
+ </item>
+ <item>
+ <p>Use the referenced IRI and retrieve a policy expression from some policy repository
+ (local or remote) or catalog. Policy tools may use any protocols (say Web Services
+ Metadata Exchange) for such metadata retrieval. These protocols may require additional
+ out of band information.</p>
+ </item>
+ <item>
+ <p>Attempt to resolve the referenced IRI on the Web. This may resolve to a policy
+ element or a resource that contains a policy element.</p>
+ </item>
+ </ulist>
+ <p>If the referenced policy expression is in the same XML document as the reference, then
+ the policy expression should be identified using the <code>wsu:Id</code> (XML ID)
+ attribute and referenced using an IRI reference to this XML ID value.</p>
+ <p>
+ WSDL 1.1 [<bibref ref="WSDL11"/>] section 2.1 and WSDL 2.0 [<bibref ref="WSDL20"/>] chapter 4
+ allow to import or include WSDL documents into another WSDL document with the
+ wsdl11:import, wsdl20:import, and wsdl20:include statements. The importing and
+ imported WSDL documents constitute separate XML documents each. If e.g. the
+ importing WSDL document references a policy in the imported WSDL document, the
+ rules for policy references between separate XML documents apply as described
+ in <specref ref="Referencing_Policy_Expressions" />.
+ </p>
+ </div2>
<div2 id="combine-policies">
<head>Combine Policies</head>
<p>Multiple policy expressions may be attached to WSDL constructs. Let us consider how
@@ -1908,6 +1923,15 @@
Editors' action <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/92">92</loc>.
</td>
</tr>
+ <tr>
+ <td>20061213</td>
+ <td>TIB</td>
+ <td>Implemented the resolution for
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3965">issue 3965</loc>
+ <loc href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Dec/0016.html">as outlined.</loc>
+ Editors' action <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/94">94</loc>.
+ </td>
+ </tr>
</tbody>
</table>
</inform-div1>
Received on Wednesday, 13 December 2006 19:13:01 UTC