- From: Asir Vedamuthu via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 09 Aug 2006 23:16:11 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv5028
Modified Files:
ws-policy-framework.xml ws-policy-framework.html
ws-policy-attachment.html ws-policy-attachment.xml
Log Message:
Framework:
Implemented the resolution for issue 3563.
Attachment:
Implemented the resolution for issue 3556 and the resolution for issue 3558.
Index: ws-policy-framework.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -d -r1.20 -r1.21
--- ws-policy-framework.xml 9 Aug 2006 06:06:33 -0000 1.20
+++ ws-policy-framework.xml 9 Aug 2006 23:16:09 -0000 1.21
@@ -77,7 +77,7 @@
<p>&framework.title; provides a flexible and extensible
language for expressing the capabilities, requirements, and
- general characteristics of entities in an XML Web
+ general characteristics of entities in a Web
services-based system. &framework.title; defines a framework and a
model for the expression of these properties as
policies.</p>
@@ -1535,6 +1535,15 @@
from the Austin F2F.
</td>
</tr>
+ <tr>
+ <td>20060809</td>
+ <td>ASV</td>
+ <td>Implemented the
+ <loc href="http://www.w3.org/2006/08/09-ws-policy-minutes.html#action08">resolution</loc>
+ for issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3563">3563</loc>.
+ </td>
+ </tr>
</tbody>
</table>
</inform-div1>
Index: ws-policy-framework.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- ws-policy-framework.html 9 Aug 2006 06:06:33 -0000 1.16
+++ ws-policy-framework.html 9 Aug 2006 23:16:09 -0000 1.17
@@ -80,7 +80,7 @@
<p>Web Services Policy 1.5 - Framework provides a flexible and extensible
language for expressing the capabilities, requirements, and
- general characteristics of entities in an XML Web
+ general characteristics of entities in a Web
services-based system. Web Services Policy 1.5 - Framework defines a framework and a
model for the expression of these properties as
policies.</p>
@@ -1520,6 +1520,15 @@
from the Austin F2F.
</td>
</tr>
+ <tr>
+ <td rowspan="1" colspan="1">20060809</td>
+ <td rowspan="1" colspan="1">ASV</td>
+ <td rowspan="1" colspan="1">Implemented the
+ <a href="http://www.w3.org/2006/08/09-ws-policy-minutes.html#action08">resolution</a>
+ for issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3563">3563</a>.
+ </td>
+ </tr>
</tbody>
</table><br>
</div>
Index: ws-policy-attachment.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -d -r1.21 -r1.22
--- ws-policy-attachment.xml 9 Aug 2006 20:55:57 -0000 1.21
+++ ws-policy-attachment.xml 9 Aug 2006 23:16:09 -0000 1.22
@@ -80,7 +80,8 @@
<p>
The &framework.title; [<bibref ref='WS-Policy'/>]
specification defines an abstract model and an XML-based
- language for policies. This specification, &attachment.title;,
+ language for expressing policies of entities in a Web services-based system.
+ This specification, &attachment.title;,
defines two general-purpose mechanisms for associating
policies with the subjects to which they apply; the policies
may be defined as part of existing metadata about the subject
@@ -91,18 +92,10 @@
To enable Web Services Policy to be used with existing Web
service technologies, this specification describes the use of
these general-purpose mechanisms with WSDL [<bibref
- ref="WSDL11" />] and UDDI [<bibref
+ ref="WSDL11" />] definitions and UDDI [<bibref
ref="UDDIAPI20" />, <bibref ref="UDDIDataStructure20" />,
<bibref ref="UDDI30" />]. WSDL [<bibref ref="WSDL20" />] is
- deferred. Specifically, this specification
- defines the following:
- </p>
-
- <ulist>
- <item><p>How to reference policies from WSDL definitions.</p></item>
- <item><p>How to associate policies with deployed Web service endpoints.</p></item>
- <item><p>How to associate policies with UDDI entities.</p></item>
- </ulist>
+ deferred.</p>
</div1>
<div1 id='NotationsTerminology'>
<head>Notations and Terminology</head>
@@ -979,34 +972,6 @@
</example>
</div3>
</div2>
-<div2 id='ExternalAttachmentDeployedEndpoints'>
- <head>External Attachment to Deployed Endpoints</head>
-
-<p>This section defines a <emph>domain expression</emph> based on Web
-Services Addressing [<bibref ref='WS-Addressing'/>] to allow the use
-of the <el>wsp:PolicyAttachment</el> mechanism to reference a specific
-endpoint of a deployed Web service.</p>
-
-<p>The following schema outline illustrates this extension:</p>
-<eg xml:space="preserve"><wsp:PolicyAttachment>
- <wsp:AppliesTo>
- <wsa:EndpointReference>… </wsa:EndpointReference>
- </wsp:AppliesTo>
- ( <wsp:Policy>…</wsp:Policy>
- | <wsp:PolicyReference>…</wsp:PolicyReference>
- ) +
-</wsp:PolicyAttachment></eg>
-
-<p>An example of an Endpoint Reference is given at the end of Section
-<specref ref='ExternalPolicyAttachment'/> to illustrate the
-extensibility of the <el>wsp:AppliesTo</el> element. </p>
-
-<p>Use of this domain expression is equivalent to <termref def='policy_attachment'>policy attachment</termref> to
-a deployed endpoint in WSDL, using the <el>wsdl11:port</el> element,
-i.e., the <termref def='effective_policy'>effective policy</termref> resulting from the combination of <termref def='policy'>policies</termref>
-declared should be considered a part of the endpoint policy scope.</p>
-
-</div2>
</div1>
<div1 id='AttachingPoliciesUsingUDDI'>
<head>Attaching Policies Using UDDI</head>
@@ -1896,8 +1861,17 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3546">3546</loc>: wsdl 2.0 status mention.
</td>
</tr>
-
-
+ <tr>
+ <td>20060809</td>
+ <td>ASV</td>
+ <td>Implemented the
+ <loc href="http://www.w3.org/2006/08/09-ws-policy-minutes.html#action06">resolution</loc>
+ for issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3556">3556</loc>
+ and the <loc href="http://www.w3.org/2006/08/09-ws-policy-minutes.html#action07">resolution</loc>
+ for issue <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3558">3558</loc>.
+ </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.25
retrieving revision 1.26
diff -u -d -r1.25 -r1.26
--- ws-policy-attachment.html 9 Aug 2006 20:55:57 -0000 1.25
+++ ws-policy-attachment.html 9 Aug 2006 23:16:09 -0000 1.26
@@ -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>
@@ -74,8 +74,8 @@
<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="#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">
+<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></p>
+<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>
@@ -83,7 +83,8 @@
<p>
The Web Services Policy 1.5 - Framework [<cite><a href="#WS-Policy">Web Services Policy Framework</a></cite>]
specification defines an abstract model and an XML-based
- language for policies. This specification, Web Services Policy 1.5 - Attachment,
+ language for expressing policies of entities in a Web services-based system.
+ This specification, Web Services Policy 1.5 - Attachment,
defines two general-purpose mechanisms for associating
policies with the subjects to which they apply; the policies
may be defined as part of existing metadata about the subject
@@ -93,17 +94,9 @@
<p>
To enable Web Services Policy to be used with existing Web
service technologies, this specification describes the use of
- these general-purpose mechanisms with WSDL [<cite><a href="#WSDL11">WSDL 1.1</a></cite>] and UDDI [<cite><a href="#UDDIAPI20">UDDI API 2.0</a></cite>, <cite><a href="#UDDIDataStructure20">UDDI Data Structure 2.0</a></cite>,
+ these general-purpose mechanisms with WSDL [<cite><a href="#WSDL11">WSDL 1.1</a></cite>] definitions and UDDI [<cite><a href="#UDDIAPI20">UDDI API 2.0</a></cite>, <cite><a href="#UDDIDataStructure20">UDDI Data Structure 2.0</a></cite>,
<cite><a href="#UDDI30">UDDI 3.0</a></cite>]. WSDL [<cite><a href="#WSDL20">WSDL 2.0 Core Language</a></cite>] is
- deferred. Specifically, this specification
- defines the following:
- </p>
-
- <ul>
- <li><p>How to reference policies from WSDL definitions.</p></li>
- <li><p>How to associate policies with deployed Web service endpoints.</p></li>
- <li><p>How to associate policies with UDDI entities.</p></li>
- </ul>
+ deferred.</p>
</div>
<div class="div1">
@@ -279,32 +272,32 @@
<p>We introduce the following terms that are used throughout this document:</p>
<p>EdNote: script will insert termdefs here</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>
</div>
@@ -322,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"
@@ -337,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"
@@ -417,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="policy subject" href="#policy_subject">policy subject</a>, is the
combination of relevant policies. The relevant policies are those
attached to <a title="policy scope" href="#policy_scope">policy scopes</a> that
contain the <a title="policy subject" href="#policy_subject">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="policy expression" href="#policy_expression">policy expression</a>, replacing their
<code class="elt">wsp:Policy</code> element with a
@@ -479,7 +472,7 @@
to form a single element <a title="policy expression" href="#policy_expression">policy expression</a>.
The resultant <a title="policy" href="#policy">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="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>
@@ -499,7 +492,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"
@@ -721,7 +714,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.
@@ -890,7 +883,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"
@@ -957,7 +950,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"
@@ -973,35 +966,6 @@
</div>
</div>
</div>
-<div class="div2">
-
-<h3><a name="ExternalAttachmentDeployedEndpoints"></a>4.2 External Attachment to Deployed Endpoints</h3>
-
-<p>This section defines a <em>domain expression</em> based on Web
-Services Addressing [<cite><a href="#WS-Addressing">WS-Addressing Core</a></cite>] to allow the use
-of the <code class="elt">wsp:PolicyAttachment</code> mechanism to reference a specific
-endpoint of a deployed Web service.</p>
-
-<p>The following schema outline illustrates this extension:</p>
-<div class="exampleInner"><pre><wsp:PolicyAttachment>
- <wsp:AppliesTo>
- <wsa:EndpointReference>… </wsa:EndpointReference>
- </wsp:AppliesTo>
- ( <wsp:Policy>…</wsp:Policy>
- | <wsp:PolicyReference>…</wsp:PolicyReference>
- ) +
-</wsp:PolicyAttachment></pre></div>
-
-<p>An example of an Endpoint Reference is given at the end of Section
-<a href="#ExternalPolicyAttachment"><b>3.4 External Policy Attachment</b></a> to illustrate the
-extensibility of the <code class="elt">wsp:AppliesTo</code> element. </p>
-
-<p>Use of this domain expression is equivalent to <a title="policy attachment" href="#policy_attachment">policy attachment</a> to
-a deployed endpoint in WSDL, using the <code class="elt">wsdl11:port</code> element,
-i.e., the <a title="effective policy" href="#effective_policy">effective policy</a> resulting from the combination of <a title="policy" href="#policy">policies</a>
-declared should be considered a part of the endpoint policy scope.</p>
-
-</div>
</div>
<div class="div1">
@@ -1881,8 +1845,17 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3546">3546</a>: wsdl 2.0 status mention.
</td>
</tr>
-
-
+ <tr>
+ <td rowspan="1" colspan="1">20060809</td>
+ <td rowspan="1" colspan="1">ASV</td>
+ <td rowspan="1" colspan="1">Implemented the
+ <a href="http://www.w3.org/2006/08/09-ws-policy-minutes.html#action06">resolution</a>
+ for issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3556">3556</a>
+ and the <a href="http://www.w3.org/2006/08/09-ws-policy-minutes.html#action07">resolution</a>
+ for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3558">3558</a>.
+ </td>
+ </tr>
</tbody>
</table><br>
</div>
Received on Wednesday, 9 August 2006 23:16:23 UTC