- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 18 Jan 2007 00:25:39 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv31923
Modified Files:
ws-policy-attachment.html ws-policy-attachment.xml
Log Message:
Applied the resolution for issues 4045 and 4127 using first (http://www.w3.org/Bugs/Public/show_bug.cgi?id=4045#c2) and second (http://www.w3.org/Bugs/Public/show_bug.cgi?id=4045#c3) parts as outlined in working group resolution (http://www.w3.org/2007/01/17-ws-policy-irc#T22-50-02) This closes editors actions 139 (http://www.w3.org/2005/06/tracker/wspolicyeds/actions/139) and 111 (http://www.w3.org/2005/06/tracker/wspolicyeds/actions/111)
Index: ws-policy-attachment.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.xml,v
retrieving revision 1.75
retrieving revision 1.76
diff -u -d -r1.75 -r1.76
--- ws-policy-attachment.xml 16 Jan 2007 22:09:36 -0000 1.75
+++ ws-policy-attachment.xml 18 Jan 2007 00:25:36 -0000 1.76
@@ -761,6 +761,12 @@
IRI or IRI References (such as endpoint, message or operation definitions) with which
<termref def="policy">policies</termref> can be associated. For example, URI domain expressions can be used
to identify WSDL 1.1 definitions, WSDL 2.0 components, etc.
+ When a URI
+ domain expression identifies multiple resources, i.e. WSDL 1.1 supports multiple
+ operations with the same name (sometimes called operation name overloading),
+ the Policy applies to all the resources that are identified.
+ </p>
+ <p>
IRI References for WSDL 2.0 components
are defined in Appendix C of the Web Services Description Language (WSDL) Version 2.0
Part 1: Core Language [<bibref ref="WSDL20"/>]. The following
@@ -775,8 +781,15 @@
<p>In this example, the <termref def="policy_expression">policy expression</termref> at
<code>http://www.example.com/policies#RmPolicy</code> applies to all interactions with
the endpoint at <code>http://example.org/TicketAgent.wsdl20#wsdl.endpoint(TicketAgentService/Endpoint)</code>.
- Similarly, an XPointer [<bibref ref="XPointer"/>] can be used as an
- IRI Reference to identify a description in a WSDL 1.1 [<bibref ref="WSDL11"/>] document.</p>
+ </p>
+ <p>
+ IRI References for WSDL 1.1 elements are defined in WSDL 1.1 Element Identifiers [<bibref ref="WSDL11EI" />].
+ </p>
+ <p>
+ The scope of URI domain expressions for WSDL 2.0 components or WSDL 1.1
+ elements is limited to the subjects defined in this specification at (ref to
+ Attaching Policies Using WSDL 1.1 and WS-Policy Attachment for WSDL 2.0).
+ </p>
</div3>
</div2>
@@ -792,41 +805,69 @@
</div1>
<div1 id="AttachingPolicyUsingWSDL1.1">
<head>Attaching Policies Using WSDL 1.1</head>
-<p>The <rfc2119>RECOMMENDED</rfc2119> means of associating a <termref def="policy">policy</termref>
-with a <termref def="policy_subject">policy subject</termref> that has a WSDL 1.1 [<bibref ref="WSDL11"/>]
-description is to attach a reference to the <termref def="policy">policy</termref> within the WSDL
-component corresponding to the target <termref def="policy_subject">policy subject</termref>. </p>
-<p>WSDL 1.1 disallows the use of extensibility elements on certain
-elements and the use of extensibility attributes on others. However,
-the WS-I Basic Profile 1.1 [<bibref ref="BP11"/>] overrules this
-restriction and allows element extensibility everywhere. Therefore,
-the <termref def="policy">policy</termref> reference <rfc2119>SHOULD</rfc2119> be attached using
-<el>wsp:PolicyReference</el> as child element unless it is
-absolutely necessary to maintain the original WSDL 1.1 restriction, in
-which case the <att>@wsp:PolicyURIs</att> attribute MAY be used
-for the following WSDL elements:</p>
-<ulist>
-<item>
-<p>
-<el>wsdl11:portType</el>
-</p>
-</item>
-<item>
-<p>
-<el>wsdl11:portType/wsdl11:operation/wsdl11:input</el>
-</p>
-</item>
-<item>
-<p>
-<el>wsdl11:portType/wsdl11:operation/wsdl11:output</el>
-</p>
-</item>
-<item>
-<p>
-<el>wsdl11:portType/wsdl11:operation/wsdl11:fault</el>
+ <p>
+ This section describes a mechanism for associating policy expressions with Web service constructs in WSDL 1.1 [<bibref ref="WSDL11"/>].
+ The mechanism consists of:
+ </p>
+ <ulist>
+ <item>
+ <p>A model for attaching policies to WSDL 1.1 constructs.</p>
+ <p> The model defines:
+ <ulist>
+ <item>
+ <p>A partitioning of WSDL constructs into service, endpoint, operation
+ and message policy subjects.
+ </p>
+ </item>
+ <item><p>
+ The semantics of attaching a <termref def="policy">policy</termref>
+ to each <termref def="policy_subject">policy subject</termref>
+</p></item>
+ <item><p>
+ How to combine policies attached to more than one WSDL construct
+ within a single policy subject.
+ </p></item>
+ </ulist></p>
+ </item>
+ <item><p>
+ An XML representation of policy expressions attached to WSDL 1.1 constructs.
+ </p></item>
+ <item><p>
+ The annotation of such policy expressions as required extensions using the
+ WSDL-defined extensibility flag <att>@wsdl:required</att>.
+ </p></item>
+ </ulist>
+ <p>
+ WSDL 1.1 disallows the use of extensibility elements on certain elements and
+ the use of extensibility attributes on others. However, the WS-I Basic Profile 1.1
+ [<bibref ref="BP11" />] overrules this restriction and allows element extensibility everywhere.
+
+ Therefore, when attaching a reference directly to the WSDL element the policy
+
+ reference SHOULD be attached using <el>wsp:PolicyReference</el> as child element unless
+ it
+
+ is absolutely necessary to maintain the original WSDL 1.1 restriction, in which
+
+ case the <att>@wsp:PolicyURIs</att> attribute MAY be used for the following WSDL elements:
+ <ulist>
+ <item><p>
+ <el>wsdl11:portType</el>
+ </p></item>
+ <item>
+ <p>
+ <el>wsdl11:portType/wsdl11:operation/wsdl11:input</el>
+ </p></item>
+ <item>
+ <p>
+ <el>wsdl11:portType/wsdl11:operation/wsdl11:output</el>
+ </p></item>
+ <item>
+ <p>
+ <el>wsdl11:portType/wsdl11:operation/wsdl11:fault</el>
+ </p></item>
+ </ulist>
</p>
-</item>
-</ulist>
<p>If it is necessary to include the actual <termref def="policy_expression">policy expressions</termref> within
the WSDL description itself, it is <rfc2119>RECOMMENDED</rfc2119> that
their <el>wsp:Policy</el> elements be included as children of
@@ -1176,8 +1217,10 @@
</p>
</item>
<item>
-<p>An XML representation of policy expressions attached to WSDL 2.0 constructs
- and annotating those policy expressions as required extensions using the
+<p>An XML representation of policy expressions attached to WSDL 2.0 constructs.</p>
+ </item>
+ <item><p>
+ The annotation those policy expressions as required extensions using the
WSDL-defined extensibility flag <code>@wsdl20:required</code>.</p>
</item>
</ulist>
@@ -2476,10 +2519,16 @@
<div2 id="Informative-References">
<head>Other References</head>
<blist>
+
<bibl key="IETF RFC 3023"
href="http://www.ietf.org/rfc/rfc2246.txt" id="RFC2246">IETF
"RFC 2246: The TLS Protocol", T. Dierks, C. Allen, January
1999.</bibl>
+ <bibl id="WSDL11EI" key="WSDL11 ElementIds" href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/wsdl11elementidentifiers.html">
+ <titleref>WSDL 1.1 Element Identifiers</titleref>
+ D. Orchard, Editor. World Wide Web Consortium, 15 November 2006.
+ TBD: URI
+ </bibl>
<bibl key="MTOM" id="MTOM" href="http://www.w3.org/TR/2005/REC-soap12-mtom-20050125/">
<titleref>SOAP Message Transmission Optimization Mechanism</titleref>, M. Gudgin, N.
Mendelsohn, M. Nottingham and H. Ruellan, Editors. World Wide Web Consortium, 25 January
@@ -3106,7 +3155,7 @@
</tr>
<tr>
<td>20061218</td>
- <td>FH</td>
+ <td>FJH</td>
<td>Implemented the
<loc href="http://www.w3.org/2006/12/13-ws-policy-irc#T17-45-16">resolution</loc> for issue
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4039">4039</loc> to close editors' action
@@ -3135,7 +3184,17 @@
<loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/116">116</loc> and
<loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/124">124</loc>
Resolution for issue <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4211">4211</loc></td>
- </tr>
+ </tr>
+ <tr>
+ <td>20070117</td>
+ <td>FJH</td>
+ <td>Applied the resolution for issues 4045 and 4127 using <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4045#c2">first</loc>
+ and <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4045#c3">second</loc> parts as outlined in working group
+ <loc href="http://www.w3.org/2007/01/17-ws-policy-irc#T22-50-02">resolution</loc>. This closes editors actions
+ <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/139">139</loc> and
+ <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/111">111</loc>.
+ </td>
+ </tr>
</tbody>
</table>
</inform-div1>
Index: ws-policy-attachment.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.html,v
retrieving revision 1.75
retrieving revision 1.76
diff -u -d -r1.75 -r1.76
--- ws-policy-attachment.html 16 Jan 2007 22:09:36 -0000 1.75
+++ ws-policy-attachment.html 18 Jan 2007 00:25:35 -0000 1.76
@@ -65,7 +65,7 @@
</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="#tocRange">Introduction</a><br>2. <a href="#NotationsTerminology">Notations and Terminology</a><br> 2.1 <a href="#NotationalConventions">Notational Conventions</a><br> 2.2 <a href="#XMLNamespaces">XML Namespaces</a><br> 2.3 <a href="#Glossary">Terminology</a><br> 2.4 <a href="#Example">Example</a><br>3. <a href="#rPolicyAttachment">Policy Attachment</a><br> 3.1 <a href="#rEffectivePolicy">Effective Policy</a><br> 3.2 <a href="#PolicyAttachmentMechanisms">Policy Attachment Mechanisms</a><br> 3.3 <a href="#XMLElementAttachement">XML Element Attachment</a><br> 3.4 <a href="#ExternalPolicyAttachment">External Policy Attachment</a><br> 3.4.1 <a href="#uri-domain-expression">URI Domain Expression</a><br> &bsp; 3.5 <a href="#IRI_Policy_Attachment">Use of IRIs in Policy Attachment</a><br>4. <a href="#AttachingPolicyUsingWSDL1.1">Attaching Policies Using WSDL 1.1</a><br> 4.1 <a href="#CalculatingEffectivyPolicywithWSDL1.1">Calculating Effective Policy in WSDL 1.1</a><br> 4.1.1 <a href="#ServicePolicySubject">Service Policy Subject</a><br> 4.1.2 <a href="#EndpointPolicySubject">Endpoint Policy Subject</a><br> 4.1.3 <a href="#OperationPolicySubject">Operation Policy Subject</a><br> 4.1.4 <a href="#MessagePolicySubject">Message Policy Subject</a><br> 4.1.5 <a href="#Example2">Example</a><br>5. <a href="#ws-policy-attachment-for-wsdl20">WS-Policy Attachment for WSDL 2.0</a><br> 5.1 <a href="#wsdl20-example">Example</a><br> nbsp; 5.2 <a href="#attaching-policy-expressions">Attaching Policy Expressions</a><br> 5.3 <a href="#extension-to-wsdl-component-model">Extension to WSDL Component Model</a><br> 5.4 <a href="#effective-policy">Effective Policy</a><br> 5.4.1 <a href="#service-policy-subject">Service Policy Subject</a><br> 5.4.2 <a href="#endpoint-policy-subject">Endpoint Policy Subject</a><br> 5.4.3 <a href="#operation-policy-subject">Operation Policy Subject</a><br> 5.4.4 <a href="#message-policy-subject-input">Message Policy Subject (input message)</a><br> 5.4.5 <a href="#message-policy-subject-output">Message Policy Subject (output message)</a><br> 5.4.6 <a href="#message-policy-subject-inut-fault">Message Policy Subject (input fault message)</a><br> 5.4.7 <a href="#message-policy-subject-output-fault">Message Policy Subject (output fault message)</a><br>6. <a href="#AttachingPoliciesUsingUDDI">Attaching Policies Using UDDI</a><br> 6.1 <a href="#CalculatingEffectivePolicyElementPolicyUDDI">Calculating Effective Policy and Element Policy in UDDI</a><br> 6.1.1 <a href="#ServiceProviderPolicySubjectUDDI">Service Provider Policy Subject</a><br> 6.1.2 <a href="#ServicePolicySubjectUDDI">Service Policy Subject</a><br> 6.1.3 <a href="#EndpointPolicySubjectUDDI">Endpoint Policy Subject</a><br> 6.2 <a href="#ReferencingRemotePolicyExpressions">Referencing Remote Policy Expressions</a><br> 6.3 <a href="#RegisteringReusablePolicyExpressions">Registerng Reusable Policy Expressions</a><br> 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="#d3e3972">External Policy Attachment Conformance</a><br> 8.2 <a href="#d3e3984">WSDL 1.1 Attachment Conformance</a><br> 8.3 <a href="#d3e3993">WSDL 2.0 Attachment Conformance</a><br></p>
+<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#tocRange">Introduction</a><br>2. <a href="#NotationsTerminology">Notations and Terminology</a><br> 2.1 <a href="#NotationalConventions">Notational Conventions</a><br> 2.2 <a href="#XMLNamespaces">XML Namespaces</a><br> 2.3 <a href="#Glossary">Terminology</a><br> 2.4 <a href="#Example">Example</a><br>3. <a href="#rPolicyAttachment">Policy Attachment</a><br> 3.1 <a href="#rEffectivePolicy">Effective Policy</a><br> 3.2 <a href="#PolicyAttachmentMechanisms">Policy Attachment Mechanisms</a><br> 3.3 <a href="#XMLElementAttachement">XML Element Attachment</a><br> 3.4 <a href="#ExternalPolicyAttachment">External Policy Attachment</a><br> 3.4.1 <a href="#uri-domain-expression">URI Domain Expression</a><br> &bsp; 3.5 <a href="#IRI_Policy_Attachment">Use of IRIs in Policy Attachment</a><br>4. <a href="#AttachingPolicyUsingWSDL1.1">Attaching Policies Using WSDL 1.1</a><br> 4.1 <a href="#CalculatingEffectivyPolicywithWSDL1.1">Calculating Effective Policy in WSDL 1.1</a><br> 4.1.1 <a href="#ServicePolicySubject">Service Policy Subject</a><br> 4.1.2 <a href="#EndpointPolicySubject">Endpoint Policy Subject</a><br> 4.1.3 <a href="#OperationPolicySubject">Operation Policy Subject</a><br> 4.1.4 <a href="#MessagePolicySubject">Message Policy Subject</a><br> 4.1.5 <a href="#Example2">Example</a><br>5. <a href="#ws-policy-attachment-for-wsdl20">WS-Policy Attachment for WSDL 2.0</a><br> 5.1 <a href="#wsdl20-example">Example</a><br> nbsp; 5.2 <a href="#attaching-policy-expressions">Attaching Policy Expressions</a><br> 5.3 <a href="#extension-to-wsdl-component-model">Extension to WSDL Component Model</a><br> 5.4 <a href="#effective-policy">Effective Policy</a><br> 5.4.1 <a href="#service-policy-subject">Service Policy Subject</a><br> 5.4.2 <a href="#endpoint-policy-subject">Endpoint Policy Subject</a><br> 5.4.3 <a href="#operation-policy-subject">Operation Policy Subject</a><br> 5.4.4 <a href="#message-policy-subject-input">Message Policy Subject (input message)</a><br> 5.4.5 <a href="#message-policy-subject-output">Message Policy Subject (output message)</a><br> 5.4.6 <a href="#message-policy-subject-inut-fault">Message Policy Subject (input fault message)</a><br> 5.4.7 <a href="#message-policy-subject-output-fault">Message Policy Subject (output fault message)</a><br>6. <a href="#AttachingPoliciesUsingUDDI">Attaching Policies Using UDDI</a><br> 6.1 <a href="#CalculatingEffectivePolicyElementPolicyUDDI">Calculating Effective Policy and Element Policy in UDDI</a><br> 6.1.1 <a href="#ServiceProviderPolicySubjectUDDI">Service Provider Policy Subject</a><br> 6.1.2 <a href="#ServicePolicySubjectUDDI">Service Policy Subject</a><br> 6.1.3 <a href="#EndpointPolicySubjectUDDI">Endpoint Policy Subject</a><br> 6.2 <a href="#ReferencingRemotePolicyExpressions">Referencing Remote Policy Expressions</a><br> 6.3 <a href="#RegisteringReusablePolicyExpressions">Registerng Reusable Policy Expressions</a><br> 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="#d3e3989">External Policy Attachment Conformance</a><br> 8.2 <a href="#d3e4001">WSDL 1.1 Attachment Conformance</a><br> 8.3 <a href="#d3e4010">WSDL 2.0 Attachment Conformance</a><br></p>
<h3><a name="appendix" id="appendix">Appendices</a></h3><p class="toc">A. <a href="#References">References</a><br> A.1 <a href="#Normative-References">Normative References</a><br> A.2 <a href="#Informative-References">Other References</a><br>B. <a href="#AppendixA">UDDI tModel Definitions</a><br> B.1 <a href="#RemotePolicyReferenceCategorySystem">Remote Policy Reference Category System</a><br> B.1.1 <a href="#DesigGoals1">Design Goals</a><br> B.1.2 <a href="#tModelDefinition1">tModel Definition</a><br> B.1.3 <a href="#ModelStructure1">tModel Structure</a><br> B.2 <a href="#WS-PolicyTypesCategorySystem">Web Services Policy Types Category System</a><br> B.2.1 <a href="#DesignGoals2">Design Goals</a><br> &bsp; B.2.2 <a href="#tModelDefinition2">tModel Definition</a><br> B.2.3 <a href="#ModelStructure2">tModel Structure</a><br> B.3 <a href="#LocalPolicyReferenceCategorySystem">Local Policy Reference Category System</a><br> B.3.1 <a href="#DesignGoals3">Design Goals</a><br> B.3.2 <a href="#tModelDefinition3">tModel Definition</a><br> B.3.3 <a href="#ModelStructure3">tModel Structure</a><br>C. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>D. <a href="#change-description">Changes in this Version of the Document</a> (Non-Normative)<br>E. <a href="#change-log">Web Services Policy 1.5 - Attachment Change Log</a> (Non-Normative)<br></p></div><hr><div class="body"><div class="div1">
<h2><a name="tocRange"></a>1. Introduction</h2><p>
The Web Services Policy 1.5 - Framework [<cite><a href="#WS-Policy">Web Services Policy Framework</a></cite>]
@@ -494,6 +494,11 @@
IRI or IRI References (such as endpoint, message or operation definitions) with which
<a title="" href="#policy">policies</a> can be associated. For example, URI domain expressions can be used
to identify WSDL 1.1 definitions, WSDL 2.0 components, etc.
+ When a URI
+ domain expression identifies multiple resources, i.e. WSDL 1.1 supports multiple
+ operations with the same name (sometimes called operation name overloading),
+ the Policy applies to all the resources that are identified.
+ </p><p>
IRI References for WSDL 2.0 components
are defined in Appendix C of the Web Services Description Language (WSDL) Version 2.0
Part 1: Core Language [<cite><a href="#WSDL20">WSDL 2.0 Core Language</a></cite>]. The following
@@ -506,34 +511,59 @@
(06) </wsp:PolicyAttachment></pre></div><p>In this example, the <a title="" href="#policy_expression">policy expression</a> at
<code>http://www.example.com/policies#RmPolicy</code> applies to all interactions with
the endpoint at <code>http://example.org/TicketAgent.wsdl20#wsdl.endpoint(TicketAgentService/Endpoint)</code>.
- Similarly, an XPointer [<cite><a href="#XPointer">XPointer Framework</a></cite>] can be used as an
- IRI Reference to identify a description in a WSDL 1.1 [<cite><a href="#WSDL11">WSDL 1.1</a></cite>] document.</p></div></div><div class="div2">
+ </p><p>
+ IRI References for WSDL 1.1 elements are defined in WSDL 1.1 Element Identifiers [<cite><a href="#WSDL11EI">WSDL11 ElementIds</a></cite>].
+ </p><p>
+ The scope of URI domain expressions for WSDL 2.0 components or WSDL 1.1
+ elements is limited to the subjects defined in this specification at (ref to
+ Attaching Policies Using WSDL 1.1 and WS-Policy Attachment for WSDL 2.0).
+ </p></div></div><div class="div2">
<h3><a name="IRI_Policy_Attachment"></a>3.5 Use of IRIs in Policy Attachment</h3><p>
Policy attachment mechanisms use IRIs for some identifiers. This
document does not define a base URI but relies
on the mechanisms defined in XML Base [<cite><a href="#XMLBASE">XML BASE</a></cite>] and RFCs 3023 [<cite><a href="#RFC3023">IETF RFC 3023</a></cite>],
3986 [<cite><a href="#RFC3986">IETF RFC 3986</a></cite>] and 3987 [<cite><a href="#RFC3987">IETF RFC 3987</a></cite>]
for establishing a base URI against which relative IRIs can be made absolute.</p></div></div><div class="div1">
-<h2><a name="AttachingPolicyUsingWSDL1.1"></a>4. Attaching Policies Using WSDL 1.1</h2><p>The <span class="rfc2119">RECOMMENDED</span> means of associating a <a title="" href="#policy">policy</a>
-with a <a title="" href="#policy_subject">policy subject</a> that has a WSDL 1.1 [<cite><a href="#WSDL11">WSDL 1.1</a></cite>]
-description is to attach a reference to the <a title="" href="#policy">policy</a> within the WSDL
-component corresponding to the target <a title="" href="#policy_subject">policy subject</a>. </p><p>WSDL 1.1 disallows the use of extensibility elements on certain
-elements and the use of extensibility attributes on others. However,
-the WS-I Basic Profile 1.1 [<cite><a href="#BP11">BP 1.1</a></cite>] overrules this
-restriction and allows element extensibility everywhere. Therefore,
-the <a title="" href="#policy">policy</a> reference <span class="rfc2119">SHOULD</span> be attached using
-<code class="elt">wsp:PolicyReference</code> as child element unless it is
-absolutely necessary to maintain the original WSDL 1.1 restriction, in
-which case the <code class="attr">@wsp:PolicyURIs</code> attribute MAY be used
-for the following WSDL elements:</p><ul><li><p>
-<code class="elt">wsdl11:portType</code>
-</p></li><li><p>
-<code class="elt">wsdl11:portType/wsdl11:operation/wsdl11:input</code>
-</p></li><li><p>
-<code class="elt">wsdl11:portType/wsdl11:operation/wsdl11:output</code>
+<h2><a name="AttachingPolicyUsingWSDL1.1"></a>4. Attaching Policies Using WSDL 1.1</h2><p>
+ This section describes a mechanism for associating policy expressions with Web service constructs in WSDL 1.1 [<cite><a href="#WSDL11">WSDL 1.1</a></cite>].
+ The mechanism consists of:
+ </p><ul><li><p>A model for attaching policies to WSDL 1.1 constructs.</p><p> The model defines:
+ <ul><li><p>A partitioning of WSDL constructs into service, endpoint, operation
+ and message policy subjects.
+ </p></li><li><p>
+ The semantics of attaching a <a title="" href="#policy">policy</a>
+ to each <a title="" href="#policy_subject">policy subject</a>
</p></li><li><p>
-<code class="elt">wsdl11:portType/wsdl11:operation/wsdl11:fault</code>
-</p></li></ul><p>If it is necessary to include the actual <a title="" href="#policy_expression">policy expressions</a> within
+ How to combine policies attached to more than one WSDL construct
+ within a single policy subject.
+ </p></li></ul></p></li><li><p>
+ An XML representation of policy expressions attached to WSDL 1.1 constructs.
+ </p></li><li><p>
+ The annotation of such policy expressions as required extensions using the
+ WSDL-defined extensibility flag <code class="attr">@wsdl:required</code> .
+ </p></li></ul><p>
+ WSDL 1.1 disallows the use of extensibility elements on certain elements and
+ the use of extensibility attributes on others. However, the WS-I Basic Profile 1.1
+ [<cite><a href="#BP11">BP 1.1</a></cite>] overrules this restriction and allows element extensibility everywhere.
+
+ Therefore, when attaching a reference directly to the WSDL element the policy
+
+ reference SHOULD be attached using <code class="elt">wsp:PolicyReference</code> as child element unless
+ it
+
+ is absolutely necessary to maintain the original WSDL 1.1 restriction, in which
+
+ case the <code class="attr">@wsp:PolicyURIs</code> attribute MAY be used for the following WSDL elements:
+ <ul><li><p>
+ <code class="elt">wsdl11:portType</code>
+ </p></li><li><p>
+ <code class="elt">wsdl11:portType/wsdl11:operation/wsdl11:input</code>
+ </p></li><li><p>
+ <code class="elt">wsdl11:portType/wsdl11:operation/wsdl11:output</code>
+ </p></li><li><p>
+ <code class="elt">wsdl11:portType/wsdl11:operation/wsdl11:fault</code>
+ </p></li></ul>
+</p><p>If it is necessary to include the actual <a title="" href="#policy_expression">policy expressions</a> within
the WSDL description itself, it is <span class="rfc2119">RECOMMENDED</span> that
their <code class="elt">wsp:Policy</code> elements be included as children of
the <code class="elt">wsdl11:definition</code> element, and referenced using
@@ -757,8 +787,8 @@
service constructs in WSDL 2.0. The mechanism consists of:</p><ul><li><p>A model for attaching policies to WSDL 2.0 constructs. The model defines:<ul><li><p>A partitioning of WSDL constructs into service, endpoint, operation
and message policy subjects.</p></li><li><p>The semantics of attaching a policy to each policy subject.</p></li><li><p>How to combine policies attached to more than one WSDL component
within a single policy subject.</p></li></ul>
-</p></li><li><p>An XML representation of policy expressions attached to WSDL 2.0 constructs
- and annotating those policy expressions as required extensions using the
+</p></li><li><p>An XML representation of policy expressions attached to WSDL 2.0 constructs.</p></li><li><p>
+ The annotation those policy expressions as required extensions using the
WSDL-defined extensibility flag <code>@wsdl20:required</code>.</p></li></ul><p>
<a href="#XMLNamespaces"><b>2.2 XML Namespaces</b></a> lists all the XML Namespaces that are used in this section. (XML
elements without a namespace prefix are from the Web Services Policy XML Namespace.)</p><div class="div2">
@@ -1367,11 +1397,11 @@
Security Considerations section of the Web Services Policy 1.5 - Framework document [<cite><a href="#WS-Policy">Web Services Policy Framework</a></cite>].
</p></div><div class="div1">
<h2><a name="Conformance"></a>8. Conformance</h2><div class="div2">
-<h3><a name="d3e3972"></a>8.1 External Policy Attachment Conformance</h3><p>An element information item whose namespace name is "http://www.w3.org/@@@@/@@/ws-policy" and whose local part is PolicyAttachment conforms to this specification if it is valid according to the XML Schema [<cite><a href="#XMLSchemaPart1">XML Schema Structures</a></cite>] for that element as defined by this specification (<a href="http://www.w3.org/@@@@/@@/ws-policy.xsd">http://www.w3.org/@@@@/@@/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="d3e3984"></a>8.2 WSDL 1.1 Attachment Conformance</h3><p>
+<h3><a name="d3e3989"></a>8.1 External Policy Attachment Conformance</h3><p>An element information item whose namespace name is "http://www.w3.org/@@@@/@@/ws-policy" and whose local part is PolicyAttachment conforms to this specification if it is valid according to the XML Schema [<cite><a href="#XMLSchemaPart1">XML Schema Structures</a></cite>] for that element as defined by this specification (<a href="http://www.w3.org/@@@@/@@/ws-policy.xsd">http://www.w3.org/@@@@/@@/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="d3e4001"></a>8.2 WSDL 1.1 Attachment Conformance</h3><p>
A WSDL 1.1 [<cite><a href="#WSDL11">WSDL 1.1</a></cite>] 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="d3e3993"></a>8.3 WSDL 2.0 Attachment Conformance</h3><p>
+<h3><a name="d3e4010"></a>8.3 WSDL 2.0 Attachment Conformance</h3><p>
A WSDL 2.0 [<cite><a href="#WSDL20">WSDL 2.0 Core Language</a></cite>] 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"></a>A. References</h2><div class="div2">
@@ -1505,7 +1535,11 @@
</dd></dl></div><div class="div2">
<h3><a name="Informative-References"></a>A.2 Other References</h3><dl><dt class="label"><a name="RFC2246"></a>[IETF RFC 3023] </dt><dd>IETF
"RFC 2246: The TLS Protocol", T. Dierks, C. Allen, January
- 1999. (See <cite><a href="http://www.ietf.org/rfc/rfc2246.txt">http://www.ietf.org/rfc/rfc2246.txt</a></cite>.)</dd><dt class="label"><a name="MTOM"></a>[MTOM] </dt><dd>
+ 1999. (See <cite><a href="http://www.ietf.org/rfc/rfc2246.txt">http://www.ietf.org/rfc/rfc2246.txt</a></cite>.)</dd><dt class="label"><a name="WSDL11EI"></a>[WSDL11 ElementIds] </dt><dd>
+ <cite><a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/wsdl11elementidentifiers.html">WSDL 1.1 Element Identifiers</a></cite>
+ D. Orchard, Editor. World Wide Web Consortium, 15 November 2006.
+ TBD: URI
+ </dd><dt class="label"><a name="MTOM"></a>[MTOM] </dt><dd>
<cite><a href="http://www.w3.org/TR/2005/REC-soap12-mtom-20050125/">SOAP Message Transmission Optimization Mechanism</a></cite>, 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
@@ -1798,7 +1832,7 @@
<a href="http://lists.w3.org/Archives/Public/public-ws-policy-eds/2006Nov/0033.html">Frederick</a> and
<a href="http://lists.w3.org/Archives/Public/public-ws-policy-eds/2006Nov/0054.html">Umit</a> to the list of editors.
Editors' action <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/86">86</a>.
- </td></tr><tr><td rowspan="1" colspan="1">20061218</td><td rowspan="1" colspan="1">FH</td><td rowspan="1" colspan="1">Implemented the
+ </td></tr><tr><td rowspan="1" colspan="1">20061218</td><td rowspan="1" colspan="1">FJH</td><td rowspan="1" colspan="1">Implemented the
<a href="http://www.w3.org/2006/12/13-ws-policy-irc#T17-45-16">resolution</a> for issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4039">4039</a> to close editors' action
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/99">99</a>.
@@ -1810,4 +1844,9 @@
</td></tr><tr><td rowspan="1" colspan="1">20070116</td><td rowspan="1" colspan="1">DBO</td><td rowspan="1" colspan="1">Completed action item:
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/116">116</a> and
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/124">124</a>
- Resolution for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4211">4211</a></td></tr></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=4211">4211</a></td></tr><tr><td rowspan="1" colspan="1">20070117</td><td rowspan="1" colspan="1">FJH</td><td rowspan="1" colspan="1">Applied the resolution for issues 4045 and 4127 using <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4045#c2">first</a>
+ and <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4045#c3">second</a> parts as outlined in working group
+ <a href="http://www.w3.org/2007/01/17-ws-policy-irc#T22-50-02">resolution</a>. This closes editors actions
+ <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/139">139</a> and
+ <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/111">111</a>.
+ </td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
Received on Thursday, 18 January 2007 00:26:02 UTC