- From: Asir Vedamuthu via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 21 Jul 2006 11:58:59 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv2138
Modified Files:
ws-policy-attachment.html ws-policy-attachment.xml
Log Message:
Completed action items 23, 25 and 26 from the Austin F2F.
Index: ws-policy-attachment.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- ws-policy-attachment.xml 19 Jul 2006 23:11:50 -0000 1.7
+++ ws-policy-attachment.xml 21 Jul 2006 11:58:57 -0000 1.8
@@ -705,7 +705,10 @@
<graphic id='Figure1' source='effective-policy-scope.svg' alt='Effective Policy and Policy Scopes in WSDL'/>
-<p>When attaching policies at different levels of the WSDL hierarchy, care must be taken. A message exchange with a deployed endpoint <rfc2119>MAY</rfc2119> contain <termref def='effective_policy'>effective policies</termref> in all four subject types simultaneously.</p>
+<p>When attaching policies at different levels of the WSDL hierarchy, care must be taken.
+A message <rfc2119>MAY</rfc2119> be described by the
+<termref def='effective_policy'>effective policies</termref>
+in all four subject types simultaneously.</p>
<p>For example, in <specref ref='Figure1'/>, for a particular input message to a deployed
endpoint, there are four <termref def='policy_subject'>policy subjects</termref> involved, each with their own
@@ -745,11 +748,8 @@
Section <specref ref='rPolicyAttachment'/>, and if present
<rfc2119>MUST</rfc2119> be merged into the <termref def='effective_policy'>effective policy</termref> of the
WSDL service policy subject.</p>
-<p>Policy attached to the service
-policy subject applies to behaviors or aspects of the service as a
-whole, irrespective of interactions over any particular port. This
-includes — but is not limited to — acting as a consumer or
-a provider of the service.</p>
+ <p>A policy associated with a service policy subject applies to any
+ message exchange using any of the endpoints offered by that service.</p>
</div3>
<div3 id='EndpointPolicySubject'>
<head>Endpoint Policy Subject</head>
@@ -763,11 +763,8 @@
<p>Since the <el>wsdl11:portType</el> may be used by more than one
binding, it is <rfc2119>RECOMMENDED</rfc2119> that only policies
containing abstract (i.e., binding independent) assertions should be
-attached to this type of element.</p> <p>An endpoint policy subject
-applies to behaviours associated with an entire endpoint of the
-service, irrespective of any message exchange made. This includes
-— but is not limited to — aspects of communicating with or
-instantiating the endpoint.</p>
+ attached to this type of element.</p> <p>Policies associated with an endpoint
+ policy subject apply to any message exchange made using that endpoint.</p>
<p>The <termref def='effective_policy'>effective policy</termref> for a WSDL endpoint policy subject includes
the <termref def='element_policy'>element policy</termref> of the <el>wsdl11:port</el> element that defines
@@ -793,10 +790,8 @@
policies containing abstract (i.e., binding independent) assertions
should be attached to this type of element.</p>
-<p>Policies attached to an operation policy subject affect behaviours
-associated with a sequence of message exchanges, as defined by a WSDL
-operation. This includes — but is not limited to — initiating the
-sequence and ending the sequence.</p>
+ <p>Policies associated with an operation policy subject apply to
+ the message exchange described by that operation.</p>
<p>The <termref def='effective_policy'>effective policy</termref> for a WSDL operation policy subject is
calculated in relation to a specific port, and includes the <termref def='element_policy'>element
@@ -823,9 +818,8 @@
policy subject representing the specific input, output, or fault
message in relation to the operation policy subject.</p>
-<p>Policy attached to a message policy subject pertains to behaviours
-associated with a particular message. This includes — but is not
-limited to — sending and receiving the message. </p>
+ <p>Policies associated with a message policy subject apply to that
+ message (i.e. input, output or fault message).</p>
<p>The <termref def='effective_policy'>effective policy</termref> for a specific WSDL message (i.e., input,
output, or fault message) is calculated in relation to a specific
@@ -1813,6 +1807,15 @@
<td>Completed action item <loc href="http://www.w3.org/2006/07/13-ws-policy-minutes.html#action22">22: Linked SVG graphic</loc>
</td>
</tr>
+ <tr>
+ <td>20060721</td>
+ <td>ASV</td>
+ <td>Completed action items
+ <loc href="http://www.w3.org/2006/07/13-ws-policy-minutes.html#action23">23</loc>,
+ <loc href="http://www.w3.org/2006/07/13-ws-policy-minutes.html#action25">25</loc> and
+ <loc href="http://www.w3.org/2006/07/13-ws-policy-minutes.html#action26">26</loc>
+ from the Austin F2F.</td>
+ </tr>
</tbody>
</table>
</inform-div1>
Index: ws-policy-attachment.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- ws-policy-attachment.html 19 Jul 2006 23:11:50 -0000 1.10
+++ ws-policy-attachment.html 21 Jul 2006 11:58:56 -0000 1.11
@@ -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> 4.2 <a href="#ExternalAttachmentDeployedEndpoints">External Attachment to Deployed Endpoints</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> &bsp; 5.1.1 <a href="#ServiceProviderPolicySubjectUDDI">Service Provider Policy Subject</a><br> 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></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="#changelog">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="#changelog">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>
@@ -245,41 +245,41 @@
<p>We introduce the following terms that are used throughout this document:</p>
-<p>[<a name="policy" title="policy">Definition</a>: A <b>policy</b> is a
+<p>[<a title="policy" name="policy">Definition</a>: A <b>policy</b> is a
collection of <a title="policy alternative" href="#policy_alternative">policy
alternatives</a>. ]</p>
-<p>[<a name="policy_alternative" title="policy alternative">Definition</a>: A
+<p>[<a title="policy alternative" name="policy_alternative">Definition</a>: A
<b>policy alternative</b> is a collection of <a title="policy assertion" href="#policy_assertion">policy assertions</a>.]</p>
-<p>[<a name="policy_assertion" title="policy assertion">Definition</a>: A
+<p>[<a title="policy assertion" name="policy_assertion">Definition</a>: A
<b>policy assertion</b> represents an individual requirement,
capability, or other property of a behavior.]</p>
-<p>[<a name="policy_expression" title="policy expression">Definition</a>: A
+<p>[<a title="policy expression" name="policy_expression">Definition</a>: A
<b>policy expression</b> is an XML Infoset representation of a
<a title="policy" href="#policy">policy</a>, either in a normal form or in
an equivalent compact form. ]</p>
-<p>[<a name="policy_subject" title="policy subject">Definition</a>: A <b>policy
+<p>[<a title="policy subject" name="policy_subject">Definition</a>: A <b>policy
subject</b> is an entity (e.g., an endpoint, message, resource,
interaction) with which a <a title="policy" href="#policy">policy</a> can
be associated. ]</p>
-<p>[<a name="policy_scope" title="policy scope">Definition</a>: A <b>policy
+<p>[<a title="policy scope" name="policy_scope">Definition</a>: A <b>policy
scope</b> is a collection of <a title="policy subject" href="#policy_subject">policy
subjects</a> to which a policy may apply.]</p>
-<p>[<a name="policy_attachment" title="policy attachment">Definition</a>: A
+<p>[<a title="policy attachment" name="policy_attachment">Definition</a>: A
<b>policy attachment</b> is a mechanism for associating <a title="policy" href="#policy">policy</a> with one or more <a title="policy scope" href="#policy_scope">policy scopes</a>.]</p>
-<p>[<a name="effective_policy" title="effective policy">Definition</a>: An
+<p>[<a title="effective policy" name="effective_policy">Definition</a>: An
<b>effective policy</b>, for a given <a title="policy subject" href="#policy_subject">policy subject</a>, is the resultant
combination of relevant policies. The relevant policies are those
attached to <a title="policy scope" href="#policy_scope">policy scopes</a> that
contain the policy subject.]</p>
-<p>[<a name="element_policy" title="element policy">Definition</a>: The
+<p>[<a title="element policy" name="element_policy">Definition</a>: The
<b>element policy</b> is the <a title="policy" href="#policy">policy</a> attached to the <a title="policy subject" href="#policy_subject">policy subjects</a> associated with
the element information item that contains it.]</p>
@@ -298,7 +298,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"
@@ -313,7 +313,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"
@@ -469,7 +469,7 @@
</pre></div>
<p>have been processed and <em>merged</em>, 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"
@@ -691,9 +691,12 @@
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.svg" 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.svg" 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>When attaching policies at different levels of the WSDL hierarchy, care must be taken. A message exchange with a deployed endpoint <span class="rfc2119">MAY</span> contain <a title="effective policy" href="#effective_policy">effective policies</a> in all four subject types simultaneously.</p>
+<p>When attaching policies at different levels of the WSDL hierarchy, care must be taken.
+A message <span class="rfc2119">MAY</span> be described by the
+<a title="effective policy" href="#effective_policy">effective policies</a>
+in all four subject types simultaneously.</p>
<p>For example, in <a href="#Figure1">Figure 4-1</a>, for a particular input message to a deployed
endpoint, there are four <a title="policy subject" href="#policy_subject">policy subjects</a> involved, each with their own
@@ -733,11 +736,8 @@
Section <a href="#rPolicyAttachment"><b>3. Policy Attachment</b></a>, and if present
<span class="rfc2119">MUST</span> be merged into the <a title="effective policy" href="#effective_policy">effective policy</a> of the
WSDL service policy subject.</p>
-<p>Policy attached to the service
-policy subject applies to behaviors or aspects of the service as a
-whole, irrespective of interactions over any particular port. This
-includes — but is not limited to — acting as a consumer or
-a provider of the service.</p>
+ <p>A policy associated with a service policy subject applies to any
+ message exchange using any of the endpoints offered by that service.</p>
</div>
<div class="div3">
@@ -752,11 +752,8 @@
<p>Since the <code class="elt">wsdl11:portType</code> may be used by more than one
binding, it is <span class="rfc2119">RECOMMENDED</span> that only policies
containing abstract (i.e., binding independent) assertions should be
-attached to this type of element.</p> <p>An endpoint policy subject
-applies to behaviours associated with an entire endpoint of the
-service, irrespective of any message exchange made. This includes
-— but is not limited to — aspects of communicating with or
-instantiating the endpoint.</p>
+ attached to this type of element.</p> <p>Policies associated with an endpoint
+ policy subject apply to any message exchange made using that endpoint.</p>
<p>The <a title="effective policy" href="#effective_policy">effective policy</a> for a WSDL endpoint policy subject includes
the <a title="element policy" href="#element_policy">element policy</a> of the <code class="elt">wsdl11:port</code> element that defines
@@ -783,10 +780,8 @@
policies containing abstract (i.e., binding independent) assertions
should be attached to this type of element.</p>
-<p>Policies attached to an operation policy subject affect behaviours
-associated with a sequence of message exchanges, as defined by a WSDL
-operation. This includes — but is not limited to — initiating the
-sequence and ending the sequence.</p>
+ <p>Policies associated with an operation policy subject apply to
+ the message exchange described by that operation.</p>
<p>The <a title="effective policy" href="#effective_policy">effective policy</a> for a WSDL operation policy subject is
calculated in relation to a specific port, and includes the <a title="element policy" href="#element_policy">element
@@ -814,9 +809,8 @@
policy subject representing the specific input, output, or fault
message in relation to the operation policy subject.</p>
-<p>Policy attached to a message policy subject pertains to behaviours
-associated with a particular message. This includes — but is not
-limited to — sending and receiving the message. </p>
+ <p>Policies associated with a message policy subject apply to that
+ message (i.e. input, output or fault message).</p>
<p>The <a title="effective policy" href="#effective_policy">effective policy</a> for a specific WSDL message (i.e., input,
output, or fault message) is calculated in relation to a specific
@@ -865,7 +859,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"
@@ -932,7 +926,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"
@@ -1796,6 +1790,15 @@
<td rowspan="1" colspan="1">Completed action item <a href="http://www.w3.org/2006/07/13-ws-policy-minutes.html#action22">22: Linked SVG graphic</a>
</td>
</tr>
+ <tr>
+ <td rowspan="1" colspan="1">20060721</td>
+ <td rowspan="1" colspan="1">ASV</td>
+ <td rowspan="1" colspan="1">Completed action items
+ <a href="http://www.w3.org/2006/07/13-ws-policy-minutes.html#action23">23</a>,
+ <a href="http://www.w3.org/2006/07/13-ws-policy-minutes.html#action25">25</a> and
+ <a href="http://www.w3.org/2006/07/13-ws-policy-minutes.html#action26">26</a>
+ from the Austin F2F.</td>
+ </tr>
</tbody>
</table><br>
</div>
Received on Friday, 21 July 2006 11:59:06 UTC