- From: Asir Vedamuthu via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 10 Nov 2006 04:50:40 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv24823
Modified Files:
ws-policy.xsd ws-policy-attachment.html
ws-policy-attachment.xml
Log Message:
Implemented the resolution for issues 3599 and 3730.
Index: ws-policy-attachment.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.html,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -d -r1.68 -r1.69
--- ws-policy-attachment.html 10 Nov 2006 02:21:23 -0000 1.68
+++ ws-policy-attachment.html 10 Nov 2006 04:50:37 -0000 1.69
@@ -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>4. <a href="#AttachingPolicyUsingWSDL1.1">Attaching Policies Using WSDL 1.1</a><br> 4.1 <a href="#CaculatingEffectivyPolicywithWSDL1.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> 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-input-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>. <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">Registering 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="#d3e3874">External Policy Attachment Conformance</a><br> 8.2 <a href="#d3e3886">WSDL 1.1 Attachment Conformance</a><br> 8.3 <a href="#d3e3895">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>4. <a hef="#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> 5.2 <a href="#attaching-policy-expressions">Attaching Policy Expressions</a><br>&nbp; 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-input-fault">Message Policy Subject (input fault message)</a><br> &nsp; 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">Registering Reusable Policy Expressions</a><br> 6.4 <a href="#RegisteringPoliciesUDDIVrsion3">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="#d3e3942">External Policy Attachment Conformance</a><br> 8.2 <a href="#d3e3954">WSDL 1.1 Attachment Conformance</a><br> 8.3 <a href="#d3e3963">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>]
@@ -106,7 +106,7 @@
<code>mtom</code>
</td><td rowspan="1" colspan="1">
<code>http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization</code>
-</td><td rowspan="1" colspan="1">[<a href="http://131.107.72.15/MTOM_Service_Indigo/">WS-OptimizedSerializationPolicy</a>]</td></tr><tr><td rowspan="1" colspan="1">
+</td><td rowspan="1" colspan="1">[<cite><a href="#WS-MTOMPolicy">WS-MTOMPolicy</a></cite>]</td></tr><tr><td rowspan="1" colspan="1">
<code>rmp</code>
</td><td rowspan="1" colspan="1">
<code>http://docs.oasis-open.org/ws-rx/wsrmp/200602</code>
@@ -455,8 +455,9 @@
WS-Security [<cite><a href="#WS-Security">WS-Security 2004</a></cite>].</p></dd><dt class="label">
<code class="attr">/wsp:PolicyAttachment/@{any}</code>
</dt><dd><p>Additional attributes <span class="rfc2119">MAY</span> be specified but
-<span class="rfc2119">MUST NOT</span> contradict the semantics of the owner
-element; if an attribute is not recognized, it
+ <span class="rfc2119">MUST NOT</span> contradict the semantics of the
+ <strong>[owner element]</strong>;
+ if an attribute is not recognized, it
<span class="rfc2119">SHOULD</span> be ignored.</p></dd><dt class="label">
<code class="elt">/wsp:PolicyAttachment/{any}</code>
</dt><dd><p>Other child elements for binding constructs
@@ -477,7 +478,36 @@
(09) </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://www.example.com/acct</code>.</p></div></div><div class="div1">
+<code>http://www.example.com/acct</code>.</p><div class="div3">
+<h4><a name="uri-domain-expression"></a>3.4.1 URI Domain Expression</h4><p>This section defines a domain expression for identifying resources as
+ <a title="" href="#policy_subject">policy subjects</a> for the external attachment mechanism. The following
+ is a pseudo-schema for the URI domain expression:</p><div class="exampleInner"><pre>(01) <wsp:PolicyAttachment … >
+(02) <wsp:AppliesTo>
+(03) <wsp:URI … >xs:anyURI</wsp:URI> *
+(04) </wsp:AppliesTo>
+(05) …
+(06) </wsp:PolicyAttachment></pre></div><p>The following describes the URI domain expression element listed in the pseudo-schema outlined above:</p><dl><dt class="label"><code class="attr">/wsp:PolicyAttachment/wsp:AppliesTo/wsp:URI</code> </dt><dd><p>This element is an absolute IRI that references a resource
+ as a <a title="" href="#policy_subject">policy subject</a>. There is no requirement that the IRI be resolvable;
+ retrieval mechanisms are beyond the scope of this specification.</p></dd><dt class="label"><code class="attr">/wsp:PolicyReference/wsp:AppliesTo/wsp:URI/@{any}</code> </dt><dd><p>Additional attributes <span class="rfc2119">MAY</span> be specified but <span class="rfc2119">MUST NOT</span> contradict the
+ semantics of the <strong>[owner element]</strong>; if an attribute is not recognized,
+ it <span class="rfc2119">SHOULD</span> be ignored.</p></dd></dl><p>URI domain expressions are used to identify resources that are identified using
+ 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.
+ 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
+ example illustrates the use of URI domain expression
+ with a WSDL 2.0 IRI Reference: </p><div class="exampleInner"><pre>(01) <wsp:PolicyAttachment>
+(02) <wsp:AppliesTo>
+(03) <wsp:URI>http://example.org/TicketAgent.wsdl20#wsdl.endpoint(TicketAgentService/Endpoint)</wsp:URI>
+(04) </wsp:AppliesTo>
+(05) <wsp:PolicyReference URI="http://www.example.com/policies#RmPolicy" />
+(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><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
@@ -1332,11 +1362,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="d3e3874"></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="d3e3886"></a>8.2 WSDL 1.1 Attachment Conformance</h3><p>
+<h3><a name="d3e3942"></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="d3e3954"></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="d3e3895"></a>8.3 WSDL 2.0 Attachment Conformance</h3><p>
+<h3><a name="d3e3963"></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">
@@ -1458,7 +1488,12 @@
Mendelsohn, M. Nottingham and H. Ruellan, Editors. World Wide Web Consortium, 25 January
2005. This version of the SOAP Message Transmission Optimization Mechanism Recommendation
is http://www.w3.org/TR/2005/REC-soap12-mtom-20050125/. The <a href="http://www.w3.org/TR/soap12-mtom/">latest version of SOAP Message Transmission
- Optimization Mechanism</a> is available at http://www.w3.org/TR/soap12-mtom/. </dd><dt class="label"><a name="SCC14N"></a>[SCC14N] </dt><dd>
+ Optimization Mechanism</a> is available at http://www.w3.org/TR/soap12-mtom/. </dd><dt class="label"><a name="WS-MTOMPolicy"></a>[WS-MTOMPolicy] </dt><dd>
+ <cite><a href="http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization/">MTOM Serialization Policy Assertion (WS-MTOMPolicy)</a></cite>, C. Ferris, et al,
+ Authors. International Business Machines Corporation and Microsoft
+ Corporation, Inc., September 2006. Available at
+ http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization/
+ </dd><dt class="label"><a name="SCC14N"></a>[SCC14N] </dt><dd>
<cite><a href="http://uddi.org/pubs/SchemaCentricCanonicalization-20050523.htm">Schema Centric XML Canonicalization Version
1.0</a></cite>, S. Aissi, A. Hately, and M. Hondo,
Editors. Organization for the Advancement of Structured
@@ -1511,7 +1546,16 @@
Nottingham and H. Ruellan, Editors. World Wide Web Consortium, 25 January 2005. This
version of the XML-binary Optimized Packaging Recommendation is
http://www.w3.org/TR/2005/REC-xop10-20050125/. The <a href="http://www.w3.org/TR/xop10/">latest version of XML-binary Optimized Packaging</a> is available at
- http://www.w3.org/TR/xop10/. </dd></dl></div></div><div class="div1">
+ http://www.w3.org/TR/xop10/. </dd><dt class="label"><a name="XPointer"></a>[XPointer Framework] </dt><dd>
+ <cite><a href="http://www.w3.org/TR/2003/REC-xptr-framework-20030325/">XPointer Framework</a></cite>,Paul Grosso, Eve
+ Maler, Jonathan Marsh, Norman Walsh, Editors. World Wide Web
+ Consortium, 22 November 2002. This version of the XPointer
+ Framework Proposed Recommendation is
+ http://www.w3.org/TR/2003/REC-xptr-framework-20030325/ The
+ <a href="http://www.w3.org/TR/xptr-framework/">latest
+ version of XPointer Framework</a> is available at
+ http://www.w3.org/TR/xptr-framework/.
+ </dd></dl></div></div><div class="div1">
<h2><a name="AppendixA"></a>B. UDDI tModel Definitions</h2><p>This section contains the UDDI tModel definitions for the canonical
tModels used in Section <a href="#AttachingPoliciesUsingUDDI"><b>6. Attaching Policies Using UDDI</b></a>. The tModelKeys shown in the tModel
structure sections are valid UDDI Version 2 keys. When using UDDI
@@ -1619,7 +1663,7 @@
acknowledged.
</p></div><div class="div1">
<h2><a name="change-description"></a>D. Changes in this Version of the Document (Non-Normative)</h2><p>A list of substantive changes since the Working Draft dated 02 November, 2006
- is below:</p><ul><li><p>None.</p></li></ul></div><div class="div1">
+ is below:</p><ul><li><p>Added a new domain expression: <a href="#uri-domain-expression"><b>3.4.1 URI Domain Expression</b></a>.</p></li></ul></div><div class="div1">
<h2><a name="change-log"></a>E. Web Services Policy 1.5 - Attachment Change Log (Non-Normative)</h2><a name="ws-policy-attachment-changelog-table"></a><table border="1"><tbody><tr><th rowspan="1" colspan="1">Date</th><th rowspan="1" colspan="1">Author</th><th rowspan="1" colspan="1">Description</th></tr><tr><td rowspan="1" colspan="1">20060712</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Updated the list of editors. Completed action items
<a href="http://www.w3.org/2006/07/12-ws-policy-minutes.html#action20">20</a>
from the Austin F2F.</td></tr><tr><td rowspan="1" colspan="1">20060712</td><td rowspan="1" colspan="1">DBO</td><td rowspan="1" colspan="1">Completed action item <a href=" http://www.w3.org/2006/07/12-ws-policy-minutes.html#action12">12</a>
@@ -1723,4 +1767,8 @@
<a href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Nov/0072.html">resolution</a> for issues
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3721">3721</a> and
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3789">3789</a>.
+ </td></tr><tr><td rowspan="1" colspan="1">20061109</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Implemented the
+ <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/72">resolution</a> for issues
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3599">3599</a> and
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3730">3730</a>.
</td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
Index: ws-policy-attachment.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.xml,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -d -r1.68 -r1.69
--- ws-policy-attachment.xml 10 Nov 2006 02:18:30 -0000 1.68
+++ ws-policy-attachment.xml 10 Nov 2006 04:50:37 -0000 1.69
@@ -179,7 +179,7 @@
<td>
<code>http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization</code>
</td>
-<td>[<loc href="http://131.107.72.15/MTOM_Service_Indigo/">WS-OptimizedSerializationPolicy</loc>]</td>
+<td>[<bibref ref="WS-MTOMPolicy"/>]</td>
</tr>
<tr>
<td>
@@ -686,8 +686,9 @@
</label>
<def>
<p>Additional attributes <rfc2119>MAY</rfc2119> be specified but
-<rfc2119>MUST NOT</rfc2119> contradict the semantics of the owner
-element; if an attribute is not recognized, it
+ <rfc2119>MUST NOT</rfc2119> contradict the semantics of the
+ <emph role="infoset-property">owner element</emph>;
+ if an attribute is not recognized, it
<rfc2119>SHOULD</rfc2119> be ignored.</p>
</def>
</gitem>
@@ -722,6 +723,54 @@
<code>http://www.example.com/policies#RmPolicy</code> applies to all
interactions with the endpoint at
<code>http://www.example.com/acct</code>.</p>
+<div3 id="uri-domain-expression">
+ <head>URI Domain Expression</head>
+ <p>This section defines a domain expression for identifying resources as
+ <termref def="policy_subject">policy subjects</termref> for the external attachment mechanism. The following
+ is a pseudo-schema for the URI domain expression:</p>
+<eg xml:space="preserve" role="needs-numbering"><wsp:PolicyAttachment … >
+ <wsp:AppliesTo>
+ <wsp:URI … >xs:anyURI</wsp:URI> *
+ </wsp:AppliesTo>
+ …
+</wsp:PolicyAttachment></eg>
+<p>The following describes the URI domain expression element listed in the pseudo-schema outlined above:</p>
+<glist>
+ <gitem>
+ <label><att>/wsp:PolicyAttachment/wsp:AppliesTo/wsp:URI</att></label>
+ <def><p>This element is an absolute IRI that references a resource
+ as a <termref def="policy_subject">policy subject</termref>. There is no requirement that the IRI be resolvable;
+ retrieval mechanisms are beyond the scope of this specification.</p></def>
+ </gitem>
+ <gitem>
+ <label><att>/wsp:PolicyReference/wsp:AppliesTo/wsp:URI/@{any}</att></label>
+ <def><p>Additional attributes <rfc2119>MAY</rfc2119> be specified but <rfc2119>MUST NOT</rfc2119> contradict the
+ semantics of the <emph role="infoset-property">owner element</emph>; if an attribute is not recognized,
+ it <rfc2119>SHOULD</rfc2119> be ignored.</p></def>
+ </gitem>
+</glist>
+ <p>URI domain expressions are used to identify resources that are identified using
+ 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.
+ 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
+ example illustrates the use of URI domain expression
+ with a WSDL 2.0 IRI Reference: </p>
+ <eg xml:space="preserve" role="needs-numbering"><wsp:PolicyAttachment>
+ <wsp:AppliesTo>
+ <wsp:URI>http://example.org/TicketAgent.wsdl20#wsdl.endpoint(TicketAgentService/Endpoint)</wsp:URI>
+ </wsp:AppliesTo>
+ <wsp:PolicyReference URI="http://www.example.com/policies#RmPolicy" />
+ </wsp:PolicyAttachment></eg>
+ <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>
+
+</div3>
</div2>
</div1>
<div1 id="AttachingPolicyUsingWSDL1.1">
@@ -2397,6 +2446,13 @@
2005. This version of the SOAP Message Transmission Optimization Mechanism Recommendation
is http://www.w3.org/TR/2005/REC-soap12-mtom-20050125/. The <loc href="http://www.w3.org/TR/soap12-mtom/">latest version of SOAP Message Transmission
Optimization Mechanism</loc> is available at http://www.w3.org/TR/soap12-mtom/. </bibl>
+ <bibl id="WS-MTOMPolicy" key="WS-MTOMPolicy"
+ href="http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization/">
+ <titleref>MTOM Serialization Policy Assertion (WS-MTOMPolicy)</titleref>, C. Ferris, et al,
+ Authors. International Business Machines Corporation and Microsoft
+ Corporation, Inc., September 2006. Available at
+ http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization/
+ </bibl>
<bibl id="SCC14N" key="SCC14N" href="http://uddi.org/pubs/SchemaCentricCanonicalization-20050523.htm">
<titleref>Schema Centric XML Canonicalization Version
1.0</titleref>, S. Aissi, A. Hately, and M. Hondo,
@@ -2458,6 +2514,18 @@
version of the XML-binary Optimized Packaging Recommendation is
http://www.w3.org/TR/2005/REC-xop10-20050125/. The <loc href="http://www.w3.org/TR/xop10/">latest version of XML-binary Optimized Packaging</loc> is available at
http://www.w3.org/TR/xop10/. </bibl>
+ <bibl key="XPointer Framework"
+ href="http://www.w3.org/TR/2003/REC-xptr-framework-20030325/"
+ id="XPointer">
+ <titleref>XPointer Framework</titleref>,Paul Grosso, Eve
+ Maler, Jonathan Marsh, Norman Walsh, Editors. World Wide Web
+ Consortium, 22 November 2002. This version of the XPointer
+ Framework Proposed Recommendation is
+ http://www.w3.org/TR/2003/REC-xptr-framework-20030325/ The
+ <loc href='http://www.w3.org/TR/xptr-framework/'>latest
+ version of XPointer Framework</loc> is available at
+ http://www.w3.org/TR/xptr-framework/.
+ </bibl>
</blist>
</div2>
</div1>
@@ -2678,7 +2746,7 @@
is below:</p>
<ulist>
<item>
- <p>None.</p>
+ <p>Added a new domain expression: <specref ref="uri-domain-expression"/>.</p>
</item>
</ulist>
</inform-div1>
@@ -2971,7 +3039,16 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3721">3721</loc> and
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3789">3789</loc>.
</td>
- </tr>
+ </tr>
+ <tr>
+ <td>20061109</td>
+ <td>ASV</td>
+ <td>Implemented the
+ <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/72">resolution</loc> for issues
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3599">3599</loc> and
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3730">3730</loc>.
+ </td>
+ </tr>
</tbody>
</table>
</inform-div1>
Index: ws-policy.xsd
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy.xsd,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- ws-policy.xsd 10 Nov 2006 02:18:30 -0000 1.3
+++ ws-policy.xsd 10 Nov 2006 04:50:37 -0000 1.4
@@ -130,5 +130,15 @@
</xs:complexType>
</xs:element>
-
+
+ <xs:element name="URI">
+ <xs:complexType>
+ <xs:simpleContent>
+ <xs:extension base="xs:anyURI">
+ <xs:anyAttribute namespace="##any" processContents="lax" />
+ </xs:extension>
+ </xs:simpleContent>
+ </xs:complexType>
+ </xs:element>
+
</xs:schema>
Received on Friday, 10 November 2006 04:50:55 UTC