- From: Asir Vedamuthu via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 16 Mar 2007 03:16:12 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv3578
Modified Files:
ws-policy-primer.html ws-policy-primer.xml
Log Message:
Implemented the resolution for issue 4288. Editors' action 196.
Index: ws-policy-primer.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer.html,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -d -r1.41 -r1.42
--- ws-policy-primer.html 16 Mar 2007 01:46:05 -0000 1.41
+++ ws-policy-primer.html 16 Mar 2007 03:16:10 -0000 1.42
@@ -340,9 +340,14 @@
<sp:TransportBinding>…</sp:TransportBinding>
<sp:AsymmetricBinding>…</sp:AsymmetricBinding>
</ExactlyOne>
-</All></pre></div></div><p>Contoso is able to meet their customer needs by adding optional support for the Optimized
- MIME Serialization. An optional policy assertion represents a behavior that may be
- engaged.</p></div><div class="div2">
+</All></pre></div></div><p>Contoso is able to meet their customer needs by adding optional support for the Optimized MIME
+ Serialization. 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.
+ An optional policy assertion represents a behavior that may be engaged. When a
+ policy assertion is absent from a policy vocabulary (See section 3.2, Web Services Policy 1.5 - Framework),
+ a policy-aware client should not conclude anything (other than ‘no claims’)
+ about the absence of that policy assertion. See section
+ <a href="#attaching-policy-expressions-to-wsdl"><b>2.11 Attaching Policy Expressions to WSDL</b></a> on the absence of policy expressions.</p></div><div class="div2">
<h3><a name="ignorable-policy-assertions" id="ignorable-policy-assertions"></a>2.7 Ignorable Policy Expressions</h3><p>
Suppose Contoso decides that it will log SOAP messages sent and received in an exchange.
This behavior has no direct impact on the messages sent on the wire, and does not affect interoperability.
@@ -542,11 +547,11 @@
binding description. This includes all the message exchanges described by operations in
the <code>DelayedDataInterface</code>.</p><p>As mentioned earlier, providers have the option to convey requirements, such as the use
of addressing or security, through word-of-mouth and documentation – as they always have.
- The absence of policy expressions in a WSDL document does not indicate anything about the
+ The absence of policy expressions, for example, in a WSDL document does not indicate anything about the
capabilities and requirements of a service. The service may have capabilities and
requirements that can be expressed as policy expressions, such as the use of addressing,
security and optimization. Or, the service may not have such capabilities and
- requirements. A policy aware client should not conclude anything (other than ‘no claims’)
+ requirements. A policy aware client should not conclude anything
about the absence of policy expressions.</p><p>Service providers, like Contoso, can preserve and leverage their investments in WSDL and
represent the capabilities and requirements of a Web service as policies. A WSDL document
may specify varying behaviors across Web service endpoints. Web service developers
@@ -1477,4 +1482,8 @@
to <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4255">issue 4255</a>
(editors action
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/192">192</a>).
+ </td></tr><tr><td rowspan="1" colspan="1">20070315</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Implemented the <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4288#c4">resolution</a>
+ for <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4288">issue 4288</a>.
+ Editors' action
+ <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/196">196</a>.
</td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
Index: ws-policy-primer.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer.xml,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -d -r1.37 -r1.38
--- ws-policy-primer.xml 16 Mar 2007 01:46:05 -0000 1.37
+++ ws-policy-primer.xml 16 Mar 2007 03:16:10 -0000 1.38
@@ -433,9 +433,14 @@
</ExactlyOne>
</All></eg>
</example>
- <p>Contoso is able to meet their customer needs by adding optional support for the Optimized
- MIME Serialization. An optional policy assertion represents a behavior that may be
- engaged.</p>
+ <p>Contoso is able to meet their customer needs by adding optional support for the Optimized MIME
+ Serialization. Optional support is outlined in section 3.4 &framework.title; and
+ detailed in section 4.5.2, &guidelines.title;, specifically for Optimized MIME Serialization.
+ An optional policy assertion represents a behavior that may be engaged. When a
+ policy assertion is absent from a policy vocabulary (See section 3.2, &framework.title;),
+ a policy-aware client should not conclude anything (other than ‘no claims’)
+ about the absence of that policy assertion. See section
+ <specref ref="attaching-policy-expressions-to-wsdl"/> on the absence of policy expressions.</p>
</div2>
<div2 id="ignorable-policy-assertions">
<head>Ignorable Policy Expressions</head>
@@ -710,11 +715,11 @@
the <code>DelayedDataInterface</code>.</p>
<p>As mentioned earlier, providers have the option to convey requirements, such as the use
of addressing or security, through word-of-mouth and documentation – as they always have.
- The absence of policy expressions in a WSDL document does not indicate anything about the
+ The absence of policy expressions, for example, in a WSDL document does not indicate anything about the
capabilities and requirements of a service. The service may have capabilities and
requirements that can be expressed as policy expressions, such as the use of addressing,
security and optimization. Or, the service may not have such capabilities and
- requirements. A policy aware client should not conclude anything (other than ‘no claims’)
+ requirements. A policy aware client should not conclude anything
about the absence of policy expressions.</p>
<p>Service providers, like Contoso, can preserve and leverage their investments in WSDL and
represent the capabilities and requirements of a Web service as policies. A WSDL document
@@ -2248,7 +2253,17 @@
href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/192">192</loc>).
</td>
- </tr>
+ </tr>
+ <tr>
+ <td>20070315</td>
+ <td>ASV</td>
+ <td>Implemented the <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4288#c4">resolution</loc>
+ for <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4288">issue 4288</loc>.
+ Editors' action
+ <loc
+ href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/196">196</loc>.
+ </td>
+ </tr>
</tbody>
</table>
</inform-div1>
Received on Friday, 16 March 2007 03:16:16 UTC