- From: Toufic Boubez via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 22 Aug 2006 20:32:13 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv30537
Modified Files:
ws-policy-primer.html ws-policy-framework.xml
ws-policy-framework.html ws-policy-attachment.html
Log Message:
Changed wording of Introduction section after consultation with Dale Moberg. Action assiged to editors:
http://www.w3.org/2006/08/16-ws-policy-minutes.html#action05
Index: ws-policy-framework.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.xml,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -d -r1.24 -r1.25
--- ws-policy-framework.xml 19 Aug 2006 01:15:46 -0000 1.24
+++ ws-policy-framework.xml 22 Aug 2006 20:32:10 -0000 1.25
@@ -75,12 +75,10 @@
<div1 id="tocRange">
<head>Introduction</head>
- <p>&framework.title; provides a flexible and extensible
- language for expressing the capabilities, requirements, and
- 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>
+ <p>&framework.title; defines a framework and a model for expressing policies that
+ refer to domain-specific capabilities, requirements, and general characteristics of
+ entities in a Web services-based system.
+ </p>
<p><termdef id='policy' term='policy'>A <term>policy</term> is a collection of
<termref def='policy_alternative'>policy alternatives</termref>, </termdef>
@@ -1598,6 +1596,15 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3560">3560</loc>.
</td>
</tr>
+ <tr>
+ <td>20060822</td>
+ <td>TIB</td>
+ <td>Completed action item:
+ <loc href="http://www.w3.org/2006/08/16-ws-policy-minutes.html#action05">resolution</loc>
+ for issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3565">3565</loc>.
+ </td>
+ </tr>
</tbody>
</table>
</inform-div1>
Index: ws-policy-primer.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- ws-policy-primer.html 17 Aug 2006 15:53:12 -0000 1.4
+++ ws-policy-primer.html 22 Aug 2006 20:32:10 -0000 1.5
@@ -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 - Primer</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 type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/base.css"><link href="#contents" rel="contents"></head><body>
+</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"><link rel="contents" href="#contents"></head><body>
<div class="head">
<h1>Web Services Policy 1.5 - Primer</h1>
<h2>Editors' copy $Date$ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
@@ -72,7 +72,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="#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-1-policy-expression">Advanced Concepts I: 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>4. <a href="#advanced-concepts-2-policy-assertion-design">Advanced Concepts II: Policy Assertion Desin</a><br> 4.1 <a href="#role-of-policy-assertions">Role of Policy Assertions</a><br> 4.2 <a href="#parts-of-a-policy-assertion">Parts of a Policy Assertion</a><br> 4.3 <a href="#when-to-design-policy-assertions">When to design policy assertions?</a><br> 4.3.1 <a href="#opt-in-behavior">Opt-in behavior</a><br> 4.3.2 <a href="#shared-behavior">Shared behavior</a><br> 4.3.3 <a href="#visible-behavior">Visible behavior</a><br> 4.4 <a href="#guidelines-for-designing-assertions">Guidelines for Designing Assertions</a><br> 4.4.1 <a href="#optional-behaviors">Optional Behaviors</a><br> 4.4.2 <a href="#assertion-vs-assertion-parameter">Assertion vs. assertion parameter</a><br> &bsp; 4.4.3 <a href="#leveraging-nested-policy">Leveraging Nested Policy</a><br> 4.4.4 <a href="#minimal-approach">Minimal approach</a><br> 4.4.5 <a href="#QName_and_XML_Information_Set_representation">QName and XML Information Set representation</a><br> 4.4.6 <a href="#Policy_subject_and_attachment_points">Policy subject and attachment points</a><br> 4.4.7 <a href="#versioning-behaviors">Versioning behaviors</a><br> 4.5 <a href="#describing-policy-assertions">Describing Policy Assertions</a><br>5. <a href="#conclusion">Conclusion</a><br></p>
-<h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#security-considerations">Security Considerations</a><br> A.1 <a href="#information-disclosure-threats">Information Disclosure Threats</a><br> A.2 <a href="#spoofing-and-tampering-threats">Spoofing and Tampering Threats</a><br> A.3 <a href="#downgrade-threats">Downgrade Threats</a><br> A.4 <a href="#repudiation-threats">Repudiation Threats</a><br> A.5 <a href="#denial-of-service-threats">Denial of Service Threats</a><br> A.6 <a href="#general-xml-considerations">General XML 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 Plicy 1.5 - Primer Change Log</a> (Non-Normative)<br></p></div><hr><div class="body">
+<h3><a name="appendix" id="appendix">Appendices</a></h3><p class="toc">A. <a href="#security-considerations">Security Considerations</a><br> A.1 <a href="#information-disclosure-threats">Information Disclosure Threats</a><br> A.2 <a href="#spoofing-and-tampering-threats">Spoofing and Tampering Threats</a><br> A.3 <a href="#downgrade-threats">Downgrade Threats</a><br> A.4 <a href="#repudiation-threats">Repudiation Threats</a><br> A.5 <a href="#denial-of-service-threats">Denial of Service Threats</a><br> A.6 <a href="#general-xml-considerations">General XML 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 Plicy 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>
@@ -167,7 +167,7 @@
<h3><a name="simple-message"></a>2.2 Simple Message</h3>
<p>Let us start by considering a SOAP Message in the example below.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 2-1. </span>SOAP Message</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 2-1. </span>SOAP Message</i></p>
<div class="exampleInner"><pre><soap:Envelope>
<soap:Header>
<wsa:To>http://stock.contoso.com/realquote</wsa:To>
@@ -207,7 +207,7 @@
<p>How does Contoso use policy to represent the use of addressing? The example below
illustrates a policy expression that requires the use of addressing.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 2-2. </span>Policy Expression</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 2-2. </span>Policy Expression</i></p>
<div class="exampleInner"><pre><Policy>
<wsap:UsingAddressing />
</Policy></pre></div>
@@ -235,7 +235,7 @@
<p>In addition to requiring the use of addressing, Contoso requires the use of
transport-level security for protecting messages.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 2-3. </span>Secure Message</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 2-3. </span>Secure Message</i></p>
<div class="exampleInner"><pre><soap:Envelope>
<soap:Header>
<wss:Security soap:mustUnderstand="1" >
@@ -259,7 +259,7 @@
using a policy expression. The example below illustrates a policy expression that requires
the use of addressing and transport-level security for securing messages.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 2-4. </span>Addressing and Security Policy Expression</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 2-4. </span>Addressing and Security Policy Expression</i></p>
<div class="exampleInner"><pre><Policy>
<wsap:UsingAddressing />
<sp:TransportBinding>...</sp:TransportBinding>
@@ -349,7 +349,7 @@
policy assertions using the <code>Policy</code> or <code>All</code> operator means that
all the behaviors represented by these assertions are required.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 2-5. </span>Addressing and Security Policy Expression</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 2-5. </span>Addressing and Security Policy Expression</i></p>
<div class="exampleInner"><pre><All>
<wsap:UsingAddressing />
<sp:TransportBinding>…</sp:TransportBinding>
@@ -361,7 +361,7 @@
message-level security for protecting messages, Contoso uses the
<code>sp:AsymmetricBinding</code> policy assertion (see the example below).</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 2-6. </span>Asymmetric Binding Security Policy Assertion</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 2-6. </span>Asymmetric Binding Security Policy Assertion</i></p>
<div class="exampleInner"><pre><sp:AsymmetricBinding>…</sp:AsymmetricBinding></pre></div>
</div>
<p>The <code>sp:AsymmetricBinding</code> element is a policy assertion. (The prefix
@@ -376,7 +376,7 @@
the assertions. The policy expression in the example below requires the use of either
transport- or message-level security for protecting messages.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 2-7. </span>Transport- or Message-Level Security Policy Expression</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 2-7. </span>Transport- or Message-Level Security Policy Expression</i></p>
<div class="exampleInner"><pre><ExactlyOne>
<sp:TransportBinding>…</sp:TransportBinding>
<sp:AsymmetricBinding>…</sp:AsymmetricBinding>
@@ -389,7 +389,7 @@
policy expression in the example below requires the use of addressing and one of
transport- or message-level security for protecting messages.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 2-8. </span>Addressing and Transport- OR Message-Level Security Policy Expression</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 2-8. </span>Addressing and Transport- OR Message-Level Security Policy Expression</i></p>
<div class="exampleInner"><pre><All>
<wsap:UsingAddressing />
<ExactlyOne>
@@ -412,7 +412,7 @@
<p>To indicate the use of optimization using the Optimized MIME Serialization, Contoso uses
the <code>mtom:OptimizedMimeSerialization</code> policy assertion (see the example below).</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 2-9. </span>Optimized MIME Serialization Policy Assertion</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 2-9. </span>Optimized MIME Serialization Policy Assertion</i></p>
<div class="exampleInner"><pre><mtom:OptimizedMimeSerialization /></pre></div>
</div>
<p>The <code>mtom:OptimizedMimeSerialization</code> element is a policy assertion. (The
@@ -432,7 +432,7 @@
optional. This policy expression allows the use of optimization and requires the use of
addressing and one of transport- or message-level security.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 2-10. </span>Optional MIME Serialization, Addressing and Transport- OR Message-Level Security
+ <p style="text-align: left" class="exampleHead"><i><span>Example 2-10. </span>Optional MIME Serialization, Addressing and Transport- OR Message-Level Security
Policy Expression</i></p>
<div class="exampleInner"><pre><All>
<mtom:OptimizedMimeSerialization wsp:Optional="true"/>
@@ -479,7 +479,7 @@
behavior of the <code>sp:TransportBinding</code> policy assertion (which already requires
the use of transport-level security for protecting messages).</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 2-11. </span>Transport Security Policy Assertion</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 2-11. </span>Transport Security Policy Assertion</i></p>
<div class="exampleInner"><pre><sp:TransportBinding>
<Policy>
<sp:TransportToken>
@@ -526,7 +526,7 @@
<code>PolicyReference</code> element can be used to reference a policy expression
identified using either of these mechanisms.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 2-12. </span>Common Policy Expression</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 2-12. </span>Common Policy Expression</i></p>
<div class="exampleInner"><pre><Policy wsu:Id=”common”>
<mtom:OptimizedMimeSerialization wsp:Optional="true"/>
<wsap:UsingAddressing />
@@ -544,7 +544,7 @@
expression as a standalone policy or within another policy expression. The example below
is a policy expression that re-uses the common policy expression above.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 2-13. </span>PolicyReference to Common Policy Expression</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 2-13. </span>PolicyReference to Common Policy Expression</i></p>
<div class="exampleInner"><pre><PolicyReference URI="#common"/></pre></div>
</div>
<p>For referencing a policy expression within the same XML document, Contoso uses the
@@ -555,7 +555,7 @@
transport- or message-level security for protecting messages and allows the use of
optimization.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 2-14. </span>Secure Policy Expression</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 2-14. </span>Secure Policy Expression</i></p>
<div class="exampleInner"><pre><Policy wsu:Id=”secure”>
<All>
<PolicyReference URI="#common"/>
@@ -574,7 +574,7 @@
attribute identifies the policy expression. The URI of this policy expression is
<code>http://real.contoso.com/policy/common</code>.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 2-15. </span>Common Policy Expression</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 2-15. </span>Common Policy Expression</i></p>
<div class="exampleInner"><pre><Policy Name=”http://real.contoso.com/policy/common”>
<mtom:OptimizedMimeSerialization wsp:Optional="true"/>
<wsap:UsingAddressing />
@@ -582,7 +582,7 @@
</div>
<p>The example below is a policy expression that re-uses the common policy expression above.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 2-16. </span>PolicyReference to Common Policy Expression</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 2-16. </span>PolicyReference to Common Policy Expression</i></p>
<div class="exampleInner"><pre><PolicyReference URI="http://real.contoso.com/policy/common"/></pre></div>
</div>
</div>
@@ -604,7 +604,7 @@
description. This includes all the message exchanges described by operations in the
<code>RealTimeDataInterface</code>.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 2-17. </span>Secure Policy Expression Attached to WSDL Binding</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 2-17. </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>
@@ -619,7 +619,7 @@
security for these services, but requires the use of addressing and allows the use of
optimization.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 2-18. </span>Open Policy Expression Attached to WSDL Binding</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 2-18. </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>
@@ -713,7 +713,7 @@
<p>Let us take a closer look at Contoso’s policy expression (see below) from the previous
section.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 3-1. </span>Contoso’s Secure Policy Expression</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 3-1. </span>Contoso’s Secure Policy Expression</i></p>
<div class="exampleInner"><pre><Policy>
<All>
<mtom:OptimizedMimeSerialization wsp:Optional="true"/>
@@ -741,7 +741,7 @@
<p>The normal form uses a subset of constructs used in the compact form and follows a simple
outline for its XML representation:</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 3-2. </span>Normal Form for Policy Expressions</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 3-2. </span>Normal Form for Policy Expressions</i></p>
<div class="exampleInner"><pre><Policy>
<ExactlyOne>
<All>
@@ -770,7 +770,7 @@
policy alternatives: one that requires the use of transport-level security and the other
that requires the use of message-level security for protecting messages.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 3-3. </span>Transport- or Message-Level Security Policy Expression in Normal Form</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 3-3. </span>Transport- or Message-Level Security Policy Expression in Normal Form</i></p>
<div class="exampleInner"><pre><Policy>
<ExactlyOne>
<All>
@@ -803,7 +803,7 @@
</li>
</ol>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 3-4. </span>Contoso’s Secure Policy Expression in Compact Form</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 3-4. </span>Contoso’s Secure Policy Expression in Compact Form</i></p>
<div class="exampleInner"><pre><Policy wsu:Id=”secure”>
<All>
<PolicyReference URI=”#common”/>
@@ -826,7 +826,7 @@
four policy alternatives in the normal form. These alternatives map to bullets (a) through
(d) above.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 3-5. </span>Contoso’s Policy Expression in Normal Form</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 3-5. </span>Contoso’s Policy Expression in Normal Form</i></p>
<div class="exampleInner"><pre><Policy>
<ExactlyOne>
<All> <!-- - - - - - - - - - - - - - Policy Alternative (a) -->
@@ -899,7 +899,7 @@
requirements or conditions for an interaction. In simple words, each policy alternative
represents a set of conditions for an interaction. The diagram below describes the policy
data model.</p>
- <div style="text-align: center" class="figure"><br><img src="ws-policy-data-model.jpg" alt="WS-Policy Data Model"><p style="text-align:left"><i><span>Figure 3-1. </span>WS-Policy Data Model</i></p><br></div>
+ <div class="figure" style="text-align: center"><br><img src="ws-policy-data-model.jpg" alt="WS-Policy Data Model"><p style="text-align:left"><i><span>Figure 3-1. </span>WS-Policy Data Model</i></p><br></div>
<p>A policy-aware client uses a policy to determine whether one of these policy alternatives
(i.e. the conditions for an interaction) can be met in order to interact with the
associated Web Service. Such clients may choose any of these policy alternatives and must
@@ -953,7 +953,7 @@
</ul>
<p>The diagram below describes this mapping from the normal form of a policy expression to
the policy data model.</p>
- <div style="text-align: center" class="figure"><br><img src="normal-form-2-data-model.jpg" alt="Mapping from Normal Form to Policy Data Model"><p style="text-align:left"><i><span>Figure 3-2. </span>Mapping from Normal Form to Policy Data Model</i></p><br></div>
+ <div class="figure" style="text-align: center"><br><img src="normal-form-2-data-model.jpg" alt="Mapping from Normal Form to Policy Data Model"><p style="text-align:left"><i><span>Figure 3-2. </span>Mapping from Normal Form to Policy Data Model</i></p><br></div>
</div>
<div class="div2">
@@ -967,7 +967,7 @@
policy alternatives. Of them, one of the policy alternatives requires the use of
addressing and transport-level security.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 3-6. </span>Contoso’s Policy Expression</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 3-6. </span>Contoso’s Policy Expression</i></p>
<div class="exampleInner"><pre><Policy>
<ExactlyOne>
<All> <!-- - - - - - - - - - Contoso’s Policy Alternative (a) -->
@@ -986,7 +986,7 @@
contains one policy alternative that requires the use of addressing and transport-level
security.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 3-7. </span>Tony’s Policy Expression in Normal Form</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 3-7. </span>Tony’s Policy Expression in Normal Form</i></p>
<div class="exampleInner"><pre><Policy>
<ExactlyOne>
<All> <!-- - - - - - - - - - - - - - Tony’s Policy Alternative -->
@@ -1039,7 +1039,7 @@
subjects: message, operation, endpoint and service. When attached, capabilities and
requirements represented by a policy expression apply to a message exchange or message
associated with (or described by) a policy subject.</p>
- <div style="text-align: center" class="figure"><br><img src="policy-subjects-in-wsdl.jpg" alt="Policy Subjects and Effective Policy in WSDL"><p style="text-align:left"><i><span>Figure 3-3. </span>Policy Subjects and Effective Policy in WSDL</i></p><br></div>
+ <div class="figure" style="text-align: center"><br><img src="policy-subjects-in-wsdl.jpg" alt="Policy Subjects and Effective Policy in WSDL"><p style="text-align:left"><i><span>Figure 3-3. </span>Policy Subjects and Effective Policy in WSDL</i></p><br></div>
<p>The WSDL <code>service</code> element represents the service policy subject. Policy
expressions associated with a service policy subject apply to any message exchange using
any of the endpoints offered by that service.</p>
@@ -1060,7 +1060,7 @@
that message.</p>
<p>In the example below, the policy expression is attached to an endpoint policy subject.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 3-8. </span>Contoso’s Policy Expression Attached to WSDL binding Element</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 3-8. </span>Contoso’s Policy Expression Attached to WSDL binding Element</i></p>
<div class="exampleInner"><pre><wsdl:binding name="SecureBinding" type="tns:RealTimeDataInterface" >
<PolicyReference URI="#secure" />
<wsdl:operation name="GetRealQuote">…</wsdl:operation>
@@ -1108,7 +1108,7 @@
attached to the <code>SecureBinding</code> WSDL binding and<code>RealTimeDataPort</code>
WSDL port descriptions.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 3-9. </span>Multiple Policy Expressions Attached to Endpoint Policy Subject </i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 3-9. </span>Multiple Policy Expressions Attached to Endpoint Policy Subject </i></p>
<div class="exampleInner"><pre><Policy wsu:Id=”common2”>
<mtom:OptimizedMimeSerialization wsp:Optional="true"/>
<wsap:UsingAddressing />
@@ -1153,7 +1153,7 @@
words, the combination of two policies is the cross product of alternatives in these two
policies.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 3-10. </span>Effective Policy of the Endpoint Policy Subject in the Previous Example</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 3-10. </span>Effective Policy of the Endpoint Policy Subject in the Previous Example</i></p>
<div class="exampleInner"><pre><Policy>
<All>
<Policy>
@@ -1194,7 +1194,7 @@
<p>The example below represents a Contoso version 1 policy expression. This expression
requires the use of addressing and transport-level security for protecting messages. </p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 3-11. </span>Contoso’s Version 1 Policy Expression</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 3-11. </span>Contoso’s Version 1 Policy Expression</i></p>
<div class="exampleInner"><pre><Policy>
<ExactlyOne>
<All>
@@ -1214,7 +1214,7 @@
clients have the option to migrate from using old policy alternatives to new policy
alternatives.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 3-12. </span>Contoso’s Version 2 Policy Expression</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 3-12. </span>Contoso’s Version 2 Policy Expression</i></p>
<div class="exampleInner"><pre><Policy>
<ExactlyOne>
<All>
@@ -1307,7 +1307,7 @@
<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.
This assertion illustrates the use of assertion parameters and nested policy.</p>
- <div style="text-align: center" class="figure"><br><img src="policy-assertion.jpg" alt="sp:IssuedToken Policy Assertion"><p style="text-align:left"><i><span>Figure 4-1. </span>sp:IssuedToken Policy Assertion</i></p><br></div>
+ <div class="figure" style="text-align: center"><br><img src="policy-assertion.jpg" alt="sp:IssuedToken Policy Assertion"><p style="text-align:left"><i><span>Figure 4-1. </span>sp:IssuedToken Policy Assertion</i></p><br></div>
<p>The <code>sp:IssuedToken</code> element is a policy assertion that identifies the use of
a security token – such as SAML token - issued by a third party for protecting messages. A
policy assertion is an XML element. The QName of this element represents the behavior
@@ -1490,7 +1490,7 @@
additional useful information for engaging the behavior that is irrelevant to
compatibility tests.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 4-1. </span>Policy Assertion with Assertion Parameters</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 4-1. </span>Policy Assertion with Assertion Parameters</i></p>
<div class="exampleInner"><pre><Policy>
<sp:SignedParts>
<sp:Body />
@@ -1606,7 +1606,7 @@
Such equivalent behaviors can be modeled as independent assertions. The policy
expression in the example below requires the use of WSS: SOAP Message Security 1.0.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 4-2. </span>Message-level Security and WSS: SOAP Message Security 1.0</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 4-2. </span>Message-level Security and WSS: SOAP Message Security 1.0</i></p>
<div class="exampleInner"><pre><Policy>
<sp:Wss10>…</sp:Wss10>
</Policy></pre></div>
@@ -1615,7 +1615,7 @@
Security 1.1. These are multiple equivalent behaviors and are represented using distinct
policy assertions.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 4-3. </span>Message-level Security and WSS: SOAP Message Security 1.1</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 4-3. </span>Message-level Security and WSS: SOAP Message Security 1.1</i></p>
<div class="exampleInner"><pre><Policy>
<sp:Wss11>…</sp:Wss11>
</Policy></pre></div>
@@ -1728,7 +1728,7 @@
policy alternatives, number of assertions in an alternative, depth of nested policy
expressions, etc.</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example A-1. </span>Chained Policy Reference Elements</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example A-1. </span>Chained Policy Reference Elements</i></p>
<div class="exampleInner"><pre><Policy wsu:Id="p1">
<PolicyReference URI="#p2"/ >
<PolicyReference URI="#p2"/>
Index: ws-policy-framework.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -d -r1.21 -r1.22
--- ws-policy-framework.html 19 Aug 2006 01:15:46 -0000 1.21
+++ ws-policy-framework.html 22 Aug 2006 20:32:10 -0000 1.22
@@ -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 - Framework</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 type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/base.css"><link href="#contents" rel="contents"></head><body>
+</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"><link rel="contents" href="#contents"></head><body>
<div class="head">
<h1>Web Services Policy 1.5 - Framework</h1>
<h2>Editors' copy $Date$ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
@@ -73,23 +73,21 @@
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> 1.1 <a href="#Goals">Goals</a><br> 1.2 <a href="#Example">Example</a><br>2. <a href="#Notation_Terminilogy">Notations and Terminology</a><br> 2.1 <a href="#Notational_Conventions">Notational Conventions</a><br> 2.2 <a href="#Extensibility">Extensibility</a><br> 2.3 <a href="#XML_Namespaces">XML Namespaces</a><br> 2.4 <a href="#Terminology">Terminology</a><br>3. <a href="#Policy_Model">Policy Model</a><br> 3.1 <a href="#rPolicy_Assertion">Policy Assertion</a><br> 3.2 <a href="#rPolicy_Alternative">Policy Alternative</a><br> 3.3 <a href="#rPolicy">Policy</a><br> 3.4 <a href="#Web_services">Web services</a><br>4. <a href="#rPolicy_Expression">Policy Expression</a><br> &nbs; 4.1 <a href="#Normal_Form_Policy_Expression">Normal Form Policy Expression</a><br> 4.2 <a href="#Policy_Identification">Policy Identification</a><br> 4.3 <a href="#Compact_Policy_Expression">Compact Policy Expression</a><br> 4.3.1 <a href="#Optional_Policy_Assertions">Optional Policy Assertions</a><br> 4.3.2 <a href="#Policy_Assertion_Nesting">Policy Assertion Nesting</a><br> 4.3.3 <a href="#Policy_Operators">Policy Operators</a><br> 4.3.4 <a href="#Policy_Inclusion">Policy Inclusion</a><br> 4.4 <a href="#Policy_Intersection">Policy Intersection</a><br>5. <a href="#Security_Considerations">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="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>C. <a href="#change-description">Changes in this Version of the Document</a> (Non-Normative)<br>D. <a href="#change-log">Web Services Policy 1.5 - Framework Change Log</a> (Non-Normative)<br></p></div><hr><div class="body">
+<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="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>C. <a href="#change-description">Changes in this Version of the Document</a> (Non-Normative)<br>D. <a href="#change-log">Web Services Policy 1.5 - Framework Change Log</a> (Non-Normative)<br></p></div><hr><div class="body">
<div class="div1">
<h2><a name="tocRange"></a>1. Introduction</h2>
- <p>Web Services Policy 1.5 - Framework provides a flexible and extensible
- language for expressing the capabilities, requirements, and
- 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>
+ <p>Web Services Policy 1.5 - Framework defines a framework and a model for expressing policies that
+ refer to domain-specific capabilities, requirements, and general characteristics of
+ entities in a Web services-based system.
+ </p>
- <p>[<a title="policy" name="policy">Definition</a>: A <b>policy</b> is a collection of
+ <p>[<a name="policy" title="policy">Definition</a>: A <b>policy</b> is a collection of
<a title="policy alternative" href="#policy_alternative">policy alternatives</a>, ]
- where [<a title="policy alternative" name="policy_alternative">Definition</a>: a <b>policy alternative</b>
+ where [<a name="policy_alternative" title="policy alternative">Definition</a>: a <b>policy alternative</b>
is a collection of <a title="policy assertion" href="#policy_assertion">policy assertions</a>.]
- [<a title="policy assertion" name="policy_assertion">Definition</a>: A <b>policy assertion</b>
+ [<a name="policy_assertion" title="policy assertion">Definition</a>: A <b>policy assertion</b>
represents an individual requirement, capability, or other property of a behavior.]
Some policy assertions
specify traditional requirements and capabilities that
@@ -103,12 +101,12 @@
<p>Web Services Policy 1.5 - Framework does not specify policy discovery or
<a title="policy attachment" href="#policy_attachment">policy attachment</a>.
- [<a title="policy attachment" name="policy_attachment">Definition</a>: A
+ [<a name="policy_attachment" title="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>.]
- [<a title="policy scope" name="policy_scope">Definition</a>: A <b>policy scope</b> is a collection of
+ [<a name="policy_scope" title="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.]
- [<a title="policy subject" name="policy_subject">Definition</a>: A <b>policy subject</b> is an entity
+ [<a name="policy_subject" title="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. ]
@@ -134,7 +132,7 @@
<p>
An XML Infoset called a <a title="policy expression" href="#policy_expression">policy
expression</a> that contains domain-specific, Web
- Service policy information. [<a title="policy expression" name="policy_expression">Definition</a>: A <b>policy expression</b>
+ Service policy information. [<a name="policy_expression" title="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></li>
@@ -155,7 +153,7 @@
assertions defined in WS-SecurityPolicy [<cite><a href="#WS-SecurityPolicy">WS-SecurityPolicy</a></cite>]:</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><i><span>Example 1-1. </span>Use of Web Services Policy with security policy assertions.</i></p>
+ <p style="text-align: left" class="exampleHead"><i><span>Example 1-1. </span>Use of Web Services Policy with security policy assertions.</i></p>
<div class="exampleInner"><pre>
(01) <wsp:Policy
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
@@ -365,7 +363,7 @@
type</a> is identified only by the XML Infoset <strong>[namespace name]</strong> and <strong>[local name]</strong> properties (that
is, the qualified name or QName) of the root Element
Information Item representing the assertion.
- [<a title="policy assertion type" name="policy_assertion_type">Definition</a>: A <b>policy assertion type</b>
+ [<a name="policy_assertion_type" title="policy assertion type">Definition</a>: A <b>policy assertion type</b>
represents a class of <a title="policy assertion" href="#policy_assertion">policy assertions</a> and implies a
schema for the assertion and assertion-specific semantics.]
Assertions of
@@ -385,7 +383,7 @@
<p>The XML Infoset of a <a title="policy assertion" href="#policy_assertion">policy assertion</a> <span class="rfc2119">MAY</span> contain a non-empty <strong>[attributes]</strong> property and/or a non-empty <strong>[children]</strong>
property. Such content <span class="rfc2119">MAY</span> be used to parameterize the
behavior indicated by the assertion.
- [<a title="policy assertion parameter" name="policy_assertion_parameter">Definition</a>: A <b>policy assertion parameter</b>
+ [<a name="policy_assertion_parameter" title="policy assertion parameter">Definition</a>: A <b>policy assertion parameter</b>
qualifies the behavior indicated by a <a title="policy assertion" href="#policy_assertion">policy assertion</a>.]
For example, an
assertion identifying support for a specific reliable
@@ -417,7 +415,7 @@
<p>The vocabulary of a policy alternative is the set of
all <a title="policy assertion type" href="#policy_assertion_type">policy assertion
types</a> within the alternative.
- [<a title="policy vocabulary" name="policy_vocabulary">Definition</a>: A <b>policy vocabulary</b> is the set of all
+ [<a name="policy_vocabulary" title="policy vocabulary">Definition</a>: A <b>policy vocabulary</b> is the set of all
<a title="policy assertion type" href="#policy_assertion_type">policy assertion types</a> used in a policy.]
An assertion whose type
is part of the policy's vocabulary but is not included in
@@ -1583,6 +1581,15 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3560">3560</a>.
</td>
</tr>
+ <tr>
+ <td rowspan="1" colspan="1">20060822</td>
+ <td rowspan="1" colspan="1">TIB</td>
+ <td rowspan="1" colspan="1">Completed action item:
+ <a href="http://www.w3.org/2006/08/16-ws-policy-minutes.html#action05">resolution</a>
+ for issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3565">3565</a>.
+ </td>
+ </tr>
</tbody>
</table><br>
</div>
Index: ws-policy-attachment.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.html,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -d -r1.31 -r1.32
--- ws-policy-attachment.html 19 Aug 2006 01:15:46 -0000 1.31
+++ ws-policy-attachment.html 22 Aug 2006 20:32:10 -0000 1.32
@@ -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 type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/base.css"><link href="#contents" rel="contents"></head><body>
+</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"><link rel="contents" href="#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></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="#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 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">
<div class="div1">
<h2><a name="tocRange"></a>1. Introduction</h2>
@@ -272,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 title="policy" name="policy">Definition</a>: A <b>policy</b> is a
+<p>[<a name="policy" title="policy">Definition</a>: A <b>policy</b> is a
collection of <a title="policy alternative" href="#policy_alternative">policy
alternatives</a>. ]</p>
-<p>[<a title="policy alternative" name="policy_alternative">Definition</a>: A
+<p>[<a name="policy_alternative" title="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 title="policy assertion" name="policy_assertion">Definition</a>: A
+<p>[<a name="policy_assertion" title="policy assertion">Definition</a>: A
<b>policy assertion</b> represents an individual requirement,
capability, or other property of a behavior.]</p>
-<p>[<a title="policy expression" name="policy_expression">Definition</a>: A
+<p>[<a name="policy_expression" title="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 title="policy subject" name="policy_subject">Definition</a>: A <b>policy
+<p>[<a name="policy_subject" title="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 title="policy scope" name="policy_scope">Definition</a>: A <b>policy
+<p>[<a name="policy_scope" title="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 title="policy attachment" name="policy_attachment">Definition</a>: A
+<p>[<a name="policy_attachment" title="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>
@@ -315,7 +315,7 @@
[<cite><a href="#WS-SecurityPolicy">WS-SecurityPolicy</a></cite>].</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><a name="Table2"></a><i><span>Example 2-1. </span>Example RM Policy Expression.</i></p>
+ <p style="text-align: left" class="exampleHead"><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"
@@ -330,7 +330,7 @@
(08) </wsp:Policy></pre></div>
</div>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><a name="Table3"></a><i><span>Example 2-2. </span>Example X509 Security Policy Expression.</i></p>
+ <p style="text-align: left" class="exampleHead"><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"
@@ -410,13 +410,13 @@
subject, and other attachments may be made by UDDI and other
mechanisms.</p>
- <p>When multiple attachments are made, [<a title="effective policy" name="effective_policy">Definition</a>: the
+ <p>When multiple attachments are made, [<a name="effective_policy" title="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 title="merge" name="merge">Definition</a>: a <b>merge</b>
+ <p>This combination can be achieved by: [<a name="merge" title="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
@@ -472,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 title="element policy" name="element_policy">Definition</a>: The
+property. [<a name="element_policy" title="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>
@@ -492,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 class="exampleHead" style="text-align: left"><a name="Table4"></a><i><span>Example 3-1. </span>Example Merged Policy Expression.</i></p>
+ <p style="text-align: left" class="exampleHead"><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"
@@ -712,7 +712,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 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>
+<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>
<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.
@@ -881,7 +881,7 @@
<a href="#Table5">Example 4-1</a> that references policies. </p>
<div class="exampleOuter">
-<p class="exampleHead" style="text-align: left"><a name="Table5"></a><i><span>Example 4-1. </span>Example Policy Attached to WSDL.</i></p>
+<p style="text-align: left" class="exampleHead"><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"
@@ -948,7 +948,7 @@
whose XML 1.0 representation is listed in <a href="#Table6">Example 4-2</a>.</p>
<div class="exampleOuter">
-<p class="exampleHead" style="text-align: left"><a name="Table6"></a><i><span>Example 4-2. </span>Example Message Security Policy Expression.</i></p>
+<p style="text-align: left" class="exampleHead"><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"
Received on Tuesday, 22 August 2006 20:32:27 UTC