- From: Asir Vedamuthu via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 07 Sep 2006 05:31:58 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv28447
Modified Files:
ws-policy-attachment.html ws-policy-attachment.xml
Log Message:
Implemented the resolution for issue 3557: clarify the use of domain expressions.
Index: ws-policy-attachment.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.xml,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -d -r1.34 -r1.35
--- ws-policy-attachment.xml 6 Sep 2006 18:15:24 -0000 1.34
+++ ws-policy-attachment.xml 7 Sep 2006 05:31:55 -0000 1.35
@@ -643,6 +643,9 @@
</def>
</gitem>
</glist>
+ <p>Domain expressions are used to identify entities such as endpoints, messages
+ or resources with which a policy can be associated. For example, domain expressions may
+ be used to refer to WSDL 1.1 definitions, WSDL 2.0 components, endpoint references, etc.</p>
<p>The following example illustrates the use of this mechanism with an
EndpointReference domain expression for a deployed endpoint as defined
in Web Services Addressing [<bibref ref='WS-Addressing'/>]:</p>
@@ -1954,6 +1957,15 @@
</tr>
</tbody>
+ <tr>
+ <td>20060906</td>
+ <td>ASV</td>
+ <td>Implemented the
+ <loc href="http://www.w3.org/2006/09/06-ws-policy-minutes.html#action07">resolution</loc>
+ for issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3557">3557</loc>: clarify the use of domain expressions.
+ </td>
+ </tr>
</table>
</inform-div1>
</back>
Index: ws-policy-attachment.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.html,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -d -r1.39 -r1.40
--- ws-policy-attachment.html 6 Sep 2006 18:15:24 -0000 1.39
+++ ws-policy-attachment.html 7 Sep 2006 05:31:55 -0000 1.40
@@ -1,4 +1,4 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en-US"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Policy 1.5 - Attachment</title><style type="text/css">
code { font-family: monospace; }
@@ -47,7 +47,7 @@
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
margin: 4px}
-</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"><link rel="contents" href="#contents"></head><body>
+</style><link type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/base.css"><link href="#contents" rel="contents"></head><body>
<div class="head">
<h1>Web Services Policy 1.5 - Attachment</h1>
<h2>Editors' copy $Date$ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
@@ -75,7 +75,7 @@
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="#tocRange">Introduction</a><br>2. <a href="#NotationsTerminology">Notations and Terminology</a><br> 2.1 <a href="#NotationalConventions">Notational Conventions</a><br> 2.2 <a href="#XMLNamespaces">XML Namespaces</a><br> 2.3 <a href="#Glossary">Terminology</a><br> 2.4 <a href="#Example">Example</a><br>3. <a href="#rPolicyAttachment">Policy Attachment</a><br> 3.1 <a href="#rEffectivePolicy">Effective Policy</a><br> 3.2 <a href="#PolicyAttachmentMechanisms">Policy Attachment Mechanisms</a><br> 3.3 <a href="#XMLElementAttachement">XML Element Attachment</a><br> 3.4 <a href="#ExternalPolicyAttachment">External Policy Attachment</a><br>4. <a href="#AttachingPolicyUsingWSDL1.1">Attaching Policies Using WSDL 1.1</a><br> 4.1 <a href="#CaculatingEffectivyPolicywithWSDL1.1">Calculating Effective Policy in WSDL 1.1</a><br> 4.1.1 <a href="#ServicePolicySubject">Service Policy Subject</a><br> 4.1.2 <a href="#EndpointPolicySubject">Endpoint Policy Subject</a><br> 4.1.3 <a href="#OperationPolicySubject">Operation Policy Subject</a><br> 4.1.4 <a href="#MessagePolicySubject">Message Policy Subject</a><br> 4.1.5 <a href="#Example2">Example</a><br>5. <a href="#AttachingPoliciesUsingUDDI">Attaching Policies Using UDDI</a><br> 5.1 <a href="#CalculatingEffectivePolicyElementPolicyUDDI">Calculating Effective Policy and Element Policy in UDDI</a><br> 5.1.1 <a href="#ServiceProviderPolicySubjectUDDI">Service Provider Policy Subject</a><br> nbsp; 5.1.2 <a href="#ServicePolicySubjectUDDI">Service Policy Subject</a><br> 5.1.3 <a href="#EndpointPolicySubjectUDDI">Endpoint Policy Subject</a><br> 5.2 <a href="#ReferencingRemotePolicyExpressions">Referencing Remote Policy Expressions</a><br> 5.3 <a href="#RegisteringReusablePolicyExpressions">Registering Reusable Policy Expressions</a><br> 5.4 <a href="#RegisteringPoliciesUDDIVersion3">Registering Policies in UDDI Version 3</a><br>6. <a href="#SecurityConsiderations">Security Considerations</a><br>7. <a href="#Conformance">Conformance</a><br></p>
-<h3><a name="appendix" id="appendix">Appendices</a></h3><p class="toc">A. <a href="#References">References</a><br> A.1 <a href="#Normative-References">Normative References</a><br> A.2 <a href="#Informative-References">Other References</a><br>B. <a href="#AppendixA">UDDI tModel Definitions</a><br> B.1 <a href="#RemotePolicyReferenceCategorySystem">Remote Policy Reference Category System</a><br> B.1.1 <a href="#DesigGoals1">Design Goals</a><br> B.1.2 <a href="#tModelDefinition1">tModel Definition</a><br> B.1.3 <a href="#ModelStructure1">tModel Structure</a><br> B.2 <a href="#WS-PolicyTypesCategorySystem">Web Services Policy Types Category System</a><br> B.2.1 <a href="#DesignGoals2">Design Goals</a><br> &bsp; B.2.2 <a href="#tModelDefinition2">tModel Definition</a><br> B.2.3 <a href="#ModelStructure2">tModel Structure</a><br> B.3 <a href="#LocalPolicyReferenceCategorySystem">Local Policy Reference Category System</a><br> B.3.1 <a href="#DesignGoals3">Design Goals</a><br> B.3.2 <a href="#tModelDefinition3">tModel Definition</a><br> B.3.3 <a href="#ModelStructure3">tModel Structure</a><br>C. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>D. <a href="#change-description">Changes in this Version of the Document</a> (Non-Normative)<br>E. <a href="#change-log">Web Services Policy 1.5 - Attachment Change Log</a> (Non-Normative)<br></p></div><hr><div class="body">
+<h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#References">References</a><br> A.1 <a href="#Normative-References">Normative References</a><br> A.2 <a href="#Informative-References">Other References</a><br>B. <a href="#AppendixA">UDDI tModel Definitions</a><br> B.1 <a href="#RemotePolicyReferenceCategorySystem">Remote Policy Reference Category System</a><br> B.1.1 <a href="#DesigGoals1">Design Goals</a><br> B.1.2 <a href="#tModelDefinition1">tModel Definition</a><br> B.1.3 <a href="#ModelStructure1">tModel Structure</a><br> B.2 <a href="#WS-PolicyTypesCategorySystem">Web Services Policy Types Category System</a><br> B.2.1 <a href="#DesignGoals2">Design Goals</a><br> &bsp; B.2.2 <a href="#tModelDefinition2">tModel Definition</a><br> B.2.3 <a href="#ModelStructure2">tModel Structure</a><br> B.3 <a href="#LocalPolicyReferenceCategorySystem">Local Policy Reference Category System</a><br> B.3.1 <a href="#DesignGoals3">Design Goals</a><br> B.3.2 <a href="#tModelDefinition3">tModel Definition</a><br> B.3.3 <a href="#ModelStructure3">tModel Structure</a><br>C. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>D. <a href="#change-description">Changes in this Version of the Document</a> (Non-Normative)<br>E. <a href="#change-log">Web Services Policy 1.5 - Attachment Change Log</a> (Non-Normative)<br></p></div><hr><div class="body">
<div class="div1">
<h2><a name="tocRange"></a>1. Introduction</h2>
@@ -283,7 +283,21 @@
<code class="elt">wsp:Policy</code> element with a
<code class="elt">wsp:All</code> element, and placing each as
children of a wrapper <code class="elt">wsp:Policy</code>
- element.</p></dd></dl>
+ element.</p></dd><dt class="label">policy</dt><dd><p>A <b>policy</b> is a
+collection of <a title="" href="#">policy
+alternatives</a>. </p></dd><dt class="label">policy alternative</dt><dd><p>A
+<b>policy alternative</b> is a collection of <a title="" href="#">policy assertions</a>.</p></dd><dt class="label">policy assertion</dt><dd><p>A
+<b>policy assertion</b> represents an individual requirement,
+capability, or other property of a behavior.</p></dd><dt class="label">policy attachment</dt><dd><p>A
+<b>policy attachment</b> is a mechanism for associating <a title="" href="#">policy</a> with one or more <a title="" href="#">policy scopes</a>.</p></dd><dt class="label">policy expression</dt><dd><p>A
+<b>policy expression</b> is an XML Infoset representation of a
+<a title="" href="#">policy</a>, either in a normal form or in
+an equivalent compact form. </p></dd><dt class="label">policy scope</dt><dd><p>A <b>policy
+scope</b> is a collection of <a title="" href="#">policy
+subjects</a> to which a policy may apply.</p></dd><dt class="label">policy subject</dt><dd><p>A <b>policy
+subject</b> is an entity (e.g., an endpoint, message, resource,
+interaction) with which a <a title="" href="#">policy</a> can
+be associated. </p></dd></dl>
</div>
@@ -301,7 +315,7 @@
[<cite><a href="#WS-SecurityPolicy">WS-SecurityPolicy</a></cite>].</p>
<div class="exampleOuter">
- <p style="text-align: left" class="exampleHead"><a name="Table2"></a><i><span>Example 2-1. </span>Example RM Policy Expression.</i></p>
+ <p class="exampleHead" style="text-align: left"><a name="Table2"></a><i><span>Example 2-1. </span>Example RM Policy Expression.</i></p>
<div class="exampleInner"><pre>(01) <wsp:Policy
xmlns:rmp="http://docs.oasis-open.org/ws-rx/wsrmp/200602"
xmlns:wsp="http://www.w3.org/@@@@/@@/policy"
@@ -316,7 +330,7 @@
(08) </wsp:Policy></pre></div>
</div>
<div class="exampleOuter">
- <p style="text-align: left" class="exampleHead"><a name="Table3"></a><i><span>Example 2-2. </span>Example X509 Security Policy Expression.</i></p>
+ <p class="exampleHead" style="text-align: left"><a name="Table3"></a><i><span>Example 2-2. </span>Example X509 Security Policy Expression.</i></p>
<div class="exampleInner"><pre>(01) <wsp:Policy
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
xmlns:wsp="http://www.w3.org/@@@@/@@/policy"
@@ -396,13 +410,13 @@
subject, and other attachments may be made by UDDI and other
mechanisms.</p>
- <p>When multiple attachments are made, [<a name="effective_policy" title="effective policy">Definition</a>: the
+ <p>When multiple attachments are made, [<a title="effective policy" name="effective_policy">Definition</a>: the
<b>effective policy</b>, for a given <a title="" href="#">policy subject</a>, is the
combination of relevant policies. The relevant policies are those
attached to <a title="" href="#">policy scopes</a> that
contain the <a title="" href="#">policy subject</a>.]
</p>
- <p>This combination can be achieved by: [<a name="merge" title="merge">Definition</a>: a <b>merge</b>
+ <p>This combination can be achieved by: [<a title="merge" name="merge">Definition</a>: a <b>merge</b>
consists of serializing each policy as a
<a title="" href="#">policy expression</a>, replacing their
<code class="elt">wsp:Policy</code> element with a
@@ -463,7 +477,7 @@
to form a single element <a title="" href="#">policy expression</a>.
The resultant <a title="" href="#">policy</a> is
then associated with the element information item's <a title="element policy" href="#element_policy">element policy</a>
-property. [<a name="element_policy" title="element policy">Definition</a>: The
+property. [<a title="element policy" name="element_policy">Definition</a>: The
<b>element policy</b> is the <a title="" href="#">policy</a> attached to the <a title="" href="#">policy subjects</a> associated with
the element information item that contains it.]</p>
@@ -483,7 +497,7 @@
it would result in an <a title="element policy" href="#element_policy">element policy</a>
whose XML 1.0 representation is listed in <a href="#Table4">Example 3-1</a>:</p>
<div class="exampleOuter">
- <p style="text-align: left" class="exampleHead"><a name="Table4"></a><i><span>Example 3-1. </span>Example Merged Policy Expression.</i></p>
+ <p class="exampleHead" style="text-align: left"><a name="Table4"></a><i><span>Example 3-1. </span>Example Merged Policy Expression.</i></p>
<div class="exampleInner"><pre>(01) <wsp:Policy
xmlns:rmp="http://docs.oasis-open.org/ws-rx/wsrmp/200602"
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
@@ -617,6 +631,9 @@
</dd>
</dl>
+ <p>Domain expressions are used to identify entities such as endpoints, messages
+ or resources with which a policy can be associated. For example, domain expressions may
+ be used to refer to WSDL 1.1 definitions, WSDL 2.0 components, endpoint references, etc.</p>
<p>The following example illustrates the use of this mechanism with an
EndpointReference domain expression for a deployed endpoint as defined
in Web Services Addressing [<cite><a href="#WS-Addressing">WS-Addressing Core</a></cite>]:</p>
@@ -709,7 +726,7 @@
or ports) are only considered in the <a title="effective policy" href="#effective_policy">effective policy</a> of that deployed
resource itself.</p>
-<div class="figure" style="text-align: center"><a name="Figure1"></a><br><img src="effective-policy-scope.png" alt="Effective Policy and Policy Scopes in WSDL"><p style="text-align:left"><i><span>Figure 4-1. </span>Effective Policy and Policy Scopes in WSDL</i></p><br></div>
+<div style="text-align: center" class="figure"><a name="Figure1"></a><br><img src="effective-policy-scope.png" alt="Effective Policy and Policy Scopes in WSDL"><p style="text-align:left"><i><span>Figure 4-1. </span>Effective Policy and Policy Scopes in WSDL</i></p><br></div>
<p>(This graphic is also available in SVG format <a href="effective-policy-scope.svg">here</a>.)</p>
<p>When attaching policies at different levels of the WSDL hierarchy, care must be taken.
@@ -878,7 +895,7 @@
<a href="#Table5">Example 4-1</a> that references policies. </p>
<div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><a name="Table5"></a><i><span>Example 4-1. </span>Example Policy Attached to WSDL.</i></p>
+<p class="exampleHead" style="text-align: left"><a name="Table5"></a><i><span>Example 4-1. </span>Example Policy Attached to WSDL.</i></p>
<div class="exampleInner"><pre>(01) <wsdl11:definitions name="StockQuote"
targetNamespace="http://www.example.com/stock/binding"
xmlns:tns="http://www.example.com/stock/binding"
@@ -945,7 +962,7 @@
whose XML 1.0 representation is listed in <a href="#Table6">Example 4-2</a>.</p>
<div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><a name="Table6"></a><i><span>Example 4-2. </span>Example Message Security Policy Expression.</i></p>
+<p class="exampleHead" style="text-align: left"><a name="Table6"></a><i><span>Example 4-2. </span>Example Message Security Policy Expression.</i></p>
<div class="exampleInner"><pre>(01) <wsp:Policy
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
xmlns:wsp="http://www.w3.org/@@@@/@@/policy"
@@ -1926,6 +1943,15 @@
</tr>
</tbody>
+ <tr>
+ <td rowspan="1" colspan="1">20060906</td>
+ <td rowspan="1" colspan="1">ASV</td>
+ <td rowspan="1" colspan="1">Implemented the
+ <a href="http://www.w3.org/2006/09/06-ws-policy-minutes.html#action07">resolution</a>
+ for issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3557">3557</a>: clarify the use of domain expressions.
+ </td>
+ </tr>
</table><br>
</div>
</div>
Received on Thursday, 7 September 2006 05:32:16 UTC