- From: Asir Vedamuthu via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 08 Jan 2007 16:53:08 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv7491
Modified Files:
ws-policy-attachment.html ws-policy-attachment.xml
Log Message:
Applied the missed amendment [1] to section 3.5 Use of IRIs in Policy Attachment.
[1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=4039#c1
Index: ws-policy-attachment.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.xml,v
retrieving revision 1.72
retrieving revision 1.73
diff -u -d -r1.72 -r1.73
--- ws-policy-attachment.xml 18 Dec 2006 18:19:50 -0000 1.72
+++ ws-policy-attachment.xml 8 Jan 2007 16:53:05 -0000 1.73
@@ -783,10 +783,11 @@
<div2 id="IRI_Policy_Attachment">
<head>Use of IRIs in Policy Attachment</head>
<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
- [<bibref ref="XMLBASE"/>]
- and RFC 3987 [<bibref ref="RFC3987"/>] for establishing a base URI against which relative IRIs can be made absolute.</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 [<bibref ref="XMLBASE" />] and RFCs 3023 [<bibref ref="RFC3023" />],
+ 3986 [<bibref ref="RFC3986" />] and 3987 [<bibref ref="RFC3987" />]
+ for establishing a base URI against which relative IRIs can be made absolute.</p>
</div2>
</div1>
<div1 id="AttachingPolicyUsingWSDL1.1">
@@ -2313,12 +2314,23 @@
version of the Basic Profile Version 1.1</loc> is available at
http://www.ws-i.org/Profiles/BasicProfile-1.1.html
</bibl>
+ <bibl key="IETF RFC 3023"
+ href="http://www.ietf.org/rfc/rfc3023.txt" id="RFC3023">IETF
+ "RFC 3023: XML Media Types", M. Murata, S. St. Laurent, D. Kohn, July
+ 1998.</bibl>
<bibl key="IETF RFC 2119" href="http://www.ietf.org/rfc/rfc2119.txt" id="RFC2119">
<titleref>Key words for use in RFCs to Indicate Requirement
Levels</titleref>, S. Bradner, Author. Internet Engineering
Task Force, June 1999. Available at
http://www.ietf.org/rfc/rfc2119.txt.
</bibl>
+ <bibl key="IETF RFC 3986" href="http://www.ietf.org/rfc/rfc3986.txt" id="RFC3986">
+ <titleref>Uniform Resource Identifier (URI): Generic Syntax
+ </titleref>, T. Berners-Lee, R. Fielding and L. Masinter,
+ Authors. Network Working Group,
+ January 2005. Available at
+ http://www.ietf.org/rfc/rfc3986.txt.
+ </bibl>
<bibl key="IETF RFC 3987" href="http://www.ietf.org/rfc/rfc3987.txt" id="RFC3987">
<titleref>Internationalized Resource Identifiers (IRIs)
</titleref>, M. Duerst and M. Suignard,
@@ -3099,7 +3111,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4039">4039</loc> to close editors' action
<loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/99">99</loc>.
</td>
- </tr>
+ </tr>
+ <tr>
+ <td>20070108</td>
+ <td>ASV</td>
+ <td>Applied the <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4039#c1">missed amendment</loc> to section <specref ref="IRI_Policy_Attachment"/>.
+ </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.72
retrieving revision 1.73
diff -u -d -r1.72 -r1.73
--- ws-policy-attachment.html 18 Dec 2006 18:22:32 -0000 1.72
+++ ws-policy-attachment.html 8 Jan 2007 16:53:05 -0000 1.73
@@ -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="#d3e3961">External Policy Attachment Conformance</a><br> 8.2 <a href="#d3e3973">WSDL 1.1 Attachment Conformance</a><br> 8.3 <a href="#d3e3982">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="#d3e3965">External Policy Attachment Conformance</a><br> 8.2 <a href="#d3e3977">WSDL 1.1 Attachment Conformance</a><br> 8.3 <a href="#d3e3986">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>]
@@ -509,10 +509,11 @@
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">
<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 RFC 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">
+ 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
@@ -1367,11 +1368,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="d3e3961"></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="d3e3973"></a>8.2 WSDL 1.1 Attachment Conformance</h3><p>
+<h3><a name="d3e3965"></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="d3e3977"></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="d3e3982"></a>8.3 WSDL 2.0 Attachment Conformance</h3><p>
+<h3><a name="d3e3986"></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">
@@ -1384,12 +1385,20 @@
<a href="http://www.ws-i.org/Profiles/BasicProfile-1.1.html">latest
version of the Basic Profile Version 1.1</a> is available at
http://www.ws-i.org/Profiles/BasicProfile-1.1.html
- </dd><dt class="label"><a name="RFC2119"></a>[IETF RFC 2119] </dt><dd>
+ </dd><dt class="label"><a name="RFC3023"></a>[IETF RFC 3023] </dt><dd>IETF
+ "RFC 3023: XML Media Types", M. Murata, S. St. Laurent, D. Kohn, July
+ 1998. (See <cite><a href="http://www.ietf.org/rfc/rfc3023.txt">http://www.ietf.org/rfc/rfc3023.txt</a></cite>.)</dd><dt class="label"><a name="RFC2119"></a>[IETF RFC 2119] </dt><dd>
<cite><a href="http://www.ietf.org/rfc/rfc2119.txt">Key words for use in RFCs to Indicate Requirement
Levels</a></cite>, S. Bradner, Author. Internet Engineering
Task Force, June 1999. Available at
http://www.ietf.org/rfc/rfc2119.txt.
- </dd><dt class="label"><a name="RFC3987"></a>[IETF RFC 3987] </dt><dd>
+ </dd><dt class="label"><a name="RFC3986"></a>[IETF RFC 3986] </dt><dd>
+ <cite><a href="http://www.ietf.org/rfc/rfc3986.txt">Uniform Resource Identifier (URI): Generic Syntax
+ </a></cite>, T. Berners-Lee, R. Fielding and L. Masinter,
+ Authors. Network Working Group,
+ January 2005. Available at
+ http://www.ietf.org/rfc/rfc3986.txt.
+ </dd><dt class="label"><a name="RFC3987"></a>[IETF RFC 3987] </dt><dd>
<cite><a href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers (IRIs)
</a></cite>, M. Duerst and M. Suignard,
Authors. Internet Engineering Task Force,
@@ -1793,4 +1802,5 @@
<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>.
+ </td></tr><tr><td rowspan="1" colspan="1">20070108</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Applied the <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4039#c1">missed amendment</a> to section <a href="#IRI_Policy_Attachment"><b>3.5 Use of IRIs in Policy Attachment</b></a>.
</td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
Received on Monday, 8 January 2007 16:53:19 UTC