- From: Asir Vedamuthu via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 28 Mar 2007 00:44:59 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv4399
Modified Files:
ws-policy-guidelines-diff20061221.html
ws-policy-attachment-diff20070228.html
ws-policy-framework-diff20070228.xml
ws-policy-guidelines-diff20061221.xml
ws-policy-attachment-diff20070228.xml
ws-policy-primer-diff20061221.xml
ws-policy-framework-diff20070228.html
ws-policy-primer-diff20061221.html
Log Message:
Regenerating the diff docs
Index: ws-policy-attachment-diff20070228.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment-diff20070228.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- ws-policy-attachment-diff20070228.html 23 Mar 2007 00:48:41 -0000 1.3
+++ ws-policy-attachment-diff20070228.html 28 Mar 2007 00:44:56 -0000 1.4
@@ -1,6 +1,6 @@
<!DOCTYPE html
PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en-US"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Policy 1.5 - Attachment -- Review Version</title><style type="text/css">
+<html lang="en-US"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title> -- Review Version</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
@@ -73,8 +73,9 @@
identify changes from a previous version. Three kinds of changes
are highlighted: <span class="diff-add">new, added text</span>,
<span class="diff-chg">changed text</span>, and
- <span class="diff-del">deleted text</span>.</p><hr></div><div class="head">
-<h1><a name="title" id="title"></a>Web Services Policy 1.5 - Attachment</h1>
+ <span class="diff-del">deleted text</span>. NOTE: the status section of the document has not been augmented to
+ identify changes from a previous version.</p><hr></div><div class="head">
+<h1><a name="title" id="title"></a></h1>
<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>
@@ -132,9 +133,9 @@
6.4 <a href="#RegisteringPoliciesUDDIVersion3">Registering Policies in UDDI Version 3</a><br>
7. <a href="#SecurityConsiderations">Security Considerations</a><br>
8. <a href="#Conformance">Conformance</a><br>
- 8.1 <a href="#d2e4012">External Policy Attachment Conformance</a><br>
- 8.2 <a href="#d2e4024">WSDL 1.1 Attachment Conformance</a><br>
- 8.3 <a href="#d2e4033">WSDL 2.0 Attachment Conformance</a><br>
+ 8.1 <a href="#d2e4011">External Policy Attachment Conformance</a><br>
+ 8.2 <a href="#d2e4023">WSDL 1.1 Attachment Conformance</a><br>
+ 8.3 <a href="#d2e4032">WSDL 2.0 Attachment Conformance</a><br>
</p>
<h3><a name="appendices" id="appendices"></a>Appendices</h3><p class="toc">A. <a href="#References">References</a><br>
A.1 <a href="#Normative-References">Normative References</a><br>
@@ -1503,11 +1504,11 @@
Security Considerations section of the Web Services Policy 1.5 - Framework document [<a href="#WS-Policy">[Web Services Policy Framework]</a>].
</p></div><div class="div1">
<h2><a name="Conformance" id="Conformance"></a>8. Conformance</h2><div class="div2">
-<h3><a name="d2e4012" id="d2e4012"></a>8.1 External Policy Attachment Conformance</h3><p>An element information item whose namespace name is "http://www.w3.org/ns/ws-policy" and whose local part is PolicyAttachment conforms to this specification if it is valid according to the XML Schema [<a href="#XMLSchemaPart1">[XML Schema Structures]</a>] for that element as defined by this specification (<a href="http://www.w3.org/2007/02/ws-policy.xsd">http://www.w3.org/2007/02/ws-policy.xsd</a>) and additionally adheres to all the constraints contained in Section <a href="#ExternalPolicyAttachment"><b>3.4 External Policy Attachment</b></a> of this specification. Such a conformant element information item constitutes an external policy attachment. </p></div><div class="div2">
-<h3><a name="d2e4024" id="d2e4024"></a>8.2 WSDL 1.1 Attachment Conformance</h3><p>
+<h3><a name="d2e4011" id="d2e4011"></a>8.1 External Policy Attachment Conformance</h3><p>An element information item whose namespace name is "http://www.w3.org/ns/ws-policy" and whose local part is PolicyAttachment conforms to this specification if it is valid according to the XML Schema [<a href="#XMLSchemaPart1">[XML Schema Structures]</a>] for that element as defined by this specification (<a href="http://www.w3.org/2007/02/ws-policy.xsd">http://www.w3.org/2007/02/ws-policy.xsd</a>) and additionally adheres to all the constraints contained in Section <a href="#ExternalPolicyAttachment"><b>3.4 External Policy Attachment</b></a> of this specification. Such a conformant element information item constitutes an external policy attachment. </p></div><div class="div2">
+<h3><a name="d2e4023" id="d2e4023"></a>8.2 WSDL 1.1 Attachment Conformance</h3><p>
A WSDL 1.1 [<a href="#WSDL11">[WSDL 1.1]</a>] description conforms to this specification when it incorporates one or more element policies and additionally adheres to all the constraints contained in section <a href="#AttachingPolicyUsingWSDL1.1"><b>4. Attaching Policies Using WSDL 1.1</b></a>
</p></div><div class="div2">
-<h3><a name="d2e4033" id="d2e4033"></a>8.3 WSDL 2.0 Attachment Conformance</h3><p>
+<h3><a name="d2e4032" id="d2e4032"></a>8.3 WSDL 2.0 Attachment Conformance</h3><p>
A WSDL 2.0 [<a href="#WSDL20">[WSDL 2.0 Core Language]</a>] description conforms to this specification when it incorporates one or more element policies and additionally adheres to all the constraints contained in section <a href="#ws-policy-attachment-for-wsdl20"><b>5. WS-Policy Attachment for WSDL 2.0</b></a>
</p></div></div></div><div class="back"><div class="div1">
<h2><a name="References" id="References"></a>A. References</h2><div class="div2">
@@ -1641,11 +1642,12 @@
(See http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/.)</dd></dl></div><div class="div2">
<h3><a name="Informative-References" id="Informative-References"></a>A.2 Other References</h3><dl><dt class="label"><a name="RFC2246" id="RFC2246"></a>[IETF RFC 2246] </dt><dd>IETF
"RFC 2246: The TLS Protocol", T. Dierks, C. Allen, January
- 1999. (See http://www.ietf.org/rfc/rfc2246.txt.)</dd><dt class="label"><a name="WSDL11EI" id="WSDL11EI"></a>[WSDL11 ElementIds] </dt><dd>
- <a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/wsdl11elementidentifiers.html"><cite>WSDL 1.1 Element Identifiers</cite></a>
- D. Orchard, Editor. World Wide Web Consortium, 15 November 2006.
- TBD: URI
- (See http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/wsdl11elementidentifiers.html.)</dd><dt class="label"><a name="MTOM" id="MTOM"></a>[MTOM] </dt><dd>
+ 1999. (See http://www.ietf.org/rfc/rfc2246.txt.)</dd><dt class="label"><span class="diff-chg"><a name="WSDL11EI"></a>WSDL11 ElementIds</span></dt><dd><div class="diff-chg">
+ <a href="http://www.w3.org/TR/2007/WD-wsdl11elementidentifiers-20070330/"><cite>WSDL 1.1 Element Identifiers</cite></a>
+ D. Orchard, <span class="diff-add"><span>A. S. Vedamuthu, F. Hirsch, M. Hondo, P. Yendluri, T.</span></span><span class="diff-del"><span>Editor. </span></span><span class="diff-add"><span>Boubez, Ü. Yalçinalp, Editors. </span></span>World Wide Web Consortium, <span class="diff-chg"><span>30 March </span></span><span class="diff-add"><span>2007.</span></span><span class="diff-del"><span>2006.
+ TBD: </span></span><span class="diff-add"><span>This version of the WSDL 1.1 Element Identifiers Working Draft is http://www.w3.org/TR/2007/WD-wsdl11elementidentifiers-20070330/. The </span></span><div class="diff-add"><a href="http://www.w3.org/TR/wsdl11elementidentifiers/"><span class="diff-add"><span>latest version of WSDL 1.1 Element Identifiers</span></span></a></div> <span class="diff-add"><span>is available at http://www.w3.org/TR/wsdl11elementidentifiers/. </span></span> (See http://www.w3.org/TR/2007/WD-wsdl11elementidentifiers-20070330/.)</div></dd><span class="diff-del"><span>URI
+
+</span></span><dt class="label"><a name="MTOM" id="MTOM"></a>[MTOM] </dt><dd>
<a href="http://www.w3.org/TR/2005/REC-soap12-mtom-20050125/"><cite>SOAP Message Transmission Optimization Mechanism</cite></a>, M. Gudgin, N.
Mendelsohn, M. Nottingham and H. Ruellan, Editors. World Wide Web Consortium, 25 January
2005. This version of the SOAP Message Transmission Optimization Mechanism Recommendation
Index: ws-policy-primer-diff20061221.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer-diff20061221.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- ws-policy-primer-diff20061221.html 23 Mar 2007 00:48:42 -0000 1.4
+++ ws-policy-primer-diff20061221.html 28 Mar 2007 00:44:57 -0000 1.5
@@ -1,6 +1,6 @@
<!DOCTYPE html
PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en-US"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Policy 1.5 - Primer -- Review Version</title><style type="text/css">
+<html lang="en-US"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title> -- Review Version</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
@@ -73,12 +73,13 @@
identify changes from a previous version. Three kinds of changes
are highlighted: <span class="diff-add">new, added text</span>,
<span class="diff-chg">changed text</span>, and
- <span class="diff-del">deleted text</span>.</p><hr></div><div class="head">
-<h1><a name="title" id="title"></a>Web Services Policy 1.5 - Primer</h1>
+ <span class="diff-del">deleted text</span>. NOTE: the status section of the document has not been augmented to
+ identify changes from a previous version.</p><hr></div><div class="head">
+<h1><a name="title" id="title"></a></h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a>Editors' copy $Date$ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
<a href="ws-policy-primer.html">ws-policy-primer.html</a>
</dd><dt>Latest version:</dt><dd><a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-primer.html?content-type=text/html;charset=utf-8">http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-primer.html?content-type=text/html;charset=utf-8</a></dd><div class="diff-add"><dt>Previous version:</dt><dd>
- <a href="http://www.w3.org/TR/2006/WD-ws-policy-guidelines-20061221"><span class="diff-add"><span>http://www.w3.org/TR/2006/WD-ws-policy-guidelines-20061221</span></span></a>
+ <a href="http://www.w3.org/TR/2006/WD-ws-policy-primer-20061221"><span class="diff-add"><span>http://www.w3.org/TR/2006/WD-ws-policy-primer-20061221</span></span></a>
</dd></div><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">traemark</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>
<em>Web Services Policy 1.5 - Primer</em> is an introductory description of the Web Services Policy
@@ -375,8 +376,8 @@
<sp:AsymmetricBinding>…</sp:AsymmetricBinding>
</ExactlyOne>
</All></pre></div></div><p><span class="diff-chg"><span>Company-X </span></span>is able to meet their customer needs by adding optional support for the Optimized
- <span class="diff-del"><span>MIME </span></span><span class="diff-add"><span>MIME
- </span></span>Serialization. <span class="diff-add"><span>Optional support is outlined in section 3.4 Web Services Policy 1.5 - Framework and
+ MIME
+ Serialization. <span class="diff-add"><span>Optional support is outlined in section 3.4 Web Services Policy 1.5 - Framework and
detailed in section 4.5.2, Web Services Policy 1.5 - Guidelines for Policy Assertion Authors, specifically for Optimized MIME Serialization.
</span></span>An optional policy assertion represents a behavior that may be engaged. <span class="diff-add"><span>When a
policy assertion is absent from a policy vocabulary (See section 3.2, Web Services Policy 1.5 - Framework),
@@ -998,7 +999,7 @@
<span class="diff-add"><span>extensibility. The </span></span><span class="diff-add"><code><span class="diff-add"><span>PolicyReference</span></span></code></span> <span class="diff-add"><span>child element allows element
</span></span>and attribute extensibility. Extensions must not use the policy language XML namespace name.
A consuming processor processes known attributes and elements, ignores unknown attributes
- and treats unknown <span class="diff-add"><span>children of the </span></span><span class="diff-add"><code><span class="diff-add"><span>Policy</span></span></code></span><span class="diff-add"><span>, </span></span><span class="diff-add"><code><span class="diff-add"><span>ExactlyOne</span></span></code></span><span class="diff-add"><span>, </span></span><span class="diff-add"><code><span class="diff-add"><span>All</span></span></code></span>
+ and treats unknown <span class="diff-add"><span>children of the </span></span><span class="diff-add"><code><span class="diff-add"><span>Policy</span></span></code></span><span class="diff-add"><span>, </span></span><span class="diff-add"><code><span class="diff-add"><span>ExactlyOne</span></span></code></span>, <span class="diff-add"><code><span class="diff-add"><span>All</span></span></code></span>
elements as policy assertions. <span class="diff-add"><span>The child elements of </span></span><span class="diff-add"><code><span class="diff-add"><span>wsp:PolicyReference</span></span></code></span> <span class="diff-add"><span>are ignored.
</span></span></p><p>The <code>PolicyReference</code> element allows element and attribute extensibility.</p><p>Web Services Policy language enables simple versioning practices that allow requesters to
@@ -1584,6 +1585,4 @@
for <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4300"><span class="diff-add"><span>issue 4300</span></span></a>.
Editors' action
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/190"><span class="diff-add"><span>190</span></span></a>.
- </td></div></tr></div><div class="diff-add"><tr class="diff-add"><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">20070321</td></div><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">ASV</td></div><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">Updated section <a href="#change-description"><b>E. Changes in this Version of the Document</b></a>. </td></div></tr></div><div class="diff-add"><tr class="diff-add"><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">20070321</td></div><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">ASV</td></div><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">Formatted the example in <a href="#ignorable-and-versioning"><b>3.8.1 Ignorable and Versioning</b></a>. </td></div></tr></div><div class="diff-add"><tr class="diff-add"><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">20070322</td></div><div class="diff-add"><td rowspan="1" colspan="1" class"diff-add">ASV</td></div><td rowspan="1" colspan="1"><p><span class="diff-add"><span>Deleted residual text in </span></span><a href="#versioning-policy-language"><b>4. Versioning Policy Language</b></a><span class="diff-add"><span>:</span></span></p>
- <p><span class="diff-add"><span>s/The possible extensibility points with their current extensibility - including some outstanding issues related to extensibility - are:/The possible extensibility points are:/</span></span></p>
- <p><span class="diff-add"><span>s/PolicyReference: any attribute and a proposal to add any element/PolicyReference: any attribute and any element/.</span></span></p></td></tr></div></tbody></table><br></div></div></body></html>
\ No newline at end of file
+ </td></div></tr></div><div class="diff-add"><tr class="diff-add"><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">20070321</td></div><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">ASV</td></div><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">Updated section <a href="#change-description"><b>E. Changes in this Version of the Document</b></a>. </td></div></tr></div><div class="diff-add"><tr class="diff-add"><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">20070321</td></div><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">ASV</td></div><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">Formatted the example in <a href="#ignorable-and-versioning"><b>3.8.1 Ignorable and Versioning</b></a>. </td></div></tr></div><div class="diff-add"><tr class="diff-add"><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">20070322</td></div><div class="diff-add"><td rowspan="1" colspan="1" class"diff-add">ASV</td></div><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">Deleted residual text in <a href="#versioning-policy-language"><b>4. Versioning Policy Language</b></a>; <code><span class="diff-add"><span>s/The possible extensibility points with their current extensibility - including some outstanding issues related to extensibility - are:/The possible extensibility points are:/</span></span></code> ; <code><span class="diff-add"><span>s/PolicyReference: any attribute and a proposal to add any element/PolicyReference: any attribute and any element/</span></span></code>.</td></div></tr></div></tbody></table><br></div></div></body></html>
\ No newline at end of file
Index: ws-policy-primer-diff20061221.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer-diff20061221.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- ws-policy-primer-diff20061221.xml 23 Mar 2007 00:48:41 -0000 1.4
+++ ws-policy-primer-diff20061221.xml 28 Mar 2007 00:44:57 -0000 1.5
@@ -1,253 +1,124 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- $Id$ -->
-<!DOCTYPE spec PUBLIC "-//W3C//DTD Specification V2.10//EN" "xmlspec.dtd" [
-<!ENTITY prefix "ws-policy-primer">
-<!ENTITY % entities SYSTEM "entities.dtd" >
-%entities;
-<!ENTITY status SYSTEM "status-primer.xml">
-<!ENTITY document.status.primer "Editors' copy $Date$">
-<!ENTITY primer-title "&primer.title;">
-<!ENTITY prevloc "http://www.w3.org/TR/2006/WD-ws-policy-guidelines-20061221">
-<!ENTITY hellip "…">
[...2785 lines suppressed...]
- <td rowspan="1" colspan="1" diff="add">20070321</td>
- <td rowspan="1" colspan="1" diff="add">ASV</td>
- <td rowspan="1" colspan="1" diff="add">Formatted the example in <specref ref="ignorable-and-versioning"></specref>. </td>
- </tr>
- <tr diff="add">
- <td rowspan="1" colspan="1" diff="add">20070322</td>
- <td rowspan="1" colspan="1" diff="add">ASV</td>
- <td rowspan="1" colspan="1"><p><phrase diff="add">Deleted residual text in </phrase><specref ref="versioning-policy-language"></specref><phrase diff="add">:</phrase></p>
- <p><phrase diff="add">s/The possible extensibility points with their current extensibility - including some outstanding issues related to extensibility - are:/The possible extensibility points are:/</phrase></p>
- <p><phrase diff="add">s/PolicyReference: any attribute and a proposal to add any element/PolicyReference: any attribute and any element/.</phrase></p></td>
- </tr>
-
- </tbody>
- </table>
- </inform-div1>
- </back>
-</spec>
+ <loc xmlns:xlink="http://www.w3.org/1999/xlink" href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/190" xlink:type="simple" xlink:actuate="onRequest" xlink:show="replace"><phrase diff="add">190</phrase></loc>.
+ </td></tr><tr diff="add"><td rowspan="1" colspan="1" diff="add">20070321</td><td rowspan="1" colspan="1" diff="add">ASV</td><td rowspan="1" colspan="1" diff="add">Updated section <specref ref="change-description"/>. </td></tr><tr diff="add"><td rowspan="1" colspan="1" diff="add">20070321</td><td rowspan="1" colspan="1" diff="add">ASV</td><td rowspan="1" colspan="1" diff="add">Formatted the example in <specref ref="ignorable-and-versioning"/>. </td></tr><tr diff="add"><td rowspan="1" colspan="1" diff="add">20070322</td><td rowspan="1" colspan="1" diff="add">ASV</td><td rowspan="1" colspan="1" diff="add">Deleted residual text in <specref ref="versioning-policy-language"/>; <code><phrase diff="add">s/The possible extensibility points with their current extensibility - including some outstanding issues related to extensibility - are:/The possible extensibility points are:/</phrase></code> ; <code><phrase diff="add">s/PolicyReference: any attribute and a proposal to add any element/PolicyReference: ny attribute and any element/</phrase></code>.</td></tr></tbody></table></inform-div1></back></spec>
\ No newline at end of file
Index: ws-policy-framework-diff20070228.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework-diff20070228.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- ws-policy-framework-diff20070228.html 23 Mar 2007 00:48:42 -0000 1.3
+++ ws-policy-framework-diff20070228.html 28 Mar 2007 00:44:57 -0000 1.4
@@ -1,6 +1,6 @@
<!DOCTYPE html
PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en-US"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Policy 1.5 - Framework -- Review Version</title><style type="text/css">
+<html lang="en-US"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title> -- Review Version</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
@@ -73,16 +73,17 @@
identify changes from a previous version. Three kinds of changes
are highlighted: <span class="diff-add">new, added text</span>,
<span class="diff-chg">changed text</span>, and
- <span class="diff-del">deleted text</span>.</p><hr></div><div class="head">
-<h1><a name="title" id="title"></a>Web Services Policy 1.5 - Framework</h1>
+ <span class="diff-del">deleted text</span>. NOTE: the status section of the document has not been augmented to
+ identify changes from a previous version.</p><hr></div><div class="head">
+<h1><a name="title" id="title"></a></h1>
<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>
<div class="diff-chg"><a href="http://www.w3.org/TR/2007/CR-ws-policy-20070228"><span class="diff-chg"><span>http://www.w3.org/TR/2007/CR-ws-policy-20070228</span></span></a></div>
</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
- <span class="diff-del"><span>syntax </span></span><span class="diff-add"><span>syntax
- </span></span>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
+ 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
requirements and capabilities.</p></div><div>
<h2><a name="status" id="status"></a>Status of this Document</h2><p><strong>This document is an editors' copy that has
@@ -139,8 +140,8 @@
representation of its policy, either in a normal form or in its equivalent compact
form. Some policy assertions specify traditional requirements and capabilities that
will manifest themselves in the messages exchanged(e.g., authentication
- <span class="diff-del"><span>scheme, </span></span><span class="diff-add"><span>scheme,
- </span></span>transport protocol selection). Other policy assertions have no wire manifestation in
+ scheme,
+ transport protocol selection). Other policy assertions have no wire manifestation in
the messages exchanged, yet are relevant to service selection and usage (e.g.,
privacy policy, QoS characteristics). Web Services Policy 1.5 - Framework provides a single policy
language to allow both kinds of assertions to be expressed and evaluated in a
@@ -184,8 +185,8 @@
<h3><a name="Notational_Conventions" id="Notational_Conventions"></a>2.1 Notational Conventions</h3><p>This specification uses the following syntax within normative outlines: </p><ul><li><p>The syntax appears as an XML instance, but values in <em>italics</em>
indicate data types instead of literal values.</p></li><li><p>Characters are appended to elements and attributes to indicate
cardinality:</p><ul><li><p>"?" (0 or 1)</p></li><li><p>"*" (0 or more)</p></li><li><p>"+" (1 or more)</p></li></ul></li><li><p>The character "|" is used to indicate an exclusive choice
- <span class="diff-del"><span>between </span></span><span class="diff-add"><span>between
- </span></span>alternatives.</p></li><li><p>The characters "(" and ")" are used to indicate that contained items are
+ between
+ alternatives.</p></li><li><p>The characters "(" and ")" are used to indicate that contained items are
to be treated as a group with respect to cardinality or choice.</p></li><li><p>This document relies on the XML Information Set [<a href="#XMLInfoset">[XML Information Set]</a>]. Information item properties are indicated by the style <em>infoset property</em>.</p></li><li><p>XML namespace prefixes (see <a href="#nsprefix">Table 2-1</a>) are used to
indicate the namespace of the element or attribute being defined.</p></li><li><p>The ellipses characters "…" are used to indicate a point of
extensibility that allows other Element or Attribute Information
@@ -234,21 +235,21 @@
Proposed Recommendation and Recommendation status. However, should the
specifications revert to Working Draft status, and a subsequent revision,
published as a WD, CR or PR draft, results in non-backwardly compatible
- <span class="diff-del"><span>changes </span></span><span class="diff-add"><span>changes
- </span></span>from a previously published WD, CR or PR draft of the specification,
- <span class="diff-del"><span>the </span></span><span class="diff-add"><span>the
- </span></span>namespace URI will be changed accordingly.</p><p>Under this policy, the following are examples of backwards compatible
- <span class="diff-del"><span>changes </span></span><span class="diff-add"><span>changes
- </span></span>that would not result in assignment of a new XML namespace URI:</p><ul><li><p>Addition of new global element, attribute, complexType and simpleType
+ changes
+ from a previously published WD, CR or PR draft of the specification,
+ the
+ namespace URI will be changed accordingly.</p><p>Under this policy, the following are examples of backwards compatible
+ changes
+ that would not result in assignment of a new XML namespace URI:</p><ul><li><p>Addition of new global element, attribute, complexType and simpleType
definitions.</p></li><li><p>Addition of new elements or attributes in locations covered by a
previously specified wildcard.</p></li><li><p>Modifications to the pattern facet of a type definition for which the
value-space of the previous definition remains valid or for which the
value-space of the vast majority of instances would remain valid.</p></li><li><p>Modifications to the cardinality of elements (i.e. modifications to
minOccurs or maxOccurs attribute value of an element declaration)
- <span class="diff-del"><span>for </span></span><span class="diff-add"><span>for
- </span></span>which the value-space of possible instance documents conformant to
- <span class="diff-del"><span>the </span></span><span class="diff-add"><span>the
- </span></span>previous revision of the schema would still be valid with regards to the
+ for
+ which the value-space of possible instance documents conformant to
+ the
+ previous revision of the schema would still be valid with regards to the
revised cardinality rule.</p></li></ul></div><div class="div2">
<h3><a name="Terminology" id="Terminology"></a>2.4 Terminology</h3><p> The keywords "<span class="rfc2119">MUST</span>", "<span class="rfc2119">MUST NOT</span>",
"<span class="rfc2119">REQUIRED</span>", "<span class="rfc2119">SHALL</span>", "<span class="rfc2119">SHALL
@@ -324,8 +325,8 @@
Intersection</a>).] By default, an assertion is not
ignorable for policy intersection. </p><p>Assertions are typed by the authors that define them. [<a name="policy_assertion_type" id="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
- <span class="diff-del"><span>schema </span></span><span class="diff-add"><span>schema
- </span></span>for the assertion and assertion-specific semantics.] The <a title="policy assertion type" href="#policy_assertion_type">policy assertion type</a> is identified
+ schema
+ for the assertion and assertion-specific semantics.] The <a title="policy assertion type" href="#policy_assertion_type">policy assertion type</a> is identified
only by the XML Infoset <em>namespace name</em> and
<em>local name</em> properties (that is, the
qualified name or QName) of the root Element Information Item representing the
@@ -349,8 +350,8 @@
assertions containing <a title="policy assertion parameter" href="#policy_assertion_parameter">policy assertion
parameters</a> or <a title="nested policy expression" href="#nested_policy_expression">nested
policy expressions</a>. Specifically, authors are encouraged
- <span class="diff-del"><span>to </span></span><span class="diff-add"><span>to
- </span></span>consider when the identity of the root Element Information Item alone is enough
+ to
+ consider when the identity of the root Element Information Item alone is enough
to convey the requirement or capability.</p></div><div class="div2">
<h3><a name="rPolicy_Alternative" id="rPolicy_Alternative"></a>3.2 Policy Alternative</h3><p>[<a name="policy_alternative" id="policy_alternative" title="policy alternative">Definition</a>: A <b>policy
alternative</b> is a potentially empty collection of <a title="policy assertion" href="#policy_assertion">policy assertions</a>.] An
@@ -369,8 +370,8 @@
order in which behaviors (indicated by assertions) are applied to a <a title="policy subject" href="#policy_subject">subject</a> are beyond the scope of this
specification. However, authors can write assertions that control the order in
which behaviours are applied.</p><p>A policy alternative <span class="rfc2119">MAY</span> contain multiple assertions of
- <span class="diff-del"><span>the </span></span><span class="diff-add"><span>the
- </span></span>same type. Mechanisms for determining the aggregate behavior indicated by the
+ the
+ same type. Mechanisms for determining the aggregate behavior indicated by the
assertions (and their Post-Schema-Validation Infoset (PSVI) (See XML Schema Part
1 [<a href="#XMLSchemaPart1">[XML Schema Structures]</a>]) content, if any) are specific to the
assertion type and are outside the scope of this document.</p><p>Note: Depending on the semantics of the domain specific policy assertions a
@@ -379,8 +380,8 @@
<h3><a name="rPolicy" id="rPolicy"></a>3.3 Policy</h3><p>[<a name="policy" id="policy" title="policy">Definition</a>: A <b>policy</b> is a potentially empty
collection of <a title="policy alternative" href="#policy_alternative">policy
alternatives</a>. ] A policy with zero alternatives
- <span class="diff-del"><span>contains </span></span><span class="diff-add"><span>contains
- </span></span>no choices; a policy with one or more alternatives indicates choice in
+ contains
+ no choices; a policy with one or more alternatives indicates choice in
requirements or capabilities within the policy. </p><p>Alternatives are not ordered, and thus aspects such as preferences between
alternatives in a given context are beyond the scope of this specification. </p><p>Alternatives within a policy may differ significantly in terms of the behaviors
they indicate. Conversely, alternatives within a policy may be very similar. In
@@ -390,8 +391,8 @@
<h3><a name="Web_services" id="Web_services"></a>3.4 Policies of Entities in a Web Services Based System</h3><p>Applied to a Web services based system, <a title="policy" href="#policy">policy</a> is
used to convey conditions on an interaction between entities (requester
application, provider service, Web infrastructure component, etc).
- <span class="diff-del"><span>An </span></span><span class="diff-add"><span>An
- </span></span>interaction involves one or more message exchanges between two entities. It is
+ An
+ interaction involves one or more message exchanges between two entities. It is
the responsibility of <a title="policy assertion" href="#policy_assertion">assertion</a>
authors to define the interaction scope of an assertion including any
constraints on the <a title="policy subject" href="#policy_subject">policy subjects</a> to
@@ -400,16 +401,16 @@
conditions under which it functions. Satisfying assertions in the policy usually
results in behavior that reflects these conditions. For example, if two entities
- requester and provider - expose their policies, a requester might use
- <span class="diff-del"><span>the </span></span><span class="diff-add"><span>the
- </span></span>policy of the provider to decide whether or not to use the service. A requester
+ the
+ policy of the provider to decide whether or not to use the service. A requester
<span class="rfc2119">MAY</span> choose any alternative since each is a valid
configuration for interaction with the service, but a requester
<span class="rfc2119">MUST</span> choose only a single alternative for an interaction with
a service since each represents an alternative configuration.</p><p>A <a title="policy assertion" href="#policy_assertion">policy assertion</a> is supported by an
entity in the web services based system if and only if the entity satisfies the
requirement (or accommodates the capability) corresponding to the assertion.
- <span class="diff-del"><span>A </span></span><span class="diff-add"><span>A
- </span></span><a title="policy alternative" href="#policy_alternative">policy alternative</a> is supported
+ A
+ <a title="policy alternative" href="#policy_alternative">policy alternative</a> is supported
by an entity if and only if the entity supports all the assertions in the
alternative. And, a <a title="policy" href="#policy">policy</a> is supported by an
entity if and only if the entity supports at least one of the alternatives in
@@ -424,8 +425,8 @@
versioning and incremental deployment of new assertions because this allows a
provider's policy to include new assertions in new alternatives while allowing
entities to continue to use old alternatives in a
- <span class="diff-del"><span>backward-compatible </span></span><span class="diff-add"><span>backward-compatible
- </span></span>manner.</p></div></div><div class="div1">
+ backward-compatible
+ manner.</p></div></div><div class="div1">
<h2><a name="rPolicy_Expression" id="rPolicy_Expression"></a>4. Policy Expression</h2><p>This section describes how to convey <a title="policy" href="#policy">policy</a> in an
interoperable form, using the XML Infoset representation of a policy. [<a name="policy_expression" id="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>,
@@ -518,8 +519,8 @@
Canonical XML 1.0 is inappropriate as described in Appendix C of
xml:id Version 1.0 [<a href="#XMLID">[XML ID]</a>] and thus this combination
must be avoided (see [<a href="#C14NNOTE">[C14N 1.0 Note]</a>]). For example,
- <span class="diff-del"><span>a </span></span><span class="diff-add"><span>a
- </span></span>policy expression identified using <code>xml:id</code> attribute
+ a
+ policy expression identified using <code>xml:id</code> attribute
should not be signed using XML Digital Signature when Canonical XML
1.0 is being used as the canonicalization method.</p></div></div><div class="diff-add"><div class="note"><p class="prefix"><b>Note:</b></p><p><span class="diff-add"><span>Canonical XML 1.1 [</span></span><a href="#XMLID11">[XMLID11]</a><span class="diff-add"><span>] is intended to
address the issues that occur with Canonical XML 1.0 with regards to
@@ -580,8 +581,8 @@
(06) <wsp:All />
(07) </wsp:ExactlyOne>
(08) </wsp:Policy></pre></div><p>The <code>@wsp:Optional</code> attribute in Line (02) of the first
-<span class="diff-del"><span>policy </span></span><span class="diff-add"><span>policy
- </span></span>expression indicates that the assertion in Line (02) is to be included in a
+policy
+ expression indicates that the assertion in Line (02) is to be included in a
policy alternative whilst excluded from another; it is included in Lines
(03-05) and excluded in Line (06). Note that <code>@wsp:Optional</code> does
not appear in the normal form of a policy expression.</p></div><div class="div3">
@@ -608,20 +609,23 @@
expression), the assertion <span class="rfc2119">MUST</span> include an
empty <code><wsp:Policy/></code> Element
Information Item in its <em>children</em> property; as explained in Section <a href="#Policy_Operators"><b>4.3.3 Policy Operators</b></a>, this is equivalent to a
-<span class="diff-del"><span>nested </span></span><span class="diff-add"><span>nested
- </span></span>policy expression with a single alternative that has zero
+nested
+ policy expression with a single alternative that has zero
assertions.</p><p>Note: This specification does not define processing for arbitrary
<code>wsp:Policy</code> Element Information Items in the
descendants of an assertion parameter, e.g., in the <em>children</em> property of one of
- the <em>children</em> as in: <div class="exampleInner"><pre><span class="diff-chg"><span>
- (01)<wsp:Policy> (02) <Lorem>
- (03) <Ipsum> (04)
- <wsp:Policy> (05) … (06)
- </wsp:Policy> (07) </Ipsum> (08)
- </Lorem>
- (09)</wsp:Policy></span></span></pre></div>.</p></dd></dl><p>Policy assertions containing a nested policy expression are
-<span class="diff-del"><span>normalized </span></span><span class="diff-add"><span>normalized
- </span></span>recursively. The nesting of a policy expression (and a <code>wsp:Policy</code>
+ the <em>children</em> as in: <div class="exampleInner"><pre>
+(01)<wsp:Policy>
+(02) <Lorem>
+(03) <Ipsum>
+(04) <wsp:Policy>
+(05) …
+(06) </wsp:Policy>
+(07) </Ipsum>
+(08) </Lorem>
+(09)</wsp:Policy></pre></div>.</p></dd></dl><p>Policy assertions containing a nested policy expression are
+normalized
+ recursively. The nesting of a policy expression (and a <code>wsp:Policy</code>
child) is retained in the normal form, but in the normal form, each nested
policy expression contains at most one policy alternative. If an assertion A
contains a nested policy expression E, and if E contains more than one
@@ -630,8 +634,8 @@
contains a single choice. This process is applied recursively to the
assertions within those choices and to their nested policy expression, if
any. Intuitively, if a compact policy is thought of as a tree whose
-<span class="diff-del"><span>branches </span></span><span class="diff-add"><span>branches
- </span></span>have branches etc, in the normal form, a policy is a stump with straight
+branches
+ have branches etc, in the normal form, a policy is a stump with straight
vines.</p><p>For example, consider the following policy expression with nested policy
expressions in a compact form:</p><div class="exampleInner"><pre>(01) <wsp:Policy
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
@@ -655,10 +659,10 @@
(17) </wsp:Policy>
(18) </sp:TransportBinding>
(19) </wsp:Policy></pre></div><p>Lines (02-18) in this policy expression contain a single transport
-<span class="diff-del"><span>binding </span></span><span class="diff-add"><span>binding
- </span></span>security policy assertion; within its nested policy expression
-<span class="diff-del"><span>(Lines </span></span><span class="diff-add"><span>(Lines
- </span></span>03-17), is an algorithm suite assertion (Lines 04-11) whose nested policy
+binding
+ security policy assertion; within its nested policy expression
+(Lines
+ 03-17), is an algorithm suite assertion (Lines 04-11) whose nested policy
expression (Lines 05-10) contains two policy alternatives (Lines 07-08).
Generally, a nested policy expression implies recursive processing; in the
example above, the behavior indicated by the transport binding assertion
@@ -703,8 +707,8 @@
(34) </wsp:All>
(35) </wsp:ExactlyOne>
(36) </wsp:Policy></pre></div><p>In the listing above, the transport binding and its nested policy
-<span class="diff-del"><span>expression </span></span><span class="diff-add"><span>expression
- </span></span>have been duplicated once for each of the nested alternatives in Lines
+expression
+ have been duplicated once for each of the nested alternatives in Lines
(07-08) of the compact policy. The first alternative (Lines 03-18) contains
a single nested algorithm suite alternative (Line 08) as does the second
alternative (Lines 19-34 and 24). </p></div><div class="div3">
@@ -712,8 +716,8 @@
capabilities, requirements, and general characteristics of entities (see
<a href="#tocRange"><b>1. Introduction</b></a>). These are generally expressible as a set of
<a title="policy alternative" href="#policy_alternative">policy alternatives</a>.
- <span class="diff-del"><span>Policy </span></span><span class="diff-add"><span>Policy
- </span></span>operators (<code>wsp:Policy</code>, <code>wsp:All</code> and <code>wsp:ExactlyOne</code>
+ Policy
+ operators (<code>wsp:Policy</code>, <code>wsp:All</code> and <code>wsp:ExactlyOne</code>
elements) are used to group <a title="policy assertion" href="#policy_assertion">policy
assertions</a> into <a title="policy alternative" href="#policy_alternative">policy
alternatives</a>. To compactly express complex policies, policy
@@ -959,21 +963,21 @@
<span class="rfc2119">SHOULD</span> be an IRI-reference to a policy
expression identified by an <code>ID</code>. For an external
policy expression, there is no requirement that the IRI
-<span class="diff-del"><span>be </span></span><span class="diff-add"><span>be
- </span></span>resolvable; retrieval mechanisms are beyond the scope of this
+be
+ resolvable; retrieval mechanisms are beyond the scope of this
specification. After retrieval, there is no requirement to check
that the retrieved policy expression is associated (Section
<a href="#Policy_Identification"><b>4.2 Policy Identification</b></a>) with this IRI.
-<span class="diff-del"><span>The </span></span><span class="diff-add"><span>The
- </span></span>IRI included in the retrieved policy expression, if any,
+The
+ IRI included in the retrieved policy expression, if any,
<span class="rfc2119">MAY</span> be different than the IRI used to
retrieve the policy expression. </p></dd><dt class="label">
<code>/wsp:PolicyReference/@Digest</code>
</dt><dd><p>This attribute is of type <code>xs:base64Binary</code> and
specifies the digest of the referenced policy expression. This
is used to ensure the included policy is the expected policy.
- <span class="diff-del"><span>If </span></span><span class="diff-add"><span>If
- </span></span>omitted, there is no implied value.</p></dd><dt class="label">
+ If
+ omitted, there is no implied value.</p></dd><dt class="label">
<code>/wsp:PolicyReference/@DigestAlgorithm</code>
</dt><dd><p>This optional URI attribute specifies the digest algorithms being
used. This specification predefines the default algorithm below,
@@ -1039,11 +1043,11 @@
in an interoperable form, a compact expression may be converted to the
corresponding normal form expression by the following procedure:</p><ol class="enumar"><li><p>Start with the Element Information Item E (as defined in the XML
Information Set [<a href="#XMLInfoset">[XML Information Set]</a>]) of the
- <span class="diff-del"><span>policy </span></span><span class="diff-add"><span>policy
- </span></span>expression. The <em>namespace name</em>
+ policy
+ expression. The <em>namespace name</em>
of E is always <code>"http://www.w3.org/ns/ws-policy"</code>. In the base case,
- <span class="diff-del"><span>the </span></span><span class="diff-add"><span>the
- </span></span><em>local name</em> property of E is
+ the
+ <em>local name</em> property of E is
<code>"Policy"</code>; in the recursive case, the <em>local name</em> property of E is
<code>"Policy"</code>, <code>"ExactlyOne"</code>, or
<code>"All"</code>.</p></li><li><p>Expand Element Information Items (as defined in the XML Information
@@ -1056,8 +1060,8 @@
operator; normalize C by recursively applying this
procedure.</p></li><li><p>Otherwise the Element Information Item C is an assertion;
normalize C per Sections <a href="#Optional_Policy_Assertions"><b>4.3.1 Optional Policy Assertions</b></a> and <a href="#Policy_Assertion_Nesting"><b>4.3.2 Policy Assertion Nesting</b></a>.</p></li></ol></li><li><p>Apply the policy operator indicated by E to the normalized
- <span class="diff-del"><span>Element </span></span><span class="diff-add"><span>Element
- </span></span>Information Items in its <em>children</em> property and construct a normal form per Section
+ Element
+ Information Items in its <em>children</em> property and construct a normal form per Section
<a href="#Policy_Operators"><b>4.3.3 Policy Operators</b></a> and <a href="#Normal_Form_Policy_Expression"><b>4.1 Normal Form Policy Expression</b></a>.</p></li></ol><p>Note that an implementation may use a more efficient procedure and is not
required to explicitly convert a compact expression into the normal form as
long as the processing results are indistinguishable from doing so.</p></div></div><div class="div2">
@@ -1182,8 +1186,8 @@
when the behavior associated with <code>sp:SignedParts</code> is invoked, the
contents of both assertions are used to indicate the correct behavior. Whether
these two assertions are compatible depends on the domain-specific semantics
-<span class="diff-del"><span>of </span></span><span class="diff-add"><span>of
- </span></span>the <code>sp:SignedParts</code> assertion. To leverage intersection, assertion
+of
+ the <code>sp:SignedParts</code> assertion. To leverage intersection, assertion
authors are encouraged to factor assertions such that two assertions of the same
assertion type are always (or at least typically) compatible.</p></div><div class="div2">
<h3><a name="IRI_Policy_Expressions" id="IRI_Policy_Expressions"></a>4.6 Use of IRIs in Policy Expressions</h3><p>Policy expressions use IRIs for some identifiers. This document does not define a
@@ -1204,8 +1208,8 @@
object-specific security mechanisms.</p><p>This section describes the security considerations that service providers,
requestors, policy authors, policy assertion authors, and policy implementers need
to consider when exposing, consuming and designing <a title="policy expression" href="#policy_expression">policy expressions</a>, authoring policy assertions or
- <span class="diff-del"><span>implementing </span></span><span class="diff-add"><span>implementing
- </span></span>policy.</p><div class="div2">
+ implementing
+ policy.</p><div class="div2">
<h3><a name="information-disclosure-threats" id="information-disclosure-threats"></a>5.1 Information Disclosure Threats</h3><p>A policy is used to represent the capabilities and requirements of a Web Service.
Policies may include sensitive information. Malicious consumers may acquire
sensitive information, fingerprint the service and infer service
@@ -1233,8 +1237,8 @@
a malicious activity. For example, say the policy assertion is privacy notice
information and the provider violates the semantics by disclosing private
information. Requestors can mitigate this threat by discarding
- <span class="diff-del"><span>policy </span></span><span class="diff-add"><span>policy
- </span></span>alternatives which include assertions whose behavior cannot be verified by
+ policy
+ alternatives which include assertions whose behavior cannot be verified by
examining the wire message from the provider to requestor. Assertion authors can
mitigate this threat by not designing assertions whose behavior cannot be
verified using wire messages.</p></div><div class="div2">
@@ -1298,10 +1302,10 @@
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 <a href="#RFC3023">[IETF RFC 3023]</a>.</p></dd><dt class="label">Base URI:</dt><dd><p>As specified in <a href="#RFC3023">[IETF RFC 3023]</a>, section 6.
- <span class="diff-del"><span>Also </span></span><span class="diff-add"><span>Also
- </span></span>see section <a href="#IRI_Policy_Expressions"><b>4.6 Use of IRIs in Policy Expressions</b></a>
- <span class="diff-del"><span>in </span></span><span class="diff-add"><span>in
- </span></span>this document and <a href="ws-policy-attachment.html#IRI_Policy_Attachment">section 3.5 Use of IRIs in Policy
+ 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="ws-policy-attachment.html#IRI_Policy_Attachment">section 3.5 Use of IRIs in Policy
Attachment</a> in <a href="#WS-PolicyAttachment">[Web Services Policy Attachment]</a>.</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
@@ -1318,38 +1322,38 @@
Web Services Policy 1.5 - Attachment</a> is available at
http://www.w3.org/TR/ws-policy-attachment. (See ws-policy-attachment.html.)</dd><dt class="label"><a name="RFC2119" id="RFC2119"></a>[IETF RFC 2119] </dt><dd>
<a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate
- <span class="diff-del"><span>Requirement </span></span><span class="diff-add"><span>Requirement
- </span></span>Levels</cite></a>, S. Bradner, Author. Internet Engineering Task Force, June
+ Requirement
+ Levels</cite></a>, S. Bradner, Author. Internet Engineering Task Force, June
1999. Available at http://www.ietf.org/rfc/rfc2119.txt. (See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a name="RFC3986" id="RFC3986"></a>[IETF RFC 3986] </dt><dd>
<a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource Identifier (URI): Generic Syntax </cite></a>, T.
Berners-Lee, R. Fielding and L. Masinter, Authors. Network Working Group,
January 2005. Available at http://www.ietf.org/rfc/rfc3986.txt. (See http://www.ietf.org/rfc/rfc3986.txt.)</dd><dt class="label"><a name="RFC3987" id="RFC3987"></a>[IETF RFC 3987] </dt><dd>
<a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>Internationalized Resource Identifiers (IRIs) </cite></a>, M.
Duerst and M. Suignard, Authors. Internet Engineering Task Force,
- <span class="diff-del"><span>January </span></span><span class="diff-add"><span>January
- </span></span>2005. Available at http://www.ietf.org/rfc/rfc3987.txt. (See http://www.ietf.org/rfc/rfc3987.txt.)</dd><dt class="label"><a name="WS-Security" id="WS-Security"></a>[WS-Security 2004] </dt><dd>
+ January
+ 2005. Available at http://www.ietf.org/rfc/rfc3987.txt. (See http://www.ietf.org/rfc/rfc3987.txt.)</dd><dt class="label"><a name="WS-Security" id="WS-Security"></a>[WS-Security 2004] </dt><dd>
<a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"><cite>Web Services Security: SOAP Message Security 1.0
- <span class="diff-del"><span>(WS-Security </span></span><span class="diff-add"><span>(WS-Security
- </span></span>2004)</cite></a>, A. Nadalin, C. Kaler, P. Hallam-Baker, and R.
+ (WS-Security
+ 2004)</cite></a>, A. Nadalin, C. Kaler, P. Hallam-Baker, and R.
Monzillo, Editors. Organization for the Advancement of Structured
Information Standards, March 2004. Available at
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf. (See http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf.)</dd><dt class="label"><a name="XMLBASE" id="XMLBASE"></a>[XML BASE] </dt><dd>
<a href="http://www.w3.org/TR/2001/REC-xmlbase-20010627/"><cite>XML Base</cite></a>, Jonathan Marsh, Editor. World Wide
- <span class="diff-del"><span>Web </span></span><span class="diff-add"><span>Web
- </span></span>Consortium, 27 June 2001. This version of the XML Base Recommendation is
+ Web
+ Consortium, 27 June 2001. This version of the XML Base Recommendation is
http://www.w3.org/TR/2001/REC-xmlbase-20010627/. The <a href="http://www.w3.org/TR/xmlbase/">latest version of XML Base</a> is
available at http://www.w3.org/TR/xmlbase/. (See http://www.w3.org/TR/2001/REC-xmlbase-20010627/.)</dd><dt class="label"><a name="XML10" id="XML10"></a>[XML 1.0] </dt><dd>
<a href="http://www.w3.org/TR/2006/REC-xml-20060816"><cite>Extensible Markup Language (XML) 1.0 (Fourth Edition)</cite></a>,
T. Bray, J. Paoli, C. M. Sperberg-McQueen, and E. Maler, Editors. World Wide
Web Consortium, 10 February 1998, revised 16 August 2006. This version of
the XML 1.0 Recommendation is
- <span class="diff-del"><span>http://www.w3.org/TR/2006/REC-xml-20060816. </span></span><span class="diff-add"><span>http://www.w3.org/TR/2006/REC-xml-20060816.
- </span></span>The <a href="http://www.w3.org/TR/REC-xml/">latest version of XML
+ http://www.w3.org/TR/2006/REC-xml-20060816.
+ The <a href="http://www.w3.org/TR/REC-xml/">latest version of XML
1.0</a> is available at http://www.w3.org/TR/REC-xml. (See http://www.w3.org/TR/2006/REC-xml-20060816.)</dd><dt class="label"><a name="XMLID" id="XMLID"></a>[XML ID] </dt><dd>
<a href="http://www.w3.org/TR/2005/REC-xml-id-20050909/"><cite>xml:id Version 1.0</cite></a>, J. Marsh, D. Veillard and N. Walsh,
Editors. World Wide Web Consortium, 9 September 2005. This version of
- <span class="diff-del"><span>the </span></span><span class="diff-add"><span>the
- </span></span>xml:id Version 1.0 Recommendation is
+ the
+ xml:id Version 1.0 Recommendation is
http://www.w3.org/TR/2005/REC-xml-id-20050909/. The <a href="http://www.w3.org/TR/xml-id/">latest version of xml:id Version
1.0</a> is available at http://www.w3.org/TR/xml-id/. (See http://www.w3.org/TR/2005/REC-xml-id-20050909/.)</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"></a>[XML Information Set] </dt><dd>
<a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/"><cite>XML Information Set (Second Edition)</cite></a>, J. Cowan and R.
@@ -1362,8 +1366,8 @@
revised 16 August 2006. This version of the XML Information Set
Recommendation is http://www.w3.org/TR/2006/REC-xml-names-20060816/. The
<a href="http://www.w3.org/TR/REC-xml-names/">latest version
- <span class="diff-del"><span>of </span></span><span class="diff-add"><span>of
- </span></span>Namespaces in XML</a> is available at
+ of
+ Namespaces in XML</a> is available at
http://www.w3.org/TR/REC-xml-names. (See http://www.w3.org/TR/2006/REC-xml-names-20060816/.)</dd><dt class="label"><a name="XMLSchemaPart1" id="XMLSchemaPart1"></a>[XML Schema Structures] </dt><dd>
<a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"><cite>XML Schema Part 1: Structures Second Edition</cite></a>, H.
Thompson, D. Beech, M. Maloney, and N. Mendelsohn, Editors. World Wide Web
@@ -1379,8 +1383,8 @@
Kohn, July 1998. (See http://www.ietf.org/rfc/rfc3023.txt.)</dd></dl></div><div class="div2">
<h3><a name="Informative-References" id="Informative-References"></a>B.2 Other References</h3><dl><dt class="label"><a name="C14NNOTE" id="C14NNOTE"></a>[C14N 1.0 Note] </dt><dd>
<a href="http://www.w3.org/2006/04/c14n-note/c14n-note.html"><cite>Known Issues with Canonical XML 1.0 (C14N/1.0)</cite></a>,
- <span class="diff-del"><span>J. </span></span><span class="diff-add"><span>J.
- </span></span>Kahan and K. Lanz, Editors. World Wide Web Consortium, 17 August 2006.
+ J.
+ Kahan and K. Lanz, Editors. World Wide Web Consortium, 17 August 2006.
Available at http://www.w3.org/2006/04/c14n-note/c14n-note.html. (See http://www.w3.org/2006/04/c14n-note/c14n-note.html.)</dd><dt class="label"><a name="RFC2246" id="RFC2246"></a>[IETF RFC 2246] </dt><dd>IETF "RFC 2246: The TLS Protocol", T. Dierks, C. Allen, January
1999. (See http://www.ietf.org/rfc/rfc2246.txt.)</dd><dt class="label"><a name="SOAP11" id="SOAP11"></a>[SOAP 1.1] </dt><dd>
<a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>Simple Object Access Protocol (SOAP) 1.1</cite></a>, D. Box, et
@@ -1408,8 +1412,8 @@
UDDI 2.0 Data Structures</a> is available at
http://uddi.org/pubs/DataStructure_v2.htm. (See http://uddi.org/pubs/DataStructure-V2.03-Published-20020719.htm.)</dd><dt class="label"><a name="UDDI30" id="UDDI30"></a>[UDDI 3.0] </dt><dd>
<a href="http://uddi.org/pubs/uddi-v3.0.1-20031014.htm"><cite>UDDI Version 3.0.1</cite></a>, L. Clément, et
- <span class="diff-del"><span>al, </span></span><span class="diff-add"><span>al,
- </span></span>Editors. Organization for the Advancement of Structured Information
+ al,
+ Editors. Organization for the Advancement of Structured Information
Standards, 14 October 2003. This version of the UDDI Version 3.0 is
http://uddi.org/pubs/uddi-v3.0.1-20031014.htm. The <a href="http://uddi.org/pubs/uddi_v3.htm">latest version of the UDDI
3.0</a> specification is available at http://uddi.org/pubs/uddi_v3.htm. (See http://uddi.org/pubs/uddi-v3.0.1-20031014.htm.)</dd><dt class="label"><a name="WS-SecurityPolicy" id="WS-SecurityPolicy"></a>[WS-SecurityPolicy] </dt><dd>
@@ -1458,13 +1462,13 @@
acknowledged.
</p></div><div class="div1">
<h2><a name="change-description" id="change-description"></a>D. Changes in this Version of the Document (Non-Normative)</h2><p>A list of major editorial changes since the Working Draft dated <span class="diff-chg"><span>28 February, </span></span><span class="diff-add"><span>2007</span></span><span class="diff-del"><span>2006
- is </span></span><span class="diff-add"><span>is
- </span></span>below:</p><ul><span class="diff-del"><span>Reorganized the content in Section
+ is </span></span>is
+ below:</p><ul><li><div class="diff-del"><p class="diff-del">Reorganized the content in Section
.
Documented the schema outline & description for policy operators
(wsp:Policy, wsp:All and wsp:ExactlyOne elements)
in Section .
- </span></span><li><p><span class="diff-add"><span>None.</span></span><span class="diff-del"><span>Explicitly described the interaction between Web Services Policy and XML Base in
+ </p></div></li><li><p><span class="diff-add"><span>None.</span></span><span class="diff-del"><span>Explicitly described the interaction between Web Services Policy and XML Base in
Section .</span></span></p></li></ul></div><div class="div1">
<h2><a name="change-log" id="change-log"></a>E. Web Services Policy 1.5 - Framework Change Log (Non-Normative)</h2><a name="ws-policy-framework-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#action12">12</a>, <a href="http://www.w3.org/2006/07/12-ws-policy-minutes.html#action16">16</a> and <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">20060718</td><td rowspan="1" colspan="1">DBO</td><td rowspan="1" colspan="1">Completed action items: 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 ddn't show up in the
change log) </td></tr><tr><td rowspan="1" colspan="1">20060726</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Incorporated the <a href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Jul/0107.html">XML namespace URI versioning policy</a> adopted by the WG. </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>
@@ -1512,4 +1516,4 @@
to <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4379"><span class="diff-add"><span>issue 4379</span></span></a>
with minor editorial revision (editors action
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/181"><span class="diff-add"><span>181</span></span></a>).
- </td></div></tr></div><div class="diff-add"><tr class="diff-add"><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">20070321</td></div><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">ASV</td></div><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">Reset Section <a href="#change-description"><b>D. Changes in this Version of the Document</b></a>. </td></div></tr></div></tbody></table><br></div></div></body></html>
\ No newline at end of file
+ </td></div></tr></div><div class="diff-add"><tr class="diff-add"><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">20070321</td></div><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">ASV</td></div><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">Reset Section <a href="#change-description"><b>D. Changes in this Version of the Document</b></a>. </td></div></tr></div><div class="diff-add"><tr class="diff-add"><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">20070328</td></div><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">FS</td></div><div class="diff-add"><td rowspan="1" colspan="1" class="diff-add">Re-formatted the first example in <a href="#Policy_Assertion_Nesting"><b>4.3.2 Policy Assertion Nesting</b></a>. </td></div></tr></div></tbody></table><br></div></div></body></html>
\ No newline at end of file
Index: ws-policy-framework-diff20070228.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework-diff20070228.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- ws-policy-framework-diff20070228.xml 23 Mar 2007 00:48:41 -0000 1.3
+++ ws-policy-framework-diff20070228.xml 28 Mar 2007 00:44:56 -0000 1.4
@@ -1,119 +1,40 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- $Id$ -->
-<!DOCTYPE spec PUBLIC "-//W3C//DTD Specification V2.10//EN" "xmlspec.dtd" [
-<!ENTITY prefix "ws-policy-framework">
-<!ENTITY % entities SYSTEM "entities.dtd" >
-%entities;
-<!ENTITY status SYSTEM "status.xml">
-<!ENTITY document.status "Editors' copy $Date$">
-<!ENTITY framework-title "&framework.title;">
-<!ENTITY prevloc "http://www.w3.org/TR/2007/CR-ws-policy-20070228">
-<!ENTITY hellip "…">
[...3333 lines suppressed...]
+ to <loc xmlns:xlink="http://www.w3.org/1999/xlink" href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4379" xlink:type="simple" xlink:actuate="onRequest" xlink:show="replace"><phrase diff="add">issue 4379</phrase></loc>
with minor editorial revision (editors action
- <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/181" xlink:type="simple" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:actuate="onRequest" xlink:show="replace"><phrase diff="add">181</phrase></loc>).
- </td>
-
- </tr>
- <tr diff="add">
- <td rowspan="1" colspan="1" diff="add">20070321</td>
- <td rowspan="1" colspan="1" diff="add">ASV</td>
- <td rowspan="1" colspan="1" diff="add">Reset Section <specref ref="change-description"></specref>. </td>
- </tr>
-
- </tbody>
- </table>
- </inform-div1>
- </back>
-</spec>
+ <loc xmlns:xlink="http://www.w3.org/1999/xlink" href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/181" xlink:type="simple" xlink:actuate="onRequest" xlink:show="replace"><phrase diff="add">181</phrase></loc>).
+ </td></tr><tr diff="add"><td rowspan="1" colspan="1" diff="add">20070321</td><td rowspan="1" colspan="1" diff="add">ASV</td><td rowspan="1" colspan="1" diff="add">Reset Section <specref ref="change-description"/>. </td></tr><tr diff="add"><td rowspan="1" colspan="1" diff="add">20070328</td><td rowspan="1" colspan="1" diff="add">FS</td><td rowspan="1" colspan="1" diff="add">Re-formatted the first example in <specref ref="Policy_Assertion_Nesting"/>. </td></tr></tbody></table></inform-div1></back></spec>
\ No newline at end of file
Index: ws-policy-attachment-diff20070228.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment-diff20070228.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- ws-policy-attachment-diff20070228.xml 23 Mar 2007 00:48:41 -0000 1.3
+++ ws-policy-attachment-diff20070228.xml 28 Mar 2007 00:44:56 -0000 1.4
@@ -1,87 +1,19 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- $Id$ -->
-<!DOCTYPE spec PUBLIC "-//W3C//DTD Specification V2.10//EN" "xmlspec.dtd" [
-<!ENTITY prefix "ws-policy-attachment">
-<!ENTITY % entities SYSTEM "entities.dtd">
-%entities;
-<!ENTITY status SYSTEM "status-attachment.xml">
-<!ENTITY document.status "Editors' copy $Date$">
-<!ENTITY attachment-title "&attachment.title;">
-<!ENTITY prevloc "http://www.w3.org/TR/2007/CR-ws-policy-attach-20070228/">
-<!ENTITY hellip "…">
[...3894 lines suppressed...]
-</table>
-</inform-div1>
-</back>
-</spec>
+ </td></tr><tr><td rowspan="1" colspan="1">20070123</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Fixed a typo in <specref ref="Informative-References"/>: "[IETF RFC 3023]IETF "RFC 2246:".
+ </td></tr><tr><td rowspan="1" colspan="1">20070124</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Updated Section <specref ref="change-description"/>.
+ </td></tr><tr><td rowspan="1" colspan="1">20070207</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Implemented the resolution for issue
+ <loc xmlns:xlink="http://www.w3.org/1999/xlink" href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4306" xlink:type="simple" xlink:actuate="onRequest" xlink:show="replace">4306</loc>.
+ Editors' action <loc xmlns:xlink="http://www.w3.org/1999/xlink" href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/158" xlink:type="simple" xlink:actuate="onRequest" xlink:show="replace">158</loc>.
+ </td></tr><tr><td rowspan="1" colspan="1">20070222</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Applied a <loc xmlns:xlink="http://www.w3.org/1999/xlink" href="http://lists.w3.org/Archives/Public/public-ws-policy/2007Jan/0157.html" xlink:type="simple" xlink:actuate="onRequest" xlink:show="replace">missed item</loc>
+ (re issue <loc xmlns:xlink="http://www.w3.org/1999/xlink" href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4207" xlink:type="simple" xlink:actuate="onRequest" xlink:show="replace">4207</loc>) to
+ <specref ref="XMLNamespaces"/>.
+ </td></tr><tr diff="add"><td rowspan="1" colspan="1" diff="add">20070315</td><td rowspan="1" colspan="1" diff="add">PY</td><td rowspan="1" colspan="1" diff="add">Implemented the resolution for issue
+ <loc xmlns:xlink="http://www.w3.org/1999/xlink" href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4391" xlink:type="simple" xlink:actuate="onRequest" xlink:show="replace"><phrase diff="add">4391</phrase></loc>.
+ Editors' action <loc xmlns:xlink="http://www.w3.org/1999/xlink" href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/200" xlink:type="simple" xlink:actuate="onRequest" xlink:show="replace"><phrase diff="add">200</phrase></loc>.
+ </td></tr><tr diff="add"><td rowspan="1" colspan="1" diff="add">20070316</td><td rowspan="1" colspan="1" diff="add">PY</td><td rowspan="1" colspan="1" diff="add">Implemented part of the resolution as it applies to the Attachment spec, for issue
+ <loc xmlns:xlink="http://www.w3.org/1999/xlink" href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4389" xlink:type="simple" xlink:actuate="onRequest" xlink:show="replace"><phrase diff="add">4389</phrase></loc>.
+ Editors' action <loc xmlns:xlink="http://www.w3.org/1999/xlink" href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/209" xlink:type="simple" xlink:actuate="onRequest" xlink:show="replace"><phrase diff="add">209</phrase></loc>.
+ </td></tr><tr diff="add"><td rowspan="1" colspan="1" diff="add">20070321</td><td rowspan="1" colspan="1" diff="add">ASV</td><td rowspan="1" colspan="1" diff="add">Reset Section <specref ref="change-description"/>. </td></tr></tbody></table></inform-div1></back></spec>
\ No newline at end of file
Index: ws-policy-guidelines-diff20061221.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines-diff20061221.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- ws-policy-guidelines-diff20061221.html 23 Mar 2007 00:48:41 -0000 1.4
+++ ws-policy-guidelines-diff20061221.html 28 Mar 2007 00:44:56 -0000 1.5
@@ -1,6 +1,6 @@
<!DOCTYPE html
PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en-US"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Policy 1.5 - Guidelines for Policy Assertion Authors -- Review Version</title><style type="text/css">
+<html lang="en-US"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title> -- Review Version</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
@@ -73,8 +73,9 @@
identify changes from a previous version. Three kinds of changes
are highlighted: <span class="diff-add">new, added text</span>,
<span class="diff-chg">changed text</span>, and
- <span class="diff-del">deleted text</span>.</p><hr></div><div class="head">
-<h1><a name="title" id="title"></a>Web Services Policy 1.5 - Guidelines for Policy Assertion Authors</h1>
+ <span class="diff-del">deleted text</span>. NOTE: the status section of the document has not been augmented to
+ identify changes from a previous version.</p><hr></div><div class="head">
+<h1><a name="title" id="title"></a></h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a>Editors' copy $Date$ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
<a href="ws-policy-guidelines.html">ws-policy-guidelines.html</a>
</dd><dt>Latest version:</dt><dd><a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-guidelines.html?content-type=text/html;charset=utf-8">http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-guidelines.html?content-type=text/html;charset=utf-8</a></dd><div class="diff-add"><dt>Previous version:</dt><dd>
@@ -92,7 +93,7 @@
no official standing.</strong></p><p></p></div><div class="toc">
<h2><a name="contents" id="contents"></a>Table of Contents</h2><p class="toc">1. <a href="#introduction">Introduction</a><br>
2. <a href="#Assertions">What is an Assertion? </a><br>
-3. <a href="#d2e377">Who is involved in authoring Assertions? </a><br>
+3. <a href="#d2e365">Who is involved in authoring Assertions? </a><br>
3.1 <a href="#roles"> Roles and Responsibilities </a><br>
3.1.1 <a href="#domain-owners"> Assertion Authors</a><br>
3.1.2 <a href="#consumers">Consumers</a><br>
@@ -110,8 +111,8 @@
4.4.2 <a href="#nested-assertions">Nested Assertions</a><br>
4.4.3 <a href="#which-one-to-use">Considerations for choosing parameters vs nesting</a><br>
4.5 <a href="#optional-policy-assertion">Designating Optional Behaviors</a><br>
- 4.5.1 <a href="#d2e1532">Optional behavior in Compact authoring</a><br>
- 4.5.2 <a href="#d2e1540">Optional behavior at runtime</a><br>
+ 4.5.1 <a href="#d2e1496">Optional behavior in Compact authoring</a><br>
+ 4.5.2 <a href="#d2e1504">Optional behavior at runtime</a><br>
4.6 <a href="#levels-of-abstraction">Levels of Abstraction in WSDL </a><br>
4.7 <a href="#interrelated-domains">Interrelated domains</a><br>
5. <a href="#versioning-policy-assertions">Versioning Policy Assertions</a><br>
@@ -151,8 +152,7 @@
services different sets of WS-Policy Assertions need to be
defined by different communities based upon domain-specific requirements of
the web service.
- </p><p>The focus of these guidelines is to capture best <span class="diff-del"><span>practices
- </span></span><span class="diff-add"><span>practices </span></span>and usage patterns for practitioners. It is a
+ </p><p>The focus of these guidelines is to capture best practices and usage patterns for practitioners. It is a
complementary guide to the Framework and Attachments
specifications and <span class="diff-add"><span>the Primer.</span></span><span class="diff-del"><span>primer. </span></span>It is intended to provide
non-normative guidelines <span class="diff-add"><span>for </span></span><span class="diff-del"><span>for:
@@ -170,9 +170,9 @@
</span></span>the <span class="diff-chg"><span>syntax </span></span>of the language and understand <span class="diff-chg"><span>how to </span></span><span class="diff-add"><span>build</span></span><span class="diff-del"><span>for
describing </span></span><span class="diff-add"><span>consistent
</span></span>policy <span class="diff-chg"><span>expressions
- </span></span></p></li><span class="diff-del"><span>Some of the guidance for authors can also be helpful for:
+ </span></span></p></li><li><div class="diff-del"><p class="diff-del">Some of the guidance for authors can also be helpful for:
- </span></span><li><p>Consumers of policy expressions who need to understand
+ </p></div></li><li><p>Consumers of policy expressions who need to understand
the requirements contained in policy <span class="diff-chg"><span>assertions
</span></span></p></li><li><p>Providers of policy expressions who need to understand
how to use the assertions authored by <span class="diff-add"><span>Assertion</span></span><span class="diff-del"><span>policy assertion </span></span><span class="diff-chg"><span>Authors
@@ -235,7 +235,7 @@
tooling or interoperability. </span></span>An example <span class="diff-del"><span>of a non-shared behavior </span></span>is the use of logging or auditing by the provider.
<span class="diff-del"><span>Requesters </span></span><span class="diff-chg"><span>If an assertion only describes one participant's behavior </span></span><span class="diff-add"><span>then
the</span></span><span class="diff-del"><span>compatible </span></span><span class="diff-chg"><span>assertion </span></span><span class="diff-add"><span>may</span></span><span class="diff-del"><span>alternative
- for </span></span><span class="diff-chg"><span>be marked as ignorable (indicating it does not impact interoperability). An </span></span><span class="diff-add"><span>ignorable</span></span><span class="diff-del"><span>behavior
+ for </span></span><span class="diff-chg"><span>be marked as ignorable (indicating it does not impact interoperability). An </span></span>ignorable<span class="diff-del"><span>behavior
then </span></span><span class="diff-chg"><span>policy </span></span>assertion <span class="diff-add"><span>is
ignored</span></span><span class="diff-del"><span>will </span></span><span class="diff-chg"><span>for lax policy intersection. If an assertion is not an </span></span><span class="diff-add"><span>ignorable</span></span><span class="diff-del"><span>policy
intersection </span></span><span class="diff-add"><span>assertion then</span></span><span class="diff-del"><span>will </span></span><span class="diff-chg"><span>it is deemed </span></span><span class="diff-add"><span>important for agreement
@@ -259,7 +259,7 @@
best practices will be an assertion specification that describes
a contract for the consumers and providers of the capabilities and constraints of the domain.
</p></div><div class="div1">
-<h2><a name="d2e377" id="d2e377"></a>3. Who is involved in authoring Assertions? </h2><p>In order for the policy framework to enable communities to
+<h2><a name="d2e365" id="d2e365"></a>3. Who is involved in authoring Assertions? </h2><p>In order for the policy framework to enable communities to
express their own domain knowledge, it is necessary to provide basic
functionality that all domains could exploit and then allow
points of extension where authors of the various WS-Policy
@@ -338,8 +338,8 @@
specify its on-the-wire message behavior as <span class="diff-chg"><span>a policy
</span></span>expression that conforms to the <span class="diff-add"><span>Web Services Policy 1.5 - Framework</span></span><span class="diff-del"><span>WS-PolicyFramework </span></span><span class="diff-add"><span>[</span></span><span class="diff-add"><a href="#WS-Policy">[Web Services Policy Framework]</a></span><span class="diff-add"><span>]
</span></span>and <span class="diff-add"><span>Web Services Policy 1.5 -
- </span></span><span class="diff-del"><span>WS-Policy </span></span>Attachment <span class="diff-add"><span>[</span></span><span class="diff-add"><a href="#WS-PolicyAttachment">[Web Services Policy Attachment]</a></span><span class="diff-add"><span>]</span></span><span class="diff-del"><span>specifications. </span></span><span class="diff-add"><span>specifications.
- </span></span>The <span class="diff-chg"><span>Web </span></span><span class="diff-add"><span>Services Policy 1.5 - Attachment </span></span>specification has defined a set of
+ </span></span><span class="diff-del"><span>WS-Policy </span></span>Attachment <span class="diff-add"><span>[</span></span><span class="diff-add"><a href="#WS-PolicyAttachment">[Web Services Policy Attachment]</a></span><span class="diff-add"><span>]</span></span>specifications.
+ The <span class="diff-chg"><span>Web </span></span><span class="diff-add"><span>Services Policy 1.5 - Attachment </span></span>specification has defined a set of
subjects and an extensible mechanism for attaching policies
to web services subjects.
<span class="diff-del"><span>When a web service provider
@@ -369,7 +369,7 @@
</p><p>Assertions can be simple or they can be complex. <span class="diff-chg"><span>Assertion Authors </span></span>may
choose to specify <span class="diff-chg"><span>multiple peer </span></span><span class="diff-add"><span>assertions, each carrying the semantic of
a particular behavior,</span></span><span class="diff-del"><span>two
- assertions </span></span>or they may choose to specify <span class="diff-add"><span>assertions</span></span><span class="diff-del"><span>many assertion
+ assertions </span></span>or they may choose to specify assertions<span class="diff-del"><span>many assertion
elements </span></span>that
<span class="diff-add"><span>contains </span></span><span class="diff-chg"><span>assertion </span></span>parameters <span class="diff-add"><span>and/or</span></span><span class="diff-del"><span>or other </span></span>nested <span class="diff-add"><span>policy expression (nested
assertions), each of which relate to an aspect of the behavior, yet
@@ -384,8 +384,8 @@
</span></span><span class="diff-del"><span>audience.
</span></span></p><p>
If a <span class="diff-chg"><span>set </span></span><span class="diff-add"><span>of assertions describes</span></span><span class="diff-del"><span>has </span></span>a wide range of behaviors, the ability
- <span class="diff-del"><span>to </span></span><span class="diff-add"><span>to
- </span></span>combine individual assertions may also need to be considered.
+ to
+ combine individual assertions may also need to be considered.
</p><p>
The <span class="diff-add"><span>WS-Policy Attachment specification defines a </span></span>number of different
<span class="diff-add"><span>policy </span></span>subjects to which an assertion can be <span class="diff-chg"><span>attached. For attaching </span></span><span class="diff-add"><span>to
@@ -397,10 +397,10 @@
Attachment </span></span><span class="diff-add"><span>specification.
</span></span></p><div class="diff-add"><p class="diff-add">
<span class="diff-add"><span>The</span></span><span class="diff-del"><span>that </span></span><span class="diff-chg"><span>WS-Policy Attachment specification provides various mechanisms </span></span><span class="diff-add"><span>to
- attach</span></span><span class="diff-del"><span>configurations </span></span><span class="diff-add"><span>a</span></span><span class="diff-del"><span>dynamically.
+ attach</span></span><span class="diff-del"><span>configurations </span></span>a<span class="diff-del"><span>dynamically.
</span></span><span class="diff-chg"><span>policy expression to a </span></span>policy <span class="diff-chg"><span>subject. Although a </span></span><span class="diff-add"><span>policy
- assertion</span></span><span class="diff-del"><span>there </span></span><span class="diff-chg"><span>may be constrained to </span></span><span class="diff-add"><span>a</span></span><span class="diff-del"><span>of
+ assertion</span></span><span class="diff-del"><span>there </span></span><span class="diff-chg"><span>may be constrained to </span></span>a<span class="diff-del"><span>of
attaching </span></span><span class="diff-chg"><span>specific set </span></span>of <span class="diff-chg"><span>policy subjects by
</span></span>assertion <span class="diff-chg"><span>authors, its semantics should not be dependent upon </span></span>the
<span class="diff-add"><span>mechanism </span></span><span class="diff-chg"><span>by which the policy expression is </span></span><span class="diff-add"><span>attached</span></span><span class="diff-del"><span>the
@@ -408,13 +408,13 @@
subject.</span></span><span class="diff-del"><span>assertion </span></span><span class="diff-chg"><span>For instance, an </span></span><span class="diff-add"><span>assertion</span></span><span class="diff-del"><span>it
in </span></span><span class="diff-chg"><span>"Foo" has the same </span></span><span class="diff-add"><span>semantic</span></span><span class="diff-del"><span>different
alternatives) </span></span><span class="diff-add"><span>when
- attached</span></span><span class="diff-del"><span>via </span></span><span class="diff-chg"><span>to </span></span><span class="diff-add"><span>an operation</span></span><span class="diff-del"><span>a </span></span>policy <span class="diff-chg"><span>subject regardless </span></span><span class="diff-add"><span>of</span></span><span class="diff-del"><span>be
+ attached</span></span><span class="diff-del"><span>via </span></span><span class="diff-chg"><span>to </span></span><span class="diff-add"><span>an operation</span></span>policy <span class="diff-chg"><span>subject regardless </span></span><span class="diff-add"><span>of</span></span><span class="diff-del"><span>be
associated </span></span><span class="diff-chg"><span>whether it </span></span><span class="diff-add"><span>was
attached</span></span><span class="diff-del"><span>alternatives </span></span><span class="diff-chg"><span>using XML </span></span><span class="diff-add"><span>element</span></span><span class="diff-del"><span>A
referencing </span></span><span class="diff-chg"><span>policy attachment or the external </span></span><span class="diff-add"><span>URI
- attachment</span></span><span class="diff-del"><span>a </span></span><span class="diff-add"><span>mechanism.</span></span><span class="diff-del"><span>tooling
+ attachment</span></span><span class="diff-add"><span>mechanism.</span></span><span class="diff-del"><span>tooling
environment; </span></span><span class="diff-chg"><span>Independence from </span></span>a <span class="diff-del"><span>domain </span></span>specific
- <span class="diff-del"><span>attachment </span></span><span class="diff-chg"><span>attachment </span></span><span class="diff-add"><span>mechanism
+ <span class="diff-chg"><span>attachment </span></span><span class="diff-add"><span>mechanism
allows</span></span><span class="diff-del"><span>multiple </span></span><span class="diff-chg"><span>policy tools to </span></span><span class="diff-add"><span>choose</span></span><span class="diff-del"><span>Endpoint
References </span></span><span class="diff-chg"><span>the most appropriate mechanism to attach </span></span><span class="diff-add"><span>a
policy</span></span><span class="diff-del"><span>policies </span></span><span class="diff-chg"><span>without having </span></span>to <span class="diff-add"><span>analyze the contents of the</span></span><span class="diff-del"><span>be </span></span><span class="diff-chg"><span>policy.
@@ -426,7 +426,7 @@
<span class="diff-del"><span>assertion. Does the assertion pertain to a </span></span><span class="diff-add"><span>assertion's</span></span><span class="diff-del"><span>specific
behavior that is tied to </span></span><span class="diff-add"><span>semantic.</span></span></em><span class="diff-del"><span>a </span></span></p></li><li><p><em><span class="diff-add"><span>The</span></span><span class="diff-del"><span>context </span></span><span class="diff-chg"><span>specification of </span></span>the <span class="diff-add"><span>set</span></span><span class="diff-del"><span>behavior
different </span></span><span class="diff-chg"><span>of valid policy subjects to which </span></span>an
- assertion <span class="diff-del"><span>that </span></span>may <span class="diff-del"><span>have different semantics for a single
+ assertion may <span class="diff-del"><span>have different semantics for a single
message exchange or for all message exchanges that pertain
to an endpoint would probably </span></span>be <span class="diff-add"><span>attached.</span></span></em><span class="diff-del"><span>represented by separate assertions.
</span></span></p></li><li><p><em><span class="diff-add"><span>The scope</span></span><span class="diff-del"><span>Scoping </span></span>of the assertion<span class="diff-del"><span>. </span></span><span class="diff-add"><span>in</span></span><span class="diff-del"><span>Where
@@ -434,7 +434,7 @@
subject.</span></span></em><span class="diff-del"><span>assertion </span></span><span class="diff-chg"><span>For </span></span><span class="diff-add"><span>example,</span></span><span class="diff-del"><span>a
specific </span></span><span class="diff-chg"><span>an assertion with Endpoint Policy Subject </span></span><span class="diff-add"><span>can be
scoped to</span></span><span class="diff-del"><span>about </span></span>a
- <span class="diff-del"><span>specific </span></span><span class="diff-chg"><span>given message exchange with that endpoint, or </span></span><span class="diff-add"><span>it</span></span><span class="diff-del"><span>a
+ <span class="diff-del"><span>specific </span></span><span class="diff-chg"><span>given message exchange with that endpoint, or </span></span>it<span class="diff-del"><span>a
specific </span></span><span class="diff-chg"><span>can be </span></span><span class="diff-add"><span>scoped
to</span></span><span class="diff-del"><span>parties? </span></span><span class="diff-chg"><span>all </span></span><span class="diff-add"><span>messages</span></span><span class="diff-del"><span>of
the </span></span><span class="diff-chg"><span>exchanged with that endpoint. The former case permits a
@@ -793,7 +793,7 @@
to the WS-Policy framework.
</p></div></div><div class="div2">
<h3><a name="optional-policy-assertion" id="optional-policy-assertion"></a>4.5 Designating Optional Behaviors</h3><div class="div3">
-<h4><a name="d2e1532" id="d2e1532"></a>4.5.1 Optional behavior in Compact authoring</h4><p>Optional behaviors represent behaviors which may be engaged by a consumer. When using the
+<h4><a name="d2e1496" id="d2e1496"></a>4.5.1 Optional behavior in Compact authoring</h4><p>Optional behaviors represent behaviors which may be engaged by a consumer. When using the
compact authoring form for assertions, behaviors are marked by
using <code>wsp:Optional</code> attribute that has a value,
"true". During the process of normalization, the runtime
@@ -804,7 +804,7 @@
runtime behavior. In order to simplify reference to such
assertions, we just use the term optional assertions in this section.
</p></div><div class="div3">
-<h4><a name="d2e1540" id="d2e1540"></a>4.5.2 Optional behavior at runtime</h4><p>The <a href="#WS-Policy-Primer">[Web Services Policy Primer]</a> document contains an
+<h4><a name="d2e1504" id="d2e1504"></a>4.5.2 Optional behavior at runtime</h4><p>The <a href="#WS-Policy-Primer">[Web Services Policy Primer]</a> document contains an
example that proposes the use of <a href="#MTOM">[MTOM]</a> as an
optional behavior that can be engaged by a consumer. The
primer proposes that an assertion that identifies the use of
@@ -1034,8 +1034,8 @@
PolicyAttachment and AppliesTo also </span></span><span class="diff-chg"><span>New Policy Subjects</span></span></p></li></ul><div class="div2">
<h3><a name="Referencing_Policy_Expressions" id="Referencing_Policy_Expressions"></a>5.1 Referencing Policy Expressions</h3><p>The <a href="#WS-Policy-Primer">[Web Services Policy Primer]</a> illustrates how providers can utilize
the identification mechanism defined in the Policy specification
- <span class="diff-del"><span>to </span></span><span class="diff-add"><span>to
- </span></span>expose a complex policy expression as a reusable building block for
+ to
+ expose a complex policy expression as a reusable building block for
other policy expressions by reference. <span class="diff-add"><span>Reuse may also be useful for
domain</span></span><span class="diff-del"><span>Domain </span></span>assertion authors, especially those defining complex assertions
<span class="diff-add"><span>utilizing references</span></span><span class="diff-del"><span>that
@@ -1088,7 +1088,7 @@
original</span></span><span class="diff-del"><span>must </span></span><span class="diff-add"><span>policy subjects but new policy subjects need to </span></span>be <span class="diff-add"><span>added, it may
be possible to use the same assertion to designate the additional</span></span><span class="diff-del"><span>considered. </span></span><span class="diff-add"><span>policy
subjects without a namespace change. </span></span>For
- <span class="diff-del"><span>example </span></span><span class="diff-chg"><span>example, a policy assertion </span></span><span class="diff-add"><span>for
+ <span class="diff-chg"><span>example, a policy assertion </span></span><span class="diff-add"><span>for
a</span></span><span class="diff-del"><span>with </span></span><span class="diff-add"><span>protocol</span></span><span class="diff-del"><span>other
protocols </span></span><span class="diff-chg"><span>that is originally designed for </span></span><span class="diff-add"><span>endpoint policy subject may add
message policy subject to</span></span><span class="diff-del"><span>result </span></span><span class="diff-add"><span>indicate finer granularity </span></span>in <span class="diff-add"><span>the attachment
@@ -1103,7 +1103,7 @@
subject.</span></span></p><p><span class="diff-add"><span>Best</span></span><span class="diff-del"><span>require </span></span><span class="diff-add"><span>Practice:</span></span><span class="diff-del"><span>composition
with </span></span><span class="diff-chg"><span>If the policy subjects change over </span></span><span class="diff-add"><span>time,
</span></span>the <span class="diff-add"><span>assertion</span></span><span class="diff-del"><span>nesting
- requirements </span></span><span class="diff-add"><span>description should</span></span><span class="diff-del"><span>on </span></span><span class="diff-chg"><span>also be versioned to reflect </span></span><span class="diff-add"><span>this
+ requirements </span></span><span class="diff-add"><span>description should</span></span><span class="diff-chg"><span>also be versioned to reflect </span></span><span class="diff-add"><span>this
change.
</span></span></p></div></div></div></div><div class="div1">
<h2><a name="best-practices-attachment" id="best-practices-attachment"></a>6. Applying Best Practices for Policy Attachment</h2><div class="div2">
@@ -1323,7 +1323,7 @@
to consider policy subjects.</p><p> The <span class="diff-chg"><span>WS-Policy 1.5 - Attachment specification </span></span><span class="diff-add"><span>defines algorithms</span></span><span class="diff-del"><span>algorithm </span></span>for calculating <span class="diff-add"><span>the
effective policy for a given policy subject and
</span></span>effective policies for
- <span class="diff-add"><span>WSDL 1.1, </span></span>WSDL <span class="diff-chg"><span>2.0 and </span></span><span class="diff-add"><span>UDDI policy</span></span><span class="diff-del"><span>subjects. </span></span><span class="diff-add"><span>subjects.</span></span></p></div></div><div class="back"><div class="div1">
+ <span class="diff-add"><span>WSDL 1.1, </span></span>WSDL <span class="diff-chg"><span>2.0 and </span></span><span class="diff-add"><span>UDDI policy</span></span>subjects.</p></div></div><div class="back"><div class="div1">
<h2><a name="security-considerations" id="security-considerations"></a>A. Security Considerations</h2><p> Security considerations are discussed in the <a href="#WS-Policy">[Web Services Policy Framework]</a> document.</p></div><div class="div1">
<h2><a name="xml-namespaces" id="xml-namespaces"></a>B. XML Namespaces</h2><p>The table below lists XML Namespaces that are used in this document. The choice of any
namespace prefix is arbitrary and not semantically significant.</p><a name="nsprefix"></a><table summary="Prefixes and XML Namespaces used in this specification" border="1" cellspacing="0" cellpadding="5"><caption>Table B-1. Prefixes and XML Namespaces used in this specification.</caption><thead><tr><th rowspan="1" colspan="1">Prefix</th><th rowspan="1" colspan="1">XML Namespace</th><th rowspan="1" colspan="1">Specifications</th></tr></thead><tbody><tr><td rowspan="1" colspan="1">
@@ -1414,6 +1414,7 @@
http://docs.oasis-open.org/ws-rx/wsrm/200608/wsrm-1.1-rddl-200608.html
(See http://docs.oasis-open.org/ws-rx/wsrm/200608/wsrm-1.1-rddl-200608.html.)</dd><dt class="label"><a name="WS-RM-Policy" id="WS-RM-Policy"></a>[Web Services Reliable Messaging Policy] </dt><dd>
<a href="http://docs.oasis-open.org/ws-rx/wsrmp/200608/wsrmp-1.1-rddl-200608.html"><cite>Web Services Reliable Messaging Policy Assertion v1.1</cite></a>, <span class="diff-chg"><span>D. </span></span><span class="diff-add"><span>Davis,
+
A.</span></span><span class="diff-del"><span>Davis </span></span><span class="diff-chg"><span>Karmarkar, G. Pilz, </span></span><span class="diff-add"><span>S. Winkler, Ü. Yalçinalp,</span></span><span class="diff-del"><span>(Oracle),
Gilbert </span></span><span class="diff-chg"><span>Editors. Organization for the Advancement </span></span><span class="diff-add"><span>of
Structured</span></span><span class="diff-del"><span>Ü. </span></span><span class="diff-chg"><span>Information Standards, </span></span>August 4, 2006, available at:
Index: ws-policy-guidelines-diff20061221.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines-diff20061221.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- ws-policy-guidelines-diff20061221.xml 23 Mar 2007 00:48:41 -0000 1.4
+++ ws-policy-guidelines-diff20061221.xml 28 Mar 2007 00:44:56 -0000 1.5
@@ -1,87 +1,18 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- $Id$ -->
-<!DOCTYPE spec PUBLIC "-//W3C//DTD Specification V2.10//EN" "xmlspec.dtd" [
-<!ENTITY % entities SYSTEM "entities.dtd" >
-%entities;
-<!ENTITY status SYSTEM "status-guidelines.xml">
-<!ENTITY prefix "ws-policy-guidelines" >
-<!ENTITY document.status.guidelines "Editors' copy $Date$">
-<!ENTITY prevloc "http://www.w3.org/TR/2006/WD-ws-policy-primer-20061221">
-<!ENTITY hellip "…">
-]><spec w3c-doctype="wd" role="editors-copy">
[...2421 lines suppressed...]
+ </td></tr><tr diff="add"><td rowspan="1" colspan="1" diff="add">20070320</td><td rowspan="1" colspan="1" diff="add">ASV</td><td rowspan="1" colspan="1" diff="add">Implemented the <loc xmlns:xlink="http://www.w3.org/1999/xlink" href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4212#c1" xlink:type="simple" xlink:actuate="onRequest" xlink:show="replace"><phrase diff="add">resolution</phrase></loc>
+ for <loc xmlns:xlink="http://www.w3.org/1999/xlink" href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4212" xlink:type="simple" xlink:actuate="onRequest" xlink:show="replace"><phrase diff="add">issue 4212</phrase></loc>.
Editors' action
- <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/207" xlink:type="simple" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:actuate="onRequest" xlink:show="replace"><phrase diff="add">207</phrase></loc>.
- </td>
- </tr>
- <tr diff="add">
- <td rowspan="1" colspan="1" diff="add">20070321</td>
- <td rowspan="1" colspan="1" diff="add">ASV</td>
- <td rowspan="1" colspan="1" diff="add">Updated section <specref ref="change-description"></specref>. </td>
- </tr>
-
- </tbody>
- </table>
- </inform-div1>
- </back>
-</spec>
+ <loc xmlns:xlink="http://www.w3.org/1999/xlink" href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/207" xlink:type="simple" xlink:actuate="onRequest" xlink:show="replace"><phrase diff="add">207</phrase></loc>.
+ </td></tr><tr diff="add"><td rowspan="1" colspan="1" diff="add">20070321</td><td rowspan="1" colspan="1" diff="add">ASV</td><td rowspan="1" colspan="1" diff="add">Updated section <specref ref="change-description"/>. </td></tr></tbody></table></inform-div1></back></spec>
\ No newline at end of file
Received on Wednesday, 28 March 2007 00:45:05 UTC