- From: Umit Yalsinap via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 30 Jan 2007 23:51:48 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv15838
Modified Files:
ws-policy-guidelines.html ws-policy-guidelines.xml
Log Message:
Action 126, Resolution of 4188
Index: ws-policy-guidelines.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -d -r1.21 -r1.22
--- ws-policy-guidelines.html 30 Jan 2007 23:05:20 -0000 1.21
+++ ws-policy-guidelines.html 30 Jan 2007 23:51:45 -0000 1.22
@@ -63,7 +63,7 @@
guide to using the specifications. </p></div><div>
<h2><a name="status">Status of this Document</a></h2><p><strong>This document is an editors' copy that has
no official standing.</strong></p><p></p></div><hr><div class="toc">
-<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#introduction">Introduction</a><br>2. <a href="#Assertions">What is an Assertion? </a><br>3. <a href="#d3e169">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> 3.1.3 <a href="#providers">Providers</a><br>4. <a href="#general-guidelines">General Guidelines for Assertion Authors</a><br> 4.1 <a href="#assertion-target">Assertions and Their Target Use</a><br> 4.2 <a href="#compact-full">Authoring Styles </a><br> 4.3 <a href="#new-guidelines-domains">Considerations when Modeling New Assertions</a><br> 43.1 <a href="#minimal-approach">Minimal approach</a><br> 4.3.2 <a href="#QName_and_XML_Information_Set_representation">QName and XML Information Set representation</a><br> 4.3.3 <a href="#self-describing"> Self Describing Messages </a><br> 4.3.4 <a href="#single-domains">Single Domains</a><br> 4.4 <a href="#comparison">Comparison of Nested and Parameterized Assertions</a><br> 4.4.1 <a href="#parameterized-assertions">Assertions with Parameters</a><br> 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> nbsp; 4.5.1 <a href="#d3e508">Optional behavior in Compact authoring</a><br> 4.5.2 <a href="#d3e516">Optional behavior at runtime</a><br> 4.6 <a href="#typing-assertions">Typing Assertions</a><br> 4.7 <a href="#levels-of-abstraction">Levels of Abstraction in WSDL </a><br>5. <a href="#lifecycle">Lifecycle of Assertions</a><br> 5.1 <a href="#Referencing_Policy_Expressions">Referencing Policy Expressions</a><br> 5.2 <a href="#extending-assertions"> Evolution of Assertions (Versioning and Compatibility)</a><br>6. <a href="#inter-policy">Inter-domain Policy and Composition Issues</a><br>7. <a href="#best-practices-attachment">Applying Best Practices for Policy Attachment</a><br> 7.1 <a href="#context-free-policies">Appropriate Attachment: Preserving Context-Free Policies</a><br> 7.2 <a href="#apropriate-attachment-assertion-subjects">Appropriate Attachment: Identifying Assertion Subjects</a><br> 7.2.1 <a href="#interaction">Interaction between Subjects</a><br> 7.3 <a href="#identifying-assertion-sources">Appropriate Attachment: Identifying Assertion Sources </a><br>8. <a href="#scenario">Scenario and a worked example</a><br></p>
+<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#introduction">Introduction</a><br>2. <a href="#Assertions">What is an Assertion? </a><br>3. <a href="#d3e169">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> 3.1.3 <a href="#providers">Providers</a><br>4. <a href="#general-guidelines">General Guidelines for Assertion Authors</a><br> 4.1 <a href="#assertion-target">Assertions and Their Target Use</a><br> 4.2 <a href="#compact-full">Authoring Styles </a><br> 4.3 <a href="#new-guidelines-domains">Considerations when Modeling New Assertions</a><br> 43.1 <a href="#minimal-approach">Minimal approach</a><br> 4.3.2 <a href="#QName_and_XML_Information_Set_representation">QName and XML Information Set representation</a><br> 4.3.3 <a href="#self-describing"> Self Describing Messages </a><br> 4.3.4 <a href="#single-domains">Single Domains</a><br> 4.4 <a href="#comparison">Comparison of Nested and Parameterized Assertions</a><br> 4.4.1 <a href="#parameterized-assertions">Assertions with Parameters</a><br> 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> nbsp; 4.5.1 <a href="#d3e510">Optional behavior in Compact authoring</a><br> 4.5.2 <a href="#d3e518">Optional behavior at runtime</a><br> 4.6 <a href="#typing-assertions">Typing Assertions</a><br> 4.7 <a href="#levels-of-abstraction">Levels of Abstraction in WSDL </a><br>5. <a href="#lifecycle">Lifecycle of Assertions</a><br> 5.1 <a href="#Referencing_Policy_Expressions">Referencing Policy Expressions</a><br> 5.2 <a href="#extending-assertions"> Evolution of Assertions (Versioning and Compatibility)</a><br>6. <a href="#inter-policy">Inter-domain Policy and Composition Issues</a><br>7. <a href="#best-practices-attachment">Applying Best Practices for Policy Attachment</a><br> 7.1 <a href="#context-free-policies">Appropriate Attachment: Preserving Context-Free Policies</a><br> 7.2 <a href="#apropriate-attachment-assertion-subjects">Appropriate Attachment: Identifying Assertion Subjects</a><br> 7.2.1 <a href="#interaction">Interaction between Subjects</a><br> 7.3 <a href="#identifying-assertion-sources">Appropriate Attachment: Identifying Assertion Sources </a><br>8. <a href="#scenario">Scenario and a worked example</a><br></p>
<h3><a name="appendix" id="appendix">Appendices</a></h3><p class="toc">A. <a href="#security-considerations">Security Considerations</a><br>B. <a href="#xml-namespaces">XML Namespaces</a><br>C. <a href="#references">References</a><br>D. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>E. <a href="#change-description">Changes in this Version of
the Document</a> (Non-Normative)<br>F. <a href="#change-log">Web Services Policy 1.5 - Guidelines for Policy Assertion Authors Change Log</a> (Non-Normative)<br></p></div><hr><div class="body"><div class="div1">
<h2><a name="introduction"></a>1. Introduction</h2><p>The WS-Policy specification defines a policy to be a collection
@@ -450,10 +450,11 @@
of the advantages of Web services is that an XML message can be stored and later examined (e.g. as a record of a business
transaction) or interpreted by an intermediary; however, if information that is necessary to understand a message is not
available, these capabilities suffer.
- </p><p>Policy assertions should not be used to express the semantics of a message. Rather, if a property is
- required to understand a message, it should be communicated in
- the message, or be made available by some other means (e.g., being
- referenced by a URI in the message) instead of being communicated as a policy element.
+ </p><p>Policy assertions should not be used to express the semantics of a
+ message. Rather, if a property is
+ required to understand a message, it should be communicated in
+ the message, or be made available by some other means (e.g., being
+ referenced by a URI in the message) instead of being communicated as a policy element. Note that there are other specifications that target specification of semantics of a message, such as <cite><a href="#SAWSDL">Semantic Annotations for WSDL and XML Schema</a></cite>.
</p><p>For example, if the details of a message's encryption ( e.g., the cipher used, etc) are expressed
in policy that isn't attached to the message, it isn't possible
to later decipher it. This is very different from expressing, in
@@ -630,7 +631,7 @@
to the WS-Policy framework.
</p></div></div><div class="div2">
<h3><a name="optional-policy-assertion"></a>4.5 Designating Optional Behaviors</h3><div class="div3">
-<h4><a name="d3e508"></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="d3e510"></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
@@ -641,7 +642,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="d3e516"></a>4.5.2 Optional behavior at runtime</h4><p>The <cite><a href="#WS-Policy-Primer">Web Services Policy Primer</a></cite> document contains an
+<h4><a name="d3e518"></a>4.5.2 Optional behavior at runtime</h4><p>The <cite><a href="#WS-Policy-Primer">Web Services Policy Primer</a></cite> document contains an
example that proposes the use of <cite><a href="#MTOM">MTOM</a></cite> as an
optional behavior that can be engaged by a consumer. The
primer proposes that an assertion that identifies the use of
@@ -1158,11 +1159,11 @@
http://www.w3.org/TR/2006/CR-wsdl20-20060327. The <a href="http://www.w3.org/TR/wsdl20/">latest version of WSDL
2.0</a> is available at http://www.w3.org/TR/wsdl20.
</dd><dt class="label"><a name="WS-Policy"></a>[Web Services Policy Framework] </dt><dd>
- <cite><a href="http://www.w3.org/TR/ws-policy/">Web Services Policy 1.5 - Framework</a></cite>, A. S. Vedamuthu, D. Orchard, F. Hirsch, M. Hondo,
- P. Yendluri, T. Boubez and Ü. Yalçinalp, Editors. World Wide Web Consortium, @@,
+ <cite><a href="http://www.w3.org/TR/ws-policy/">Web Services Policy 1.5 - Framework</a></cite>, A. S. Vedamuthu, D. Orchard, F. Hirsch, M. Hondo, P. Yendluri, T. Boubez and Ü. Yalçinalp, Editors. World Wide Web Consortium, @@,
@@@@ @@@@. This version of the
- Web Services Policy 1.5 - Framework specification is at http://www.w3.org/TR/ws-policy/. The <a href="http://www.w3.org/TR/ws-policy/">latest version of
- Web Services Policy 1.5 - Framework</a> is available at http://www.w3.org/TR/ws-policy/. </dd><dt class="label"><a name="WS-PolicyAttachment"></a>[Web Services Policy Attachment] </dt><dd>
+ Web Services Policy 1.5 - Framework specification is at http://www.w3.org/TR/ws-policy/.
+ The <a href="http://www.w3.org/TR/ws-policy/">latest version of
+ Web Services Policy 1.5 - Framework</a> is available at http://www.w3.org/TR/ws-policy/. </dd><dt class="label"><a name="WS-PolicyAttachment"></a>[Web Services Policy Attachment] </dt><dd>
<cite><a href="http://www.w3.org/TR/ws-policy-attach/">Web Services Policy 1.5 - Attachment</a></cite>, A. S. Vedamuthu, D. Orchard, F. Hirsch, M. Hondo,
P. Yendluri, T. Boubez and Ü. Yalçinalp, Editors. World Wide Web Consortium, @@,
@@@@ @@@@. This version of the
@@ -1224,7 +1225,10 @@
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.
- </dd></dl></div><div class="div1">
+ </dd><dt class="label"><a name="SAWSDL"></a>[Semantic Annotations for WSDL and XML Schema] </dt><dd>
+ <cite><a href="http://www.w3.org/TR/sawsdl/">Semantic Annotations for WSDL and XML Schema</a></cite> Joel Farrell, Holger Lausen, Editors. World Wide Web Consortium, 26 January 2007. This version of the
+ specification is at http://www.w3.org/TR/sawsdl. The <a href="http://www.w3.org/TR/sawsdl/"> latest version of Semantic Annotations for WSDL and XML Schema</a> is available at
+ http://www.w3.org/TR/sawsdl/.</dd></dl></div><div class="div1">
<h2><a name="acknowledgments"></a>D. Acknowledgements (Non-Normative)</h2><p>This document is the work of the <a href="http://www.w3.org/2002/ws/policy/">W3C Web Services Policy
Working Group</a>.</p><p>
Members of the Working Group are (at the time of writing, and by
@@ -1276,4 +1280,6 @@
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/137">137</a>.
Resolution for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4198">4198</a></td></tr><tr><td rowspan="1" colspan="1">20070130</td><td rowspan="1" colspan="1">UY</td><td rowspan="1" colspan="1">Completed action item:
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/119">119</a>.
- Resolution for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4141">4141</a></td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
+ Resolution for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4141">4141</a></td></tr><tr><td rowspan="1" colspan="1">20070130</td><td rowspan="1" colspan="1">UY</td><td rowspan="1" colspan="1">Completed action item:
+ <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/126">126</a>.
+ Resolution for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4188">4188</a></td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
Index: ws-policy-guidelines.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.xml,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -d -r1.30 -r1.31
--- ws-policy-guidelines.xml 30 Jan 2007 23:05:20 -0000 1.30
+++ ws-policy-guidelines.xml 30 Jan 2007 23:51:46 -0000 1.31
@@ -649,10 +649,11 @@
transaction) or interpreted by an intermediary; however, if information that is necessary to understand a message is not
available, these capabilities suffer.
</p>
- <p>Policy assertions should not be used to express the semantics of a message. Rather, if a property is
- required to understand a message, it should be communicated in
- the message, or be made available by some other means (e.g., being
- referenced by a URI in the message) instead of being communicated as a policy element.
+ <p>Policy assertions should not be used to express the semantics of a
+ message. Rather, if a property is
+ required to understand a message, it should be communicated in
+ the message, or be made available by some other means (e.g., being
+ referenced by a URI in the message) instead of being communicated as a policy element. Note that there are other specifications that target specification of semantics of a message, such as <bibref ref="SAWSDL"/>.
</p>
<p>For example, if the details of a message's encryption ( e.g., the cipher used, etc) are expressed
in policy that isn't attached to the message, it isn't possible
@@ -1695,12 +1696,13 @@
2.0</loc> is available at http://www.w3.org/TR/wsdl20.
</bibl>
- <bibl id="WS-Policy" key="Web Services Policy Framework" href="http://www.w3.org/TR/ws-policy/">
- <titleref>&framework.title;</titleref>, A. S. Vedamuthu, D. Orchard, F. Hirsch, M. Hondo,
- P. Yendluri, T. Boubez and Ü. Yalçinalp, Editors. World Wide Web Consortium, &draft.day;,
+ <bibl id="WS-Policy" key="Web Services Policy Framework"
+ href="http://www.w3.org/TR/ws-policy/">
+ <titleref>&framework.title;</titleref>, A. S. Vedamuthu, D. Orchard, F. Hirsch, M. Hondo, P. Yendluri, T. Boubez and Ü. Yalçinalp, Editors. World Wide Web Consortium, &draft.day;,
&draft.month; &draft.year;. This version of the
- &framework.title; specification is at http://www.w3.org/TR/ws-policy/. The <loc href="http://www.w3.org/TR/ws-policy/">latest version of
- &framework.title;</loc> is available at http://www.w3.org/TR/ws-policy/. </bibl>
+ &framework.title; specification is at http://www.w3.org/TR/ws-policy/.
+ The <loc href="http://www.w3.org/TR/ws-policy/">latest version of
+ &framework.title;</loc> is available at http://www.w3.org/TR/ws-policy/. </bibl>
<bibl id="WS-PolicyAttachment" key="Web Services Policy Attachment" href="http://www.w3.org/TR/ws-policy-attach/">
<titleref>&attachment.title;</titleref>, A. S. Vedamuthu, D. Orchard, F. Hirsch, M. Hondo,
P. Yendluri, T. Boubez and Ü. Yalçinalp, Editors. World Wide Web Consortium, &draft.day;,
@@ -1774,6 +1776,11 @@
the UDDI 3.0</loc> specification is available at
http://uddi.org/pubs/uddi_v3.htm.
</bibl>
+ <bibl id="SAWSDL" key="Semantic Annotations for WSDL and XML Schema"
+ href="http://www.w3.org/TR/sawsdl/">
+ <titleref>Semantic Annotations for WSDL and XML Schema</titleref> Joel Farrell, Holger Lausen, Editors. World Wide Web Consortium, 26 January 2007. This version of the
+ specification is at http://www.w3.org/TR/sawsdl. The <loc href="http://www.w3.org/TR/sawsdl/"> latest version of Semantic Annotations for WSDL and XML Schema</loc> is available at
+ http://www.w3.org/TR/sawsdl/.</bibl>
</blist>
</div1>&acknowledgements; <inform-div1 id="change-description">
<head>Changes in this Version of
@@ -1945,13 +1952,20 @@
<loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/137">137</loc>.
Resolution for issue <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4198">4198</loc></td>
</tr>
-<tr>
+ <tr>
<td>20070130</td>
<td>UY</td>
<td>Completed action item:
<loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/119">119</loc>.
Resolution for issue <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4141">4141</loc></td>
</tr>
+ <tr>
+ <td>20070130</td>
+ <td>UY</td>
+ <td>Completed action item:
+ <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/126">126</loc>.
+ Resolution for issue <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4188">4188</loc></td>
+ </tr>
</tbody>
</table>
</inform-div1>
Received on Tuesday, 30 January 2007 23:51:58 UTC