- From: David Orchard via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 26 Oct 2007 22:09:45 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv5062
Modified Files:
ws-policy-primer.html ws-policy-primer.xml
Log Message:
Editors Action 377
Index: ws-policy-primer.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer.html,v
retrieving revision 1.76
retrieving revision 1.77
diff -u -d -r1.76 -r1.77
--- ws-policy-primer.html 24 Oct 2007 13:47:17 -0000 1.76
+++ ws-policy-primer.html 26 Oct 2007 22:09:42 -0000 1.77
@@ -127,7 +127,7 @@
3.7 <a href="#combine-policies">Combine Policies</a><br>
3.8 <a href="#extensibility-and-versioning">Extensibility and Versioning</a><br>
3.8.1 <a href="#ext-vers-policylanguage">Policy Language</a><br>
- 3.8.2 <a href="#d3e1425">Policy Expressions</a><br>
+ 3.8.2 <a href="#d3e1441">Policy Expressions</a><br>
3.8.3 <a href="#ignorable-and-versioning">Use of Ignorable attribute and an alternative Versioning Scenario</a><br>
3.8.4 <a href="#ignorable-and-optional-and-versioning">Use of Ignorable and Optional attributes</a><br>
3.9 <a href="#parts-of-a-policy-assertion">Parts of a Policy Assertion</a><br>
@@ -570,15 +570,39 @@
</Policy></pre></div></div><p>The <code>Name</code> attribute is an alternate mechanism to identify a policy
expression. The value of the <code>Name</code> attribute is an absolute IRI and is
independent of the location of the XML document where the identified policy expression
- resides in. As such, referencing a policy expression using the <code>Name</code> attribute
- relies on additional out of band information. In the example below, the <code>Name</code>
+ resides in. As such, referencing a policy expression using the Name attribute relies on
+ additional out of band information and is outside the scope of the Web Services Policy
+ Framework and Attachment (See <a href="#policy-retrieval"><b>3.6 Policy Retrieval</b></a>). In the example below, the <code>Name</code>
attribute identifies the policy expression. The IRI of this policy expression is
<code>http://x.example.com/policy/common</code>.</p><div class="exampleOuter">
<p style="text-align: left" class="exampleHead"><i><span>Example 2-19. </span>Common Policy Expression</i></p><div class="exampleInner"><pre><Policy Name=”http://x.example.com/policy/common”>
<mtom:OptimizedMimeSerialization wsp:Optional="true"/>
<wsam:Addressing>…</wsam:Addressing>
</Policy></pre></div></div><p>The example below is a policy expression that re-uses the common policy expression above.</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-20. </span>PolicyReference to Common Policy Expression</i></p><div class="exampleInner"><pre><PolicyReference URI="http://x.example.com/policy/common"/></pre></div></div><p>As policy expressions are composed from other policy expressions and
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-20. </span>PolicyReference to Common Policy Expression</i></p><div class="exampleInner"><pre><PolicyReference URI="http://x.example.com/policy/common"/></pre></div></div><p>
+ The following example shows a policy expression identified using a UDDI key, which may refer to a tModel that references the reusable policy expression as described in section 6.3 of <cite><a href="#WS-PolicyAttachment">Web Services Policy Attachment</a></cite>. </p><div class="exampleOuter">
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-21. </span>PolicyReference to Reusable Policy Expression in UDDI</i></p><div class="exampleInner"><pre><PolicyReference URI="uddi:3bed4710-1f46-11dc-899e-391cf3b1899c"/>
+</pre></div></div><p>The reusable policy expression could be registered in UDDI using a tModel as shown below</p><div class="exampleOuter">
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-22. </span>UDDI tModel for a Reusable Policy Expression</i></p><div class="exampleInner"><pre><tModel tModelKey="uddi:3bed4710-1f46-11dc-899e-391cf3b1899c">
+ <name>�</name>
+ <description xml:lang="EN">
+Policy Expression for example's Web services
+ </description>
+ <overviewDoc>
+ <description xml:lang="EN">Web Services Policy Expression</description>
+ <overviewURL>http://repository.example.com/policy/common</overviewURL>
+ </overviewDoc>
+ <categoryBag>
+ <keyedReference
+ keyName="Reusable policy Expression"
+ keyValue="policy"
+ tModelKey="uddi:w3.org:ws-policy:v1.5:attachment:policytypes" />
+ <keyedReference
+ keyName="Policy Expression for example's Web services"
+ keyValue="http://x.example.com/policy/common"
+ tModelKey="uddi:w3.org:ws-policy:v1.5:attachment:remotepolicyreference" />
+ </categoryBag>
+</tModel></pre></div></div><p>As policy expressions are composed from other policy expressions and
assertions from different domains are used in a policy expression,
complex expressions will emerge. Naming parts of complex expressions for
reuse and building more complex policies through referencing enables
@@ -602,7 +626,7 @@
any message exchange associated with any <code>port</code> that supports this binding
description. This includes all the message exchanges described by operations in the
<code>RealTimeDataInterface</code>.</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-21. </span>Secure Policy Expression Attached to WSDL Binding</i></p><div class="exampleInner"><pre><wsdl:binding name="SecureBinding" type="tns:RealTimeDataInterface" >
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-23. </span>Secure Policy Expression Attached to WSDL Binding</i></p><div class="exampleInner"><pre><wsdl:binding name="SecureBinding" type="tns:RealTimeDataInterface" >
<PolicyReference URI="#secure" />
<wsdl:operation name="GetRealQuote">…</wsdl:operation>
…
@@ -613,7 +637,7 @@
<code>GetSymbol</code> and <code>GetSymbols</code>). Company-X does not require the use of
security for these services, but requires the use of addressing and allows the use of
optimization.</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-22. </span>Open Policy Expression Attached to WSDL Binding</i></p><div class="exampleInner"><pre><wsdl:binding name="OpenBinding" type="tns:DelayedDataInterface" >
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-24. </span>Open Policy Expression Attached to WSDL Binding</i></p><div class="exampleInner"><pre><wsdl:binding name="OpenBinding" type="tns:DelayedDataInterface" >
<PolicyReference URI="#common" />
<wsdl:operation name="GetDelayedQuote">…</wsdl:operation>
…
@@ -1089,7 +1113,7 @@
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></div><div class="div3">
-<h4><a name="d3e1425" id="d3e1425"></a>3.8.2 Policy Expressions</h4><p>Services that use the Web Services Policy language for policy expression enable simple versioning practices that allow requesters to
+<h4><a name="d3e1441" id="d3e1441"></a>3.8.2 Policy Expressions</h4><p>Services that use the Web Services Policy language for policy expression enable simple versioning practices that allow requesters to
continue the use of older policy alternatives in a backward compatible manner. This
versioning practice allows service providers, like Company-X, to deploy new behaviors using additional (or new) policy
assertions without breaking compatibility with clients that rely on any older policy
@@ -1509,7 +1533,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><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-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><li><p>Added UDDI example into <a href="#Referencing_Policy_Expressions"><b>2.10 Referencing Policy Expressions</b></a></p></li></ul></iv><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>
@@ -1683,4 +1707,7 @@
</td></tr><tr><td rowspan="1" colspan="1">20071024</td><td rowspan="1" colspan="1">TIB</td><td rowspan="1" colspan="1">Implemented the resolution for issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=5187">5187</a>. Editors' action
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/368">368</a>.
+ </td></tr><tr><td rowspan="1" colspan="1">20071026</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?">TBD</a>. Editors' action
+ <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/377">377</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.82
retrieving revision 1.83
diff -u -d -r1.82 -r1.83
--- ws-policy-primer.xml 24 Oct 2007 13:47:17 -0000 1.82
+++ ws-policy-primer.xml 26 Oct 2007 22:09:42 -0000 1.83
@@ -686,8 +686,9 @@
<p>The <code>Name</code> attribute is an alternate mechanism to identify a policy
expression. The value of the <code>Name</code> attribute is an absolute IRI and is
independent of the location of the XML document where the identified policy expression
- resides in. As such, referencing a policy expression using the <code>Name</code> attribute
- relies on additional out of band information. In the example below, the <code>Name</code>
+ resides in. As such, referencing a policy expression using the Name attribute relies on
+ additional out of band information and is outside the scope of the Web Services Policy
+ Framework and Attachment (See <specref ref="policy-retrieval"/>). In the example below, the <code>Name</code>
attribute identifies the policy expression. The IRI of this policy expression is
<code>http://x.example.com/policy/common</code>.</p>
<example>
@@ -702,6 +703,37 @@
<head>PolicyReference to Common Policy Expression</head>
<eg xml:space="preserve"><PolicyReference URI="http://x.example.com/policy/common"/></eg>
</example>
+ <p>
+ The following example shows a policy expression identified using a UDDI key, which may refer to a tModel that references the reusable policy expression as described in section 6.3 of <bibref ref="WS-PolicyAttachment"/>. </p>
+ <example>
+ <head>PolicyReference to Reusable Policy Expression in UDDI</head>
+ <eg xml:space="preserve"><PolicyReference URI="uddi:3bed4710-1f46-11dc-899e-391cf3b1899c"/>
+</eg>
+</example>
+<p>The reusable policy expression could be registered in UDDI using a tModel as shown below</p>
+<example>
+<head>UDDI tModel for a Reusable Policy Expression</head>
+<eg xml:space="preserve"><tModel tModelKey="uddi:3bed4710-1f46-11dc-899e-391cf3b1899c">
+ <name>�</name>
+ <description xml:lang="EN">
+Policy Expression for example's Web services
+ </description>
+ <overviewDoc>
+ <description xml:lang="EN">Web Services Policy Expression</description>
+ <overviewURL>http://repository.example.com/policy/common</overviewURL>
+ </overviewDoc>
+ <categoryBag>
+ <keyedReference
+ keyName="Reusable policy Expression"
+ keyValue="policy"
+ tModelKey="uddi:w3.org:ws-policy:v1.5:attachment:policytypes" />
+ <keyedReference
+ keyName="Policy Expression for example's Web services"
+ keyValue="http://x.example.com/policy/common"
+ tModelKey="uddi:w3.org:ws-policy:v1.5:attachment:remotepolicyreference" />
+ </categoryBag>
+</tModel></eg></example>
+
<p>As policy expressions are composed from other policy expressions and
assertions from different domains are used in a policy expression,
complex expressions will emerge. Naming parts of complex expressions for
@@ -2157,8 +2189,8 @@
<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>
+<p>Removed the illegal wsp:Choice example and changed wsp to wsp16 prefix in <specref ref="versioning-policy-language"/>.</p></item>
+<item><p>Added UDDI example into <specref ref="Referencing_Policy_Expressions"/></p></item>
</ulist>
</inform-div1>
<inform-div1 id="change-log">
@@ -2654,6 +2686,14 @@
<loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/368">368</loc>.
</td>
</tr>
+ <tr>
+ <td>20071026</td>
+ <td>DBO</td>
+ <td>Implemented the resolution for issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?">TBD</loc>. Editors' action
+ <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/377">377</loc>.
+ </td>
+ </tr>
</tbody>
</table>
</inform-div1>
Received on Friday, 26 October 2007 22:09:53 UTC