- From: Philippe Le Hegaret via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 21 Feb 2007 20:09:46 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv28096
Modified Files:
ws-policy-attachment.html ws-policy-framework.html
Log Message:
New
Index: ws-policy-framework.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.html,v
retrieving revision 1.99
retrieving revision 1.100
diff -u -d -r1.99 -r1.100
--- ws-policy-framework.html 9 Feb 2007 22:51:57 -0000 1.99
+++ ws-policy-framework.html 21 Feb 2007 20:09:43 -0000 1.100
@@ -59,7 +59,7 @@
<h2><a name="w3c-doctype" id="w3c-doctype"></a>Editors' copy $Date$ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
<a href="ws-policy-framework.html">ws-policy-framework.html</a>
</dd><dt>Latest version:</dt><dd><a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-framework.html?content-type=text/html;charset=utf-8">http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-framework.html?content-type=text/html;charset=utf-8</a></dd><dt>Previous version:</dt><dd>
- <a href="http://www.w3.org/TR/2006/WD-ws-policy-20060927">http://www.w3.org/TR/2006/WD-ws-policy-20060927</a>
+ <a href="http://www.w3.org/TR/2006/WD-ws-policy-20061117">http://www.w3.org/TR/2006/WD-ws-policy-20061117</a>
</dd><dt>Editors:</dt><dd>Asir S Vedamuthu, Microsoft Corporation</dd><dd>David Orchard, BEA Systems, Inc.</dd><dd>Frederick Hirsch, Nokia</dd><dd>Maryann Hondo, IBM Corporation</dd><dd>Prasad Yendluri, webMethods, Inc.</dd><dd>Toufic Boubez, Layer 7 Technologies</dd><dd>Ümit Yalçinalp, SAP AG.</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" id="abstract"></a>Abstract</h2><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
@@ -254,7 +254,7 @@
alternative</a>.</p></dd><dt class="label">
<a href="#policy_assertion">policy assertion</a>
</dt><dd><p>A <b>policy assertion</b>
- represents an individual requirement, capability, or other property of a behavior.</p></dd><dt class="label">
+ represents a requirement, a capability, or other property of a behavior.</p></dd><dt class="label">
<a href="#policy_assertion_parameter">policy assertion parameter</a>
</dt><dd><p>A <b>policy assertion parameter</b>
qualifies the behavior indicated by a <a title="policy assertion" href="#policy_assertion">policy assertion</a>.</p></dd><dt class="label">
@@ -430,7 +430,7 @@
enumerate each of their <a title="policy assertion" href="#policy_assertion">assertions</a>. The schema outline for
the normal form of a policy expression is as follows:</p><div class="exampleInner"><pre>(01) <wsp:Policy … >
(02) <wsp:ExactlyOne>
-(03) ( <wsp:All> ( <<emph>Assertion</emph> …> … </<emph>Assertion</emph>> )* </wsp:All> )*
+(03) ( <wsp:All> ( <<b>Assertion</b> …> … </<b>Assertion</b>> )* </wsp:All> )*
(04) </wsp:ExactlyOne>
(05) </wsp:Policy> </pre></div><p>The following describes the Element Information Items defined in the schema outline above:</p><dl><dt class="label"><code>/wsp:Policy</code></dt><dd><p>A policy expression.</p></dd><dt class="label"><code>/wsp:Policy/wsp:ExactlyOne</code></dt><dd><p>
A collection of policy alternatives. If there are no Element
@@ -467,8 +467,8 @@
conversely, if the second alternative is selected, the message body needs to be encrypted. </p></div><div class="div2">
<h3><a name="Policy_Identification" id="Policy_Identification"></a>4.2 Policy Identification</h3><p>A <a title="policy expression" href="#policy_expression">policy expression</a>
<span class="rfc2119">MAY</span> be associated with an IRI [<cite><a href="#RFC3987">IETF RFC 3987</a></cite>]. The schema outline
-for attributes to associate an IRI is as follows:</p><div class="exampleInner"><pre>(01) <wsp:Policy ( Name="<emph>xs:anyURI</emph>" )?
-(02) ( wsu:Id="<emph>xs:ID</emph>" | xml:id="<emph>xs:ID</emph>" )?
+for attributes to associate an IRI is as follows:</p><div class="exampleInner"><pre>(01) <wsp:Policy ( Name="<b>xs:anyURI</b>" )?
+(02) ( wsu:Id="<b>xs:ID</b>" | xml:id="<b>xs:ID</b>" )?
(03) … >
(04) …
(05) </wsp:Policy></pre></div><p>The following describes the Attribute Information Items listed and defined in the schema outline above:</p><dl><dt class="label"><code>/wsp:Policy/@Name</code></dt><dd><p>The identity of the policy expression as an absolute IRI [<cite><a href="#RFC3987">IETF RFC 3987</a></cite>]. If
@@ -516,12 +516,12 @@
assertion</a> is optional, this specification defines an attribute
that is a compact authoring style for expressing a pair of <a title="policy alternative" href="#policy_alternative">alternatives</a>,
one with and one without that assertion. The schema outline for
-this attribute is as follows:</p><div class="exampleInner"><pre>(01) <<emph>Assertion</emph> ( wsp:Optional="<emph>xs:boolean</emph>" )? …> … </<emph>Assertion</emph>></pre></div><p>The following describes the Attribute Information Item defined in
+this attribute is as follows:</p><div class="exampleInner"><pre>(01) <<b>Assertion</b> ( wsp:Optional="<b>xs:boolean</b>" )? …> … </<b>Assertion</b>></pre></div><p>The following describes the Attribute Information Item defined in
the schema outline above:</p><dl><dt class="label"><code>/Assertion/@wsp:Optional</code></dt><dd><p>If the actual value (See XML Schema Part 1 [<cite><a href="#XMLSchemaPart1">XML Schema Structures</a></cite>]) is true, the expression of the assertion is semantically equivalent to the following:</p><div class="exampleInner"><pre>(01) <wsp:ExactlyOne>
-(02) <wsp:All> <<emph>Assertion</emph> …> … </<emph>Assertion</emph>> </wsp:All>
+(02) <wsp:All> <<b>Assertion</b> …> … </<b>Assertion</b>> </wsp:All>
(03) <wsp:All />
(04) </wsp:ExactlyOne></pre></div><p>If the actual value (See XML Schema Part 1 [<cite><a href="#XMLSchemaPart1">XML Schema Structures</a></cite>]) is false, the expression of the assertion is semantically equivalent to the following:</p><div class="exampleInner"><pre>(01) <wsp:ExactlyOne>
-(02) <wsp:All> <<emph>Assertion</emph> …> … </<emph>Assertion</emph>> </wsp:All>
+(02) <wsp:All> <<b>Assertion</b> …> … </<b>Assertion</b>> </wsp:All>
(03) </wsp:ExactlyOne></pre></div><p>Omitting this attribute is semantically equivalent to including it
with a value of false. Policy expressions should not include this
attribute with a value of false, but policy parsers must accept this
@@ -546,11 +546,11 @@
policy expression.</p></div><div class="div3">
<h4><a name="Policy_Assertion_Nesting" id="Policy_Assertion_Nesting"></a>4.3.2 Policy Assertion Nesting</h4><p>Any <a title="policy assertion" href="#policy_assertion">policy assertion</a>
<span class="rfc2119">MAY</span> contain a <a title="policy expression" href="#policy_expression">policy expression</a>. [<a name="nested_policy_expression" id="nested_policy_expression" title="nested policy expression">Definition</a>: A <b>nested policy expression</b> is a <a title="policy expression" href="#policy_expression">policy expression</a> that is an Element Information Item in the <strong>[children]</strong> property of a <a title="policy assertion" href="#policy_assertion">policy assertion</a>.] The schema
-outline for a <a title="nested policy expression" href="#nested_policy_expression">nested policy expression</a> is:</p><div class="exampleInner"><pre>(01) <<emph>Assertion</emph> …>
+outline for a <a title="nested policy expression" href="#nested_policy_expression">nested policy expression</a> is:</p><div class="exampleInner"><pre>(01) <<b>Assertion</b> …>
(02) …
(03) ( <wsp:Policy …> … </wsp:Policy> )?
(04) …
-(05) </<emph>Assertion</emph>></pre></div><p>The following describes additional processing constraints on the outline listed above:</p><dl><dt class="label"><code>/Assertion/wsp:Policy</code></dt><dd><p>This indicates that the assertion contains a nested policy
+(05) </<b>Assertion</b>></pre></div><p>The following describes additional processing constraints on the outline listed above:</p><dl><dt class="label"><code>/Assertion/wsp:Policy</code></dt><dd><p>This indicates that the assertion contains a nested policy
expression. If there is no <code>wsp:Policy</code> Element Information
Item in the <strong>[children]</strong> property,
the assertion has no nested policy expression.
@@ -724,58 +724,58 @@
(06) </wsp:ExactlyOne></pre></div></dd><dt class="label">Empty</dt><dd><ul><li><p><code><wsp:All /></code> expresses a policy with zero policy assertions. Note that since <code>wsp:Policy</code> is equivalent to <code>wsp:All</code>, <code><wsp:Policy /></code> is therefore equivalent to <code><wsp:All /></code>, i.e., a policy alternative with zero assertions.</p></li><li><p><code><wsp:ExactlyOne /></code> expresses a policy with zero policy alternatives.</p></li></ul></dd><dt class="label">Commutative</dt><dd><p>In line with the previous statements that policy assertions within
a policy alternative and policy alternatives within a policy are not
ordered (see <a href="#rPolicy_Alternative"><b>3.2 Policy Alternative</b></a> and <a href="#rPolicy"><b>3.3 Policy</b></a>, respectively), <code>wsp:All</code> and
-<code>wsp:ExactlyOne</code> are commutative. For example,</p><div class="exampleInner"><pre>(01) <wsp:All> <emph><!-- assertion 1 --> <!-- assertion 2 --> </emph></wsp:All></pre></div><p>is equivalent to:</p><div class="exampleInner"><pre>(01) <wsp:All> <emph><!-- assertion 2 --> <!-- assertion 1 --> </emph></wsp:All></pre></div><p>and:</p><div class="exampleInner"><pre>(01) <wsp:ExactlyOne>
-(02) <emph><!-- assertion 1 --> <!-- assertion 2 --></emph>
+<code>wsp:ExactlyOne</code> are commutative. For example,</p><div class="exampleInner"><pre>(01) <wsp:All> <b><!-- assertion 1 --> <!-- assertion 2 --> </b></wsp:All></pre></div><p>is equivalent to:</p><div class="exampleInner"><pre>(01) <wsp:All> <b><!-- assertion 2 --> <!-- assertion 1 --> </b></wsp:All></pre></div><p>and:</p><div class="exampleInner"><pre>(01) <wsp:ExactlyOne>
+(02) <b><!-- assertion 1 --> <!-- assertion 2 --></b>
(03) </wsp:ExactlyOne></pre></div><p>is equivalent to:</p><div class="exampleInner"><pre>(01) <wsp:ExactlyOne>
-(02) <emph><!-- assertion 2 --> <!-- assertion 1 --></emph>
+(02) <b><!-- assertion 2 --> <!-- assertion 1 --></b>
(03) </wsp:ExactlyOne></pre></div></dd><dt class="label">Associative</dt><dd><p><code>wsp:All</code> and <code>wsp:ExactlyOne</code> are associative. For example,</p><div class="exampleInner"><pre>(01) <wsp:All>
-(02) <emph><!-- assertion 1 --></emph>
-(03) <emph> </emph><wsp:All> <emph><!-- assertion 2 --> </emph></wsp:All>
-(04) </wsp:All></pre></div><p>is equivalent to:</p><div class="exampleInner"><pre>(01) <wsp:All> <emph><!-- assertion 1 --> <!-- assertion 2 --> </emph></wsp:All></pre></div><p>and:</p><div class="exampleInner"><pre>(01) <wsp:ExactlyOne>
-(02) <emph><!-- assertion 1 --></emph>
-(03) <emph> </emph><wsp:ExactlyOne> <emph><!-- assertion 2 --> </emph></wsp:ExactlyOne>
+(02) <b><!-- assertion 1 --></b>
+(03) <b> </b><wsp:All> <b><!-- assertion 2 --> </b></wsp:All>
+(04) </wsp:All></pre></div><p>is equivalent to:</p><div class="exampleInner"><pre>(01) <wsp:All> <b><!-- assertion 1 --> <!-- assertion 2 --> </b></wsp:All></pre></div><p>and:</p><div class="exampleInner"><pre>(01) <wsp:ExactlyOne>
+(02) <b><!-- assertion 1 --></b>
+(03) <b> </b><wsp:ExactlyOne> <b><!-- assertion 2 --> </b></wsp:ExactlyOne>
(04) </wsp:ExactlyOne></pre></div><p>is equivalent to:</p><div class="exampleInner"><pre>(01) <wsp:ExactlyOne>
-(02) <emph><!-- assertion 1 --> <!-- assertion 2 --></emph>
+(02) <b><!-- assertion 1 --> <!-- assertion 2 --></b>
(03) </wsp:ExactlyOne></pre></div></dd><dt class="label">Idempotent</dt><dd><p><code>wsp:All</code> and <code>wsp:ExactlyOne</code> are idempotent. For example,</p><div class="exampleInner"><pre>(01) <wsp:All>
-(02) <wsp:All> <emph><!-- assertion 1 --> <!-- assertion 2 --> </emph></wsp:All>
-(03) </wsp:All></pre></div><p>is equivalent to:</p><div class="exampleInner"><pre>(01) <wsp:All> <emph><!-- assertion 1 --> <!-- assertion 2 --> </emph></wsp:All></pre></div><p>and:</p><div class="exampleInner"><pre>(01) <wsp:ExactlyOne>
+(02) <wsp:All> <b><!-- assertion 1 --> <!-- assertion 2 --> </b></wsp:All>
+(03) </wsp:All></pre></div><p>is equivalent to:</p><div class="exampleInner"><pre>(01) <wsp:All> <b><!-- assertion 1 --> <!-- assertion 2 --> </b></wsp:All></pre></div><p>and:</p><div class="exampleInner"><pre>(01) <wsp:ExactlyOne>
(02) <wsp:ExactlyOne>
-(03) <emph><!-- assertion 1 --> <!-- assertion 2 --></emph>
-(04) <emph> </emph></wsp:ExactlyOne>
+(03) <b><!-- assertion 1 --> <!-- assertion 2 --></b>
+(04) <b> </b></wsp:ExactlyOne>
(05) </wsp:ExactlyOne></pre></div><p>is equivalent to:</p><div class="exampleInner"><pre>(01) <wsp:ExactlyOne>
-(02) <emph><!-- assertion 1 --> <!-- assertion 2 --></emph>
+(02) <b><!-- assertion 1 --> <!-- assertion 2 --></b>
(03) </wsp:ExactlyOne></pre></div></dd><dt class="label">Distributive</dt><dd><p><code>wsp:All</code> distributes over <code>wsp:ExactlyOne</code>. For example,</p><div class="exampleInner"><pre>(01) <wsp:All>
(02) <wsp:ExactlyOne>
-(03) <emph> <!-- assertion 1 --></emph>
-(04) <emph> <!-- assertion 2 --></emph>
+(03) <b> <!-- assertion 1 --></b>
+(04) <b> <!-- assertion 2 --></b>
(05) </wsp:ExactlyOne>
(06) </wsp:All></pre></div><p>is equivalent to:</p><div class="exampleInner"><pre>(01) <wsp:ExactlyOne>
(02) <wsp:All>
-(03) <emph> <!-- assertion 1 --></emph>
+(03) <b> <!-- assertion 1 --></b>
(04) </wsp:All>
(05) <wsp:All>
-(06) <emph> <!-- assertion 2 --></emph>
+(06) <b> <!-- assertion 2 --></b>
(07) </wsp:All>
(08) </wsp:ExactlyOne></pre></div><p>Similarly by repeatedly distributing wsp:All over wsp:ExactlyOne,</p><div class="exampleInner"><pre>(01) <wsp:All>
(02) <wsp:ExactlyOne>
-(03) <emph> <!-- assertion 1 --></emph>
-(04) <emph> <!-- assertion 2 --></emph>
+(03) <b> <!-- assertion 1 --></b>
+(04) <b> <!-- assertion 2 --></b>
(05) </wsp:ExactlyOne>
(06) <wsp:ExactlyOne>
-(07) <emph> <!-- assertion 3 --></emph>
-(08) <emph> <!-- assertion 4 --></emph>
+(07) <b> <!-- assertion 3 --></b>
+(08) <b> <!-- assertion 4 --></b>
(09) </wsp:ExactlyOne>
(10) </wsp:All></pre></div><p>is equivalent to:</p><div class="exampleInner"><pre>(01) <wsp:ExactlyOne>
-(02) <wsp:All><emph><!-- assertion 1 --><!-- assertion 3 --></emph></wsp:All>
-(03) <wsp:All><emph><!-- assertion 1 --><!-- assertion 4 --></emph></wsp:All>
-(04) <wsp:All><emph><!-- assertion 2 --><!-- assertion 3 --></emph></wsp:All>
-(05) <wsp:All><emph><!-- assertion 2 --><!-- assertion 4 --></emph></wsp:All>
+(02) <wsp:All><b><!-- assertion 1 --><!-- assertion 3 --></b></wsp:All>
+(03) <wsp:All><b><!-- assertion 1 --><!-- assertion 4 --></b></wsp:All>
+(04) <wsp:All><b><!-- assertion 2 --><!-- assertion 3 --></b></wsp:All>
+(05) <wsp:All><b><!-- assertion 2 --><!-- assertion 4 --></b></wsp:All>
(06) </wsp:ExactlyOne></pre></div><p>Distributing <code>wsp:All</code> over an empty <code>wsp:ExactlyOne</code> is equivalent to no alternatives. For example,</p><div class="exampleInner"><pre>(01) <wsp:All>
(02) <wsp:ExactlyOne />
(03) </wsp:All></pre></div><p>is equivalent to:</p><div class="exampleInner"><pre>(01) <wsp:ExactlyOne /></pre></div><p>and:</p><div class="exampleInner"><pre>(01) <wsp:All>
(02) <wsp:ExactlyOne>
-(03) <emph> <!-- assertion 1 --></emph>
-(04) <emph> <!-- assertion 2 --></emph>
+(03) <b> <!-- assertion 1 --></b>
+(04) <b> <!-- assertion 2 --></b>
(05) </wsp:ExactlyOne>
(06) <wsp:ExactlyOne />
(07) </wsp:All></pre></div><p>is equivalent to:</p><div class="exampleInner"><pre>(01) <wsp:ExactlyOne /></pre></div><p>For example, given the following compact policy expression:</p><div class="exampleInner"><pre>(01) <wsp:Policy
@@ -827,8 +827,8 @@
(17) </wsp:ExactlyOne>
(18) </wsp:Policy></pre></div><p>Note that the two alternatives listed in Lines (03-06) in the second listing are combined with the two alternatives listed in Lines (09-14) in the second listing to create four alternatives in the normalized policy, Lines (03-06), (07-10), (11-13), and (14-16).</p></div><div class="div3">
<h4><a name="Policy_References" id="Policy_References"></a>4.3.4 Policy References</h4><p>The <code>wsp:PolicyReference</code> element is used to reference <a title="policy expression" href="#policy_expression">policy expressions</a>. The semantics of the <code>wsp:PolicyReference</code> element are determined by the context in which it is used (for an example, see <a href="#Policy_Inclusion"><b>4.3.5 Policy Inclusion</b></a>).</p><p>The schema outline for the <code>wsp:PolicyReference</code> element is as follows:</p><div class="exampleInner"><pre>(01) <wsp:PolicyReference
-(02) URI="<emph>xs:anyURI</emph>"
-(03) ( Digest="<emph>xs:base64Binary</emph>" ( DigestAlgorithm="<emph>xs:anyURI</emph>" )? )?
+(02) URI="<b>xs:anyURI</b>"
+(03) ( Digest="<b>xs:base64Binary</b>" ( DigestAlgorithm="<b>xs:anyURI</b>" )? )?
(04) … >
(05) …
(06) </wsp:PolicyReference></pre></div><p>The following describes the Attribute and Element Information Items defined in the schema outline above:</p><dl><dt class="label"><code>/wsp:PolicyReference</code></dt><dd><p>This element references a policy expression that is being referenced.</p></dd><dt class="label"><code>/wsp:PolicyReference/@URI</code></dt><dd><p>This attribute references a policy expression by an IRI. For a policy
@@ -1096,11 +1096,10 @@
Security Consideration section in <cite><a href="#WS-PolicyAttachment">Web Services Policy Attachment</a></cite>.</p></dd><dt class="label">Interoperability considerations:</dt><dd><p>There are no known interoperability issues.</p></dd><dt class="label">Published specifications:</dt><dd><p>This document and <cite><a href="#WS-PolicyAttachment">Web Services Policy Attachment</a></cite>.</p></dd><dt class="label">Applications which use this media type:</dt><dd><p>This new media type is being registered to allow for deployment of Web Services
Policy and references to Web Services Policy on the World Wide Web.</p></dd><dt class="label">Additional information:</dt><dd><dl><dt class="label">File extension:</dt><dd><p>wspolicy</p></dd><dt class="label">Fragment identifiers:</dt><dd><p>A syntax identical to that of
"application/xml" as described in <cite><a href="#RFC3023">IETF RFC 3023</a></cite>.</p></dd><dt class="label">Base URI:</dt><dd><p>As specified in <cite><a href="#RFC3023">IETF RFC 3023</a></cite>, section 6.
- Also see section
- <a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-framework.html?content-type=text/html;charset=utf-8#IRI_Policy_Expressions">4.6 Use of IRIs in Policy Expressions</a>
+ Also see section <a href="#IRI_Policy_Expressions"><b>4.6 Use of IRIs in Policy Expressions</b></a>
in this document and
<a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-attachment.html?content-type=text/html;charset=utf-8#IRI_Policy_Attachment">section 3.5
- Use of IRIs in Policy Attachment</a> in the Web Services Policy 1.5 - Attachment.</p></dd><dt class="label">Macintosh File Type code:</dt><dd><p>TEXT</p></dd><dt class="label">Person and email address to contact for further information:</dt><dd><p>World Wide Web Consortium <web-human@w3.org></p></dd><dt class="label">Intended usage:</dt><dd><p>COMMON</p></dd><dt class="label">Author/Change controller:</dt><dd><p>The Web Services Policy 1.5 specification set is a work product of the World Wide
+ Use of IRIs in Policy Attachment</a> in <cite><a href="#WS-PolicyAttachment">Web Services Policy Attachment</a></cite>.</p></dd><dt class="label">Macintosh File Type code:</dt><dd><p>TEXT</p></dd><dt class="label">Person and email address to contact for further information:</dt><dd><p>World Wide Web Consortium <web-human@w3.org></p></dd><dt class="label">Intended usage:</dt><dd><p>COMMON</p></dd><dt class="label">Author/Change controller:</dt><dd><p>The Web Services Policy 1.5 specification set is a work product of the World Wide
Web Consortium's
<a href="http://www.w3.org/2002/ws/desc/">Web Service Policy Working Group</a>.
The W3C has change control over these specifications.</p></dd></dl></dd></dl></div></div><div class="div1">
@@ -1290,7 +1289,7 @@
Dimitar Angelov (SAP AG), Abbie Barbir (Nortel Networks), Charlton Barreto (Adobe Systems Inc.), Sergey Beryozkin (IONA Technologies, Inc.), Vladislav Bezrukov (SAP AG), Toufic Boubez (Layer 7 Technologies), Symon Chang (BEA Systems, Inc.), Paul Cotton (Microsoft Corporation), Jeffrey Crump (Sonic Software), Glen Daniels (Sonic Software), Jacques Durand (Fujitsu Limited), Ruchith Fernando (WSO2), Christopher Ferris (IBM Corporation), William Henry (IONA Technologies, Inc.), Frederick Hirsch (Nokia), Maryann Hondo (IBM Corporation), Tom Jordahl (Adobe Systems Inc.), Paul Knight (Nortel Networks), Philippe Le Hégaret (W3C/MIT), Mark Little (JBoss Inc.), Ashok Malhotra (Oracle Corporation), Monica Martin (Sun Microsystems, Inc.), Arnaud Meyniel (Axway Software), Jeff Mischkinsky (Oracle Corporation), Dale Moberg (Axway Software), Anthony Nadalin (IBM Corporation), Bob Natale (MITRE Corporation), David Orchard (BEA Systems, Inc.), Fabian Ritzmann (Sun Microsystems, Inc.), Daniel Roth (Microsoft Corporaton), Tom Rutt (Fujitsu Limited), Sanka Samaranayake (WSO2), Felix Sasaki (W3C/Keio), Skip Snow (Citigroup), Yakov Sverdlov (CA Inc.), Mark Temple-Raston (Citigroup), Asir Vedamuthu (Microsoft Corporation), Sanjiva Weerawarana (WSO2), Ümit Yalçinalp (SAP AG), Prasad Yendluri (webMethods, Inc.).
</p><p>
Previous members of the Working Group were:
- Jong Lee (BEA Systems, Inc.), Bijan Parsia (University of Manchester), Seumas Soltysik (IONA Technologies, Inc.)
+ Jong Lee (BEA Systems, Inc.), Bijan Parsia (University of Manchester), Seumas Soltysik (IONA Technologies, Inc.).
</p><p>
The people who have contributed to <a href="http://lists.w3.org/Archives/Public/public-ws-policy/">discussions
on public-ws-policy@w3.org</a> are also gratefully
Index: ws-policy-attachment.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.html,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -d -r1.89 -r1.90
--- ws-policy-attachment.html 9 Feb 2007 22:51:57 -0000 1.89
+++ ws-policy-attachment.html 21 Feb 2007 20:09:43 -0000 1.90
@@ -59,7 +59,7 @@
<h2><a name="w3c-doctype" id="w3c-doctype"></a>Editors' copy $Date$ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
<a href="ws-policy-attachment.html">ws-policy-attachment.html</a>
</dd><dt>Latest version:</dt><dd><a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-attachment.html?content-type=text/html;charset=utf-8">http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-attachment.html?content-type=text/html;charset=utf-8</a></dd><dt>Previous version:</dt><dd>
- <a href="http://www.w3.org/TR/2006/WD-ws-policy-attach-20060927">http://www.w3.org/TR/2006/WD-ws-policy-attach-20060927</a>
+ <a href="http://www.w3.org/TR/2006/WD-ws-policy-attach-20061117">http://www.w3.org/TR/2006/WD-ws-policy-attach-20061117</a>
</dd><dt>Editors:</dt><dd>Asir S Vedamuthu, Microsoft Corporation</dd><dd>David Orchard, BEA Systems, Inc.</dd><dd>Frederick Hirsch, Nokia</dd><dd>Maryann Hondo, IBM Corporation</dd><dd>Prasad Yendluri, webMethods, Inc.</dd><dd>Toufic Boubez, Layer 7 Technologies</dd><dd>Ümit Yalçinalp, SAP AG.</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" id="abstract"></a>Abstract</h2><p>
This specification, Web Services Policy 1.5 - Attachment, defines two
@@ -260,7 +260,7 @@
interpreted as described in RFC 2119 [<cite><a href="#RFC2119">IETF RFC 2119</a></cite>].
</p><p>We introduce the following terms that are used throughout this document:</p><dl><dt class="label">
<a href="#effective_policy">effective policy</a>
- </dt><dd><p>the
+ </dt><dd><p>The
<b>effective policy</b>, for a given <a title="" href="#policy_subject">policy subject</a>, is the
combination of relevant policies. The relevant policies are those
attached to <a title="" href="#policy_scope">policy scopes</a> that
@@ -275,7 +275,7 @@
an assertion that may be ignored for policy intersection (as defined in
<a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-framework.html?content-type=text/html;charset=utf-8#Policy_Intersection">4.5 Policy Intersection</a>).</p></dd><dt class="label">
<a href="#merge">merge</a>
- </dt><dd><p>a <b>merge</b>
+ </dt><dd><p>A <b>merge</b>
consists of serializing each policy as a
<a title="" href="#policy_expression">policy expression</a>, replacing their
<code>wsp:Policy</code> element with a
@@ -290,7 +290,7 @@
is a potentially empty collection of <a title="" href="#policy_assertion">policy assertions</a>.</p></dd><dt class="label">
<a href="ws-policy-framework.html#policy_assertion">policy assertion</a>
</dt><dd><p id="policy_assertion">A <b>policy assertion</b>
- represents an individual requirement, capability, or other property of a behavior.</p></dd><dt class="label">
+ represents a requirement, a capability, or other property of a behavior.</p></dd><dt class="label">
<a href="ws-policy-framework.html#policy_attachment">policy attachment</a>
</dt><dd><p id="policy_attachment">A
<b>policy attachment</b> is a mechanism for associating
@@ -1492,9 +1492,9 @@
<h3><a name="Normative-References" id="Normative-References"></a>A.1 Normative References</h3><dl><dt class="label"><a name="BP11"></a>[BP 1.1] </dt><dd>
<cite><a href="http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html">Basic Profile Version 1.1</a></cite>, K. Ballinger,
et al, Editors. The Web Services-Interoperability
- Organization, 24 August 2004. This version of the Basic
+ Organization, 10 June 2006. This version of the Basic
Profile Version 1.1 is
- http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html. The
+ http://www.ws-i.org/Profiles/BasicProfile-1.1-2006-04-10.html. The
<a href="http://www.ws-i.org/Profiles/BasicProfile-1.1.html">latest
version of the Basic Profile Version 1.1</a> is available at
http://www.ws-i.org/Profiles/BasicProfile-1.1.html
@@ -1592,7 +1592,7 @@
Information Set</a> is available at
http://www.w3.org/TR/xml-infoset.
</dd><dt class="label"><a name="XML-NS"></a>[XML Namespaces] </dt><dd>
-<cite><a href="http://www.w3.org/TR/2006/REC-xml-names-20060816/">Namespaces in XML 1.0</a></cite>, T. Bray, D. Hollander,
+<cite><a href="http://www.w3.org/TR/2006/REC-xml-names-20060816/">Namespaces in XML 1.0 (Second Edition)</a></cite>, T. Bray, D. Hollander,
A. Layman, and R. Tobin, Editors. World Wide Web Consortium,
14 January 1999, revised 16 August 2006. This version of the
XML Information Set Recommendation is
@@ -1796,7 +1796,7 @@
Dimitar Angelov (SAP AG), Abbie Barbir (Nortel Networks), Charlton Barreto (Adobe Systems Inc.), Sergey Beryozkin (IONA Technologies, Inc.), Vladislav Bezrukov (SAP AG), Toufic Boubez (Layer 7 Technologies), Symon Chang (BEA Systems, Inc.), Paul Cotton (Microsoft Corporation), Jeffrey Crump (Sonic Software), Glen Daniels (Sonic Software), Jacques Durand (Fujitsu Limited), Ruchith Fernando (WSO2), Christopher Ferris (IBM Corporation), William Henry (IONA Technologies, Inc.), Frederick Hirsch (Nokia), Maryann Hondo (IBM Corporation), Tom Jordahl (Adobe Systems Inc.), Paul Knight (Nortel Networks), Philippe Le Hégaret (W3C/MIT), Mark Little (JBoss Inc.), Ashok Malhotra (Oracle Corporation), Monica Martin (Sun Microsystems, Inc.), Arnaud Meyniel (Axway Software), Jeff Mischkinsky (Oracle Corporation), Dale Moberg (Axway Software), Anthony Nadalin (IBM Corporation), Bob Natale (MITRE Corporation), David Orchard (BEA Systems, Inc.), Fabian Ritzmann (Sun Microsystems, Inc.), Daniel Roth (Microsoft Corporaton), Tom Rutt (Fujitsu Limited), Sanka Samaranayake (WSO2), Felix Sasaki (W3C/Keio), Skip Snow (Citigroup), Yakov Sverdlov (CA Inc.), Mark Temple-Raston (Citigroup), Asir Vedamuthu (Microsoft Corporation), Sanjiva Weerawarana (WSO2), Ümit Yalçinalp (SAP AG), Prasad Yendluri (webMethods, Inc.).
</p><p>
Previous members of the Working Group were:
- Jong Lee (BEA Systems, Inc.), Bijan Parsia (University of Manchester), Seumas Soltysik (IONA Technologies, Inc.)
+ Jong Lee (BEA Systems, Inc.), Bijan Parsia (University of Manchester), Seumas Soltysik (IONA Technologies, Inc.).
</p><p>
The people who have contributed to <a href="http://lists.w3.org/Archives/Public/public-ws-policy/">discussions
on public-ws-policy@w3.org</a> are also gratefully
@@ -1809,7 +1809,7 @@
Section <a href="#IRI_Policy_Attachment"><b>3.5 Use of IRIs in Policy Attachment</b></a>.</p></li></ul></div><div class="div1">
<h2><a name="change-log" id="change-log"></a>E. Web Services Policy 1.5 - Attachment Change Log (Non-Normative)</h2><a name="ws-policy-attachment-changelog-table"></a><table border="1"><tbody><tr><th rowspan="1" colspan="1">Date</th><th rowspan="1" colspan="1">Author</th><th rowspan="1" colspan="1">Description</th></tr><tr><td rowspan="1" colspan="1">20060712</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Updated the list of editors. Completed action items
<a href="http://www.w3.org/2006/07/12-ws-policy-minutes.html#action20">20</a>
- from the Austin F2F.</td></tr><tr><td rowspan="1" colspan="1">20060712</td><td rowspan="1" colspan="1">DBO</td><td rowspan="1" colspan="1">Completed action item <a href=" http://www.w3.org/2006/07/12-ws-policy-minutes.html#action12">12</a>
+ from the Austin F2F.</td></tr><tr><td rowspan="1" colspan="1">20060712</td><td rowspan="1" colspan="1">DBO</td><td rowspan="1" colspan="1">Completed action item <a href="http://www.w3.org/2006/07/12-ws-policy-minutes.html#action12">12</a>
</td></tr><tr><td rowspan="1" colspan="1">20060718</td><td rowspan="1" colspan="1">DBO</td><td rowspan="1" colspan="1">Completed action items
Editors to remove extraneous namespace decl in the example at the end of section 3.4 <a href="http://www.w3.org/2006/07/12-ws-policy-minutes.html#action18">18</a>,
RFC2606 for domain names <a href="http://www.w3.org/2006/07/12-ws-policy-minutes.html#action09">09</a> (note: PLH had already done but it didn't show up in the change log)
@@ -1932,7 +1932,6 @@
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/116">116</a> and
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/124">124</a>
Resolution for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4211">4211</a></td></tr><tr><td rowspan="1" colspan="1">20070117</td><td rowspan="1" colspan="1">FJH</td><td rowspan="1" colspan="1">Applied the resolution for issues 4045 and 4127 using <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4045#c2">first</a>
-
and <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4045#c3">second</a> parts as outlined in working group
<a href="http://www.w3.org/2007/01/17-ws-policy-irc#T22-50-02">resolution</a>. This closes editors actions
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/139">139</a> and
Received on Wednesday, 21 February 2007 20:09:51 UTC