- From: Asir Vedamuthu via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 09 Aug 2006 06:06:35 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv4489
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 3543 and the resolution for issue 'Modify wording in Abstract for Framework'. Restored Section 2.2 Extensibility (that was accidentally dropped). Completed action item 17 from the Austin F2F.
Attachment - Implemented the resolution for issue 3543.
Index: ws-policy-framework.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -d -r1.19 -r1.20
--- ws-policy-framework.xml 9 Aug 2006 05:35:41 -0000 1.19
+++ ws-policy-framework.xml 9 Aug 2006 06:06:33 -0000 1.20
@@ -56,9 +56,8 @@
</author>
</authlist>
<abstract>
- <p>The &framework.title; provides a general
- purpose model and corresponding syntax to describe the
- policies of a Web Service.</p>
+ <p>The &framework.title; provides a general purpose model and corresponding
+ syntax to describe the policies of entities in a Web services-based system.</p>
<p>Web Services Policy Framework defines a base set of
constructs that can be used and extended by other Web
services specifications to describe a broad range of service
@@ -121,36 +120,6 @@
ref="UDDIAPI20" />, <bibref ref="UDDIDataStructure20"
/>, <bibref ref="UDDI30" />].</p>
- <p>The following example illustrates a security policy using
- assertions defined in WS-SecurityPolicy [<bibref
- ref="WS-SecurityPolicy"/>]:</p>
-
- <example>
- <head>Use of Web Services Policy with security policy assertions.</head>
- <eg xml:space="preserve">
-(01) <wsp:Policy
- xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
- xmlns:wsp="&nsuri;" >
-(02) <wsp:ExactlyOne>
-(03) <sp:Basic256Rsa15 />
-(04) <sp:TripleDesRsa15 />
-(05) </wsp:ExactlyOne>
-(06) </wsp:Policy>
- </eg>
- </example>
-
- <p>Lines (01-06) represent a
- policy for the algorithm suite required for performing
- cryptographic operations with symmetric or asymmetric
- key-based security tokens.</p>
-
- <p>Lines (02-05) illustrate the <el>ExactlyOne</el> policy
- operator. Policy operators group policy assertions into
- policy alternatives. A valid interpretation of the policy
- above would be that an invocation of a Web service uses
- one of the algorithm suite assertions (Lines 03-04)
- specified.</p>
-
<div2 id="Goals">
<head>Goals</head>
@@ -181,6 +150,37 @@
ref="UDDIAPI20" />, <bibref ref="UDDIDataStructure20"
/>, <bibref ref="UDDI30" />].</p>
</div2>
+ <div2 id="Example">
+ <head>Example</head>
+ <p>The following example illustrates a security policy using
+ assertions defined in WS-SecurityPolicy [<bibref
+ ref="WS-SecurityPolicy"/>]:</p>
+
+ <example>
+ <head>Use of Web Services Policy with security policy assertions.</head>
+ <eg xml:space="preserve">
+(01) <wsp:Policy
+ xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
+ xmlns:wsp="&nsuri;" >
+(02) <wsp:ExactlyOne>
+(03) <sp:Basic256Rsa15 />
+(04) <sp:TripleDesRsa15 />
+(05) </wsp:ExactlyOne>
+(06) </wsp:Policy></eg>
+ </example>
+
+ <p>Lines (01-06) represent a
+ policy for the algorithm suite required for performing
+ cryptographic operations with symmetric or asymmetric
+ key-based security tokens.</p>
+
+ <p>Lines (02-05) illustrate the <el>ExactlyOne</el> policy
+ operator. Policy operators group policy assertions into
+ policy alternatives. A valid interpretation of the policy
+ above would be that an invocation of a Web service uses
+ one of the algorithm suite assertions (Lines 03-04)
+ specified.</p>
+ </div2>
</div1>
<div1 id='Notation_Terminilogy'>
<head>Notations and Terminology</head>
@@ -227,17 +227,7 @@
<item>
<p>The ellipses characters "…" are used to
indicate a point of extensibility that allows other
- Element or Attribute Information Items. Information Items
- <rfc2119>MAY</rfc2119> be added at the indicated extension
- points but <rfc2119>MUST NOT</rfc2119> contradict the
- semantics of the element information item indicated by the
- <emph role='infoset-property'>parent</emph> or <emph
- role='infoset-property'>owner</emph> property of the
- extension. If a processor does not recognize an Attribute
- Information Item, the processor <rfc2119>SHOULD</rfc2119>
- ignore it; if a processor does not recognize an Element
- Information Item, the processor <rfc2119>SHOULD</rfc2119>
- treat it as an assertion.</p>
+ Element or Attribute Information Items.</p>
</item>
</ulist>
@@ -248,7 +238,19 @@
descriptions.
</p>
</div2>
-
+
+ <div2 id="Extensibility">
+ <head>Extensibility</head>
+ <p>Within normative outlines, ellipses (i.e., "…")
+ indicate a point of extensibility that allows other Element or Attribute
+ Information Items. Information Items <rfc2119>MAY</rfc2119> be added at the
+ indicated extension points but <rfc2119>MUST NOT</rfc2119> contradict the semantics
+ of the element information item indicated by the <emph role='infoset-property'>parent</emph>
+ or <emph role='infoset-property'>owner</emph> property of the extension. If an
+ Attribute Information Item is not recognized, it <rfc2119>SHOULD</rfc2119>
+ be ignored; if an Element Information Item is not recognized, it
+ <rfc2119>SHOULD</rfc2119> be treated as an assertion.</p>
+ </div2>
<div2 id="XML_Namespaces">
<head>XML Namespaces</head>
@@ -1517,6 +1519,22 @@
as early as possible in the doc, use the definition that are defined in the doc.
</td>
</tr>
+ <tr>
+ <td>20060808</td>
+ <td>ASV</td>
+ <td>Implemented the
+ <loc href="http://www.w3.org/2006/08/02-ws-policy-minutes.html#action08">resolution</loc>
+ for issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3543">3543</loc> and
+ the <loc href="http://www.w3.org/2006/07/26-ws-policy-minutes.html#action15">
+ resolution</loc> for issue
+ <loc href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Jul/0072.html">
+ 'Modify wording in Abstract for Framework'</loc>.
+ Restored Section <specref ref='Extensibility'/> (that was accidentally dropped).
+ Completed action item <loc href="http://www.w3.org/2006/07/12-ws-policy-minutes.html#action17">17</loc>
+ from the Austin F2F.
+ </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.15
retrieving revision 1.16
diff -u -d -r1.15 -r1.16
--- ws-policy-framework.html 8 Aug 2006 23:05:10 -0000 1.15
+++ ws-policy-framework.html 9 Aug 2006 06:06:33 -0000 1.16
@@ -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 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 - Framework</h1>
<h2>Editors' copy $Date$ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
@@ -62,9 +62,8 @@
<dd>Prasad Yendluri, webMethods, Inc.</dd>
</dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © @@@@ <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr><div>
<h2><a name="abstract">Abstract</a></h2>
- <p>The Web Services Policy 1.5 - Framework provides a general
- purpose model and corresponding syntax to describe the
- policies of a Web Service.</p>
+ <p>The Web Services Policy 1.5 - Framework provides a general purpose model and corresponding
+ syntax to describe the policies of entities in a Web services-based system.</p>
<p>Web Services Policy Framework defines a base set of
constructs that can be used and extended by other Web
services specifications to describe a broad range of service
@@ -73,8 +72,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> 1.1 <a href="#Goals">Goals</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="#XML_Namespaces">XML Namespaces</a><br> 2.3 <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> 4.1 <a href="#Normal_Form_Policy_Expression">Normal Form Policy Expression</a><br> 4.2 <a href="#Poicy_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 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="#changelog">Web Services Policy 1.5 - Framework 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> 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="#changelog">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>
@@ -86,11 +85,11 @@
model for the expression of these properties as
policies.</p>
- <p>[<a name="policy" title="policy">Definition</a>: A <b>policy</b> is a collection of
+ <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>, ]
- where [<a name="policy_alternative" title="policy alternative">Definition</a>: a <b>policy alternative</b>
+ where [<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>.]
- [<a name="policy_assertion" title="policy assertion">Definition</a>: A <b>policy assertion</b>
+ [<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.]
Some policy assertions
specify traditional requirements and capabilities that
@@ -104,12 +103,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 name="policy_attachment" title="policy attachment">Definition</a>: A
+ [<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>.]
- [<a name="policy_scope" title="policy scope">Definition</a>: A <b>policy scope</b> is a collection of
+ [<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.]
- [<a name="policy_subject" title="policy subject">Definition</a>: A <b>policy subject</b> is an entity
+ [<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. ]
@@ -121,35 +120,6 @@
with arbitrary XML elements [<cite><a href="#XML10">XML 1.0</a></cite>], WSDL artifacts [<cite><a href="#WSDL11">WSDL 1.1</a></cite>, <cite><a href="#WSDL20">WSDL 2.0 Core Language</a></cite>], and UDDI
elements [<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>].</p>
- <p>The following example illustrates a security policy using
- assertions defined in WS-SecurityPolicy [<cite><a href="#WS-SecurityPolicy">WS-SecurityPolicy</a></cite>]:</p>
-
- <div class="exampleOuter">
- <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"
- xmlns:wsp="http://www.w3.org/@@@@/@@/policy" >
-(02) <wsp:ExactlyOne>
-(03) <sp:Basic256Rsa15 />
-(04) <sp:TripleDesRsa15 />
-(05) </wsp:ExactlyOne>
-(06) </wsp:Policy>
- </pre></div>
- </div>
-
- <p>Lines (01-06) represent a
- policy for the algorithm suite required for performing
- cryptographic operations with symmetric or asymmetric
- key-based security tokens.</p>
-
- <p>Lines (02-05) illustrate the <code class="elt">ExactlyOne</code> policy
- operator. Policy operators group policy assertions into
- policy alternatives. A valid interpretation of the policy
- above would be that an invocation of a Web service uses
- one of the algorithm suite assertions (Lines 03-04)
- specified.</p>
-
<div class="div2">
<h3><a name="Goals"></a>1.1 Goals</h3>
@@ -164,7 +134,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 name="policy_expression" title="policy expression">Definition</a>: A <b>policy expression</b>
+ Service policy information. [<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></li>
@@ -178,6 +148,37 @@
general Web services framework, including WSDL service
descriptions [<cite><a href="#WSDL11">WSDL 1.1</a></cite>, <cite><a href="#WSDL20">WSDL 2.0 Core Language</a></cite>] and UDDI service registrations [<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>].</p>
</div>
+ <div class="div2">
+
+<h3><a name="Example"></a>1.2 Example</h3>
+ <p>The following example illustrates a security policy using
+ 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>
+ <div class="exampleInner"><pre>
+(01) <wsp:Policy
+ xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
+ xmlns:wsp="http://www.w3.org/@@@@/@@/policy" >
+(02) <wsp:ExactlyOne>
+(03) <sp:Basic256Rsa15 />
+(04) <sp:TripleDesRsa15 />
+(05) </wsp:ExactlyOne>
+(06) </wsp:Policy></pre></div>
+ </div>
+
+ <p>Lines (01-06) represent a
+ policy for the algorithm suite required for performing
+ cryptographic operations with symmetric or asymmetric
+ key-based security tokens.</p>
+
+ <p>Lines (02-05) illustrate the <code class="elt">ExactlyOne</code> policy
+ operator. Policy operators group policy assertions into
+ policy alternatives. A valid interpretation of the policy
+ above would be that an invocation of a Web service uses
+ one of the algorithm suite assertions (Lines 03-04)
+ specified.</p>
+ </div>
</div>
<div class="div1">
@@ -224,16 +225,7 @@
<li>
<p>The ellipses characters "…" are used to
indicate a point of extensibility that allows other
- Element or Attribute Information Items. Information Items
- <span class="rfc2119">MAY</span> be added at the indicated extension
- points but <span class="rfc2119">MUST NOT</span> contradict the
- semantics of the element information item indicated by the
- <strong>[parent]</strong> or <strong>[owner]</strong> property of the
- extension. If a processor does not recognize an Attribute
- Information Item, the processor <span class="rfc2119">SHOULD</span>
- ignore it; if a processor does not recognize an Element
- Information Item, the processor <span class="rfc2119">SHOULD</span>
- treat it as an assertion.</p>
+ Element or Attribute Information Items.</p>
</li>
</ul>
@@ -244,10 +236,23 @@
descriptions.
</p>
</div>
-
+
<div class="div2">
-<h3><a name="XML_Namespaces"></a>2.2 XML Namespaces</h3>
+<h3><a name="Extensibility"></a>2.2 Extensibility</h3>
+ <p>Within normative outlines, ellipses (i.e., "…")
+ indicate a point of extensibility that allows other Element or Attribute
+ Information Items. Information Items <span class="rfc2119">MAY</span> be added at the
+ indicated extension points but <span class="rfc2119">MUST NOT</span> contradict the semantics
+ of the element information item indicated by the <strong>[parent]</strong>
+ or <strong>[owner]</strong> property of the extension. If an
+ Attribute Information Item is not recognized, it <span class="rfc2119">SHOULD</span>
+ be ignored; if an Element Information Item is not recognized, it
+ <span class="rfc2119">SHOULD</span> be treated as an assertion.</p>
+ </div>
+ <div class="div2">
+
+<h3><a name="XML_Namespaces"></a>2.3 XML Namespaces</h3>
<p> This specification uses a number of namespace prefixes throughout; they are
listed in <a href="#nsprefix">Table 2-1</a>. Note that the choice of any namespace
@@ -320,7 +325,7 @@
</div>
<div class="div2">
-<h3><a name="Terminology"></a>2.3 Terminology</h3>
+<h3><a name="Terminology"></a>2.4 Terminology</h3>
<p>
The keywords "<span class="rfc2119">MUST</span>", "<span class="rfc2119">MUST
@@ -360,7 +365,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 name="policy_assertion_type" title="policy assertion type">Definition</a>: A <b>policy assertion type</b>
+ [<a title="policy assertion type" name="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
@@ -380,7 +385,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 name="policy_assertion_parameter" title="policy assertion parameter">Definition</a>: A <b>policy assertion parameter</b>
+ [<a title="policy assertion parameter" name="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
@@ -412,7 +417,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 name="policy_vocabulary" title="policy vocabulary">Definition</a>: A <b>policy vocabulary</b> is the set of all
+ [<a title="policy vocabulary" name="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
@@ -1479,12 +1484,42 @@
</td>
</tr>
<tr>
+ <td rowspan="1" colspan="1">20060803</td>
+ <td rowspan="1" colspan="1">PY</td>
+ <td rowspan="1" colspan="1">Completed Issue: <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3551">3551</a>
+ Misc updates throughout.
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">20060808</td>
+ <td rowspan="1" colspan="1">PY</td>
+ <td rowspan="1" colspan="1">Completed action item: <a href="http://www.w3.org/2006/07/13-ws-policy-minutes.html#action20">20</a>
+ to highlight infoset terms uniformly.
+ </td>
+ </tr>
+ <tr>
<td rowspan="1" colspan="1">20060808</td>
<td rowspan="1" colspan="1">DBO</td>
<td rowspan="1" colspan="1">Completed action items: <a href="http://www.w3.org/2006/07/12-ws-policy-minutes.html#action15">15</a>
as early as possible in the doc, use the definition that are defined in the doc.
</td>
</tr>
+ <tr>
+ <td rowspan="1" colspan="1">20060808</td>
+ <td rowspan="1" colspan="1">ASV</td>
+ <td rowspan="1" colspan="1">Implemented the
+ <a href="http://www.w3.org/2006/08/02-ws-policy-minutes.html#action08">resolution</a>
+ for issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3543">3543</a> and
+ the <a href="http://www.w3.org/2006/07/26-ws-policy-minutes.html#action15">
+ resolution</a> for issue
+ <a href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Jul/0072.html">
+ 'Modify wording in Abstract for Framework'</a>.
+ Restored Section <a href="#Extensibility"><b>2.2 Extensibility</b></a> (that was accidentally dropped).
+ Completed action item <a href="http://www.w3.org/2006/07/12-ws-policy-minutes.html#action17">17</a>
+ from the Austin F2F.
+ </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.17
retrieving revision 1.18
diff -u -d -r1.17 -r1.18
--- ws-policy-attachment.xml 9 Aug 2006 00:31:59 -0000 1.17
+++ ws-policy-attachment.xml 9 Aug 2006 06:06:33 -0000 1.18
@@ -134,17 +134,7 @@
<item>
<p>The ellipses characters "…" are used to
indicate a point of extensibility that allows other
- Element or Attribute Information Items. Information Items
- <rfc2119>MAY</rfc2119> be added at the indicated extension
- points but <rfc2119>MUST NOT</rfc2119> contradict the
- semantics of the element information item indicated by the
- <emph role='infoset-property'>parent</emph> or <emph
- role='infoset-property'>owner</emph> property of the
- extension. If a processor does not recognize an Attribute
- Information Item, the processor <rfc2119>SHOULD</rfc2119>
- ignore it; if a processor does not recognize an Element
- Information Item, the processor <rfc2119>SHOULD</rfc2119>
- treat it as an assertion.</p>
+ Element or Attribute Information Items.</p>
</item>
</ulist>
<p>Elements and Attributes defined by this specification are referred to in the text of this document using
@@ -1884,7 +1874,16 @@
Issue <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3545">3545</loc>,
use of {any} and {@any} in xpath-like expressions not defined in Notational Conventions section
</td>
- </tr>
+ </tr>
+ <tr>
+ <td>20060808</td>
+ <td>ASV</td>
+ <td>Implemented the
+ <loc href="http://www.w3.org/2006/08/02-ws-policy-minutes.html#action08">resolution</loc>
+ for issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3543">3543</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.21
retrieving revision 1.22
diff -u -d -r1.21 -r1.22
--- ws-policy-attachment.html 9 Aug 2006 00:31:59 -0000 1.21
+++ ws-policy-attachment.html 9 Aug 2006 06:06:33 -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 - 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>
@@ -135,16 +135,7 @@
<li>
<p>The ellipses characters "…" are used to
indicate a point of extensibility that allows other
- Element or Attribute Information Items. Information Items
- <span class="rfc2119">MAY</span> be added at the indicated extension
- points but <span class="rfc2119">MUST NOT</span> contradict the
- semantics of the element information item indicated by the
- <strong>[parent]</strong> or <strong>[owner]</strong> property of the
- extension. If a processor does not recognize an Attribute
- Information Item, the processor <span class="rfc2119">SHOULD</span>
- ignore it; if a processor does not recognize an Element
- Information Item, the processor <span class="rfc2119">SHOULD</span>
- treat it as an assertion.</p>
+ Element or Attribute Information Items.</p>
</li>
</ul>
<p>Elements and Attributes defined by this specification are referred to in the text of this document using
@@ -287,32 +278,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>
@@ -330,7 +321,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"
@@ -345,7 +336,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"
@@ -425,7 +416,7 @@
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
@@ -487,7 +478,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>
@@ -505,7 +496,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"
@@ -727,7 +718,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.
@@ -896,7 +887,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"
@@ -963,7 +954,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"
@@ -1868,7 +1859,16 @@
Issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3545">3545</a>,
use of {any} and {@any} in xpath-like expressions not defined in Notational Conventions section
</td>
- </tr>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">20060808</td>
+ <td rowspan="1" colspan="1">ASV</td>
+ <td rowspan="1" colspan="1">Implemented the
+ <a href="http://www.w3.org/2006/08/02-ws-policy-minutes.html#action08">resolution</a>
+ for issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3543">3543</a>.
+ </td>
+ </tr>
</tbody>
</table><br>
</div>
Received on Wednesday, 9 August 2006 06:06:51 UTC