2006/ws/policy ws-policy-attachment.html,1.76,1.77 ws-policy-attachment.xml,1.77,1.78

Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv26868

Modified Files:
	ws-policy-attachment.html ws-policy-attachment.xml 
Log Message:
Implemented the resolution for issue 4230. Editors' action 135. 

Index: ws-policy-attachment.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.xml,v
retrieving revision 1.77
retrieving revision 1.78
diff -u -d -r1.77 -r1.78
--- ws-policy-attachment.xml	22 Jan 2007 14:24:21 -0000	1.77
+++ ws-policy-attachment.xml	22 Jan 2007 21:39:21 -0000	1.78
@@ -504,6 +504,9 @@
 	as part of their intrinsic definition. The second allows
 	policies to be associated with arbitrary policy subjects
 	independently from their definition.</p>
+  <p>The <termref def="policy_scope">policy scope</termref> of an attachment is specific to the <termref def="policy_attachment">policy attachment</termref>
+    Mechanism using it. Accordingly, any <termref def="policy_attachment">policy attachment</termref> mechanism <rfc2119>MUST</rfc2119> define
+    the <termref def="policy_scope">policy scope</termref> of the attachment.</p>	
 </div2>
 <div2 id="XMLElementAttachement">
 <head>XML Element Attachment</head>
@@ -538,10 +541,6 @@
 	<term>element policy</term> is the <termref def="policy">policy</termref> attached to the <termref def="policy_subject">policy subjects</termref> associated with
 	the element information item that contains it.</termdef>
 </p>
-<p>Note that the <termref def="policy_scope">policy scope</termref> of the attachment is specific to the
-<termref def="policy_attachment">policy attachment</termref> Mechanism using it; accordingly, any <termref def="policy_attachment">policy
-attachment</termref> mechanism using this attribute <rfc2119>MUST</rfc2119>
-define the <termref def="policy_scope">policy scope</termref> of the attachment.</p>
 <p>An example of <termref def="element_policy">element policy</termref> through the use of this global
 attribute is given below using the sample policies stated in Section
 <specref ref="Example"/>.</p>
@@ -3201,6 +3200,13 @@
 	<td>Completed action item:
          <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/129">129</loc>
          Resolution for issue  <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4207">4207</loc></td>
+  </tr> 
+  <tr>
+    <td>20070122</td>
+    <td>ASV</td>
+    <td>Implemented the resolution for issue <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4230">4230</loc>.
+    Editors' action <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/135">135</loc>.
+    </td>
   </tr>                                     
 </tbody>
 </table>

Index: ws-policy-attachment.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.html,v
retrieving revision 1.76
retrieving revision 1.77
diff -u -d -r1.76 -r1.77
--- ws-policy-attachment.html	18 Jan 2007 00:25:35 -0000	1.76
+++ ws-policy-attachment.html	22 Jan 2007 21:39:21 -0000	1.77
@@ -94,7 +94,7 @@
 	      Element or Attribute Information Items.</p></li></ul><p>Elements and Attributes defined by this specification are referred to in the text of this document using 
 XPath 1.0 [XPATH 1.0] expressions. Extensibility points are referred to using an extended version of this 
 syntax:</p><ul><li><p>An element extensibility point is referred to using {any} in place of the element name. This 
-indicates that any element name can be used, from any namespace other than the http://www.w3.org/@@@@/@@/ws-policy 
+indicates that any element name can be used, from any namespace other than the http://www.w3.org/ns/ws-policy 
 namespace. </p></li><li><p>An attribute extensibility point is referred to using @{any} in place of the attribute name. This 
 indicates that any attribute name can be used, from any namespace. 
 namespace. </p></li></ul><p>Normative text within this specification takes precedence over
@@ -137,7 +137,7 @@
 </td><td rowspan="1" colspan="1">[<cite><a href="#WSDL11BindingforSOAP12">WSDL 1.1 Binding for SOAP 1.2</a></cite>]</td></tr><tr><td rowspan="1" colspan="1">
 <code>(none), wsp</code>
 </td><td rowspan="1" colspan="1">
-<code>http://www.w3.org/@@@@/@@/ws-policy</code>
+<code>http://www.w3.org/ns/ws-policy</code>
 </td><td rowspan="1" colspan="1">This specification</td></tr><tr><td rowspan="1" colspan="1">
 <code>wsse</code>
 </td><td rowspan="1" colspan="1">
@@ -152,9 +152,9 @@
 <code>http://www.w3.org/2001/XMLSchema</code>
 </td><td rowspan="1" colspan="1">[<cite><a href="#XMLSchemaPart1">XML Schema Structures</a></cite>]</td></tr></tbody></table><br><p>
 	  All information items defined by this specification
-	  are identified by the XML namespace URI [<cite><a href="#XML-NS">XML Namespaces</a></cite>] http://www.w3.org/@@@@/@@/ws-policy. A <a href="http://www.w3.org/@@@@/@@/ws-policy">normative XML
+	  are identified by the XML namespace URI [<cite><a href="#XML-NS">XML Namespaces</a></cite>] http://www.w3.org/ns/ws-policy. A <a href="http://www.w3.org/ns/ws-policy">normative XML
 	  Schema</a> [<cite><a href="#XMLSchemaPart1">XML Schema Structures</a></cite>, <cite><a href="#XMLSchemaPart2">XML Schema Datatypes</a></cite>] document can be obtained by
-	dereferencing the XML namespace URI.</p><p>
+	dereferencing the namespace document at the WS-Policy 1.5 namespace URI.</p><p>
 	  In this document reference is made to the <code class="attr">wsu:Id</code> 
 	  attribute in a utility schema (<a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd</a>). The
 	  <code class="attr">wsu:Id</code>  attribute was added to the utility schema
@@ -187,7 +187,7 @@
 	      interpreted as described in RFC 2119 [<cite><a href="#RFC2119">IETF RFC 2119</a></cite>].
 	    </p><p>We introduce the following terms that are used throughout this document:</p><dl><dt class="label">
          <a href="#effective_policy">effective policy</a>
-      </dt><dd><p>The
+      </dt><dd><p>the
 <b>effective policy</b>, for a given <a title="" href="#policy_subject">policy subject</a>, is the 
 combination of relevant policies. The relevant policies are those
 attached to <a title="" href="#policy_scope">policy scopes</a> that
@@ -202,7 +202,7 @@
 	    an assertion that may be ignored for policy intersection (as defined in 
 	        <a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-framework.html?content-type=text/html;charset=utf-8#Policy_Intersection">4.5 Policy Intersection</a>).</p></dd><dt class="label">
          <a href="#merge">merge</a>
-      </dt><dd><p>A <b>merge</b>
+      </dt><dd><p>a <b>merge</b>
 	consists of serializing each policy as a
 	<a title="" href="#policy_expression">policy expression</a>, replacing their
 	<code class="elt">wsp:Policy</code>  element with a
@@ -241,7 +241,7 @@
 	is a policy for securing messages using X509 certificates
 	[<cite><a href="#WS-SecurityPolicy">WS-SecurityPolicy</a></cite>].</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><a name="Table2"></a><i><span>Example 2-1. </span>Example RM Policy Expression.</i></p><div class="exampleInner"><pre>(01) &lt;wsp:Policy
 &nbsp; &nbsp; &nbsp; &nbsp; xmlns:rmp="http://docs.oasis-open.org/ws-rx/wsrmp/200602"
-&nbsp; &nbsp; &nbsp; &nbsp; xmlns:wsp="http://www.w3.org/@@@@/@@/ws-policy"
+&nbsp; &nbsp; &nbsp; &nbsp; xmlns:wsp="http://www.w3.org/ns/ws-policy"
 &nbsp; &nbsp; &nbsp; &nbsp; xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
 &nbsp; &nbsp; &nbsp; &nbsp; wsu:Id="RmPolicy" &gt;
 (02)&nbsp; &nbsp;&lt;rmp:RMAssertion&gt;
@@ -252,7 +252,7 @@
 (07)&nbsp; &nbsp;&lt;/rmp:RMAssertion&gt;
 (08) &lt;/wsp:Policy&gt;</pre></div></div><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><a name="Table3"></a><i><span>Example 2-2. </span>Example X509 Security Policy Expression.</i></p><div class="exampleInner"><pre>(01) &lt;wsp:Policy
 &nbsp; &nbsp; &nbsp; &nbsp; xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
-&nbsp; &nbsp; &nbsp; &nbsp; xmlns:wsp="http://www.w3.org/@@@@/@@/ws-policy"
+&nbsp; &nbsp; &nbsp; &nbsp; xmlns:wsp="http://www.w3.org/ns/ws-policy"
 &nbsp; &nbsp; &nbsp; &nbsp; xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
 &nbsp; &nbsp; &nbsp; &nbsp; wsu:Id="X509EndpointPolicy" &gt;
 (02)&nbsp; &nbsp;&lt;sp:AsymmetricBinding&gt;
@@ -335,7 +335,9 @@
 	resources to associate <a title="" href="#policy">policy</a>
 	as part of their intrinsic definition. The second allows
 	policies to be associated with arbitrary policy subjects
-	independently from their definition.</p></div><div class="div2">
+	independently from their definition.</p><p>The <a title="" href="#policy_scope">policy scope</a> of an attachment is specific to the <a title="" href="#policy_attachment">policy attachment</a>
+    Mechanism using it. Accordingly, any <a title="" href="#policy_attachment">policy attachment</a> mechanism <span class="rfc2119">MUST</span> define
+    the <a title="" href="#policy_scope">policy scope</a> of the attachment.</p></div><div class="div2">
 <h3><a name="XMLElementAttachement"></a>3.3 XML Element Attachment</h3><p>It is often desirable to associate <a title="" href="#policy">policies</a> with Web services <a title="" href="#policy_subject">policy subjects</a> represented as XML elements (i.e., WSDL 1.1 elements - Section <a href="#AttachingPolicyUsingWSDL1.1"><b>4. Attaching Policies Using WSDL 1.1</b></a> for the specific details
 	of WSDL attachment).</p><p>Since <a title="" href="#policy_assertion">policy assertions</a> are strongly typed by the authors, the precise
 	semantics of how element policy is to be processed once
@@ -350,7 +352,7 @@
 (04) 	&lt;xs:list itemType="xs:anyURI" /&gt;
 (05)     &lt;/xs:simpleType&gt;
 (06)   &lt;/xs:attribute&gt;
-(07) &lt;/xs:schema&gt;</pre></div><p>The namespace URI [<cite><a href="#XML-NS">XML Namespaces</a></cite>] for this attribute is <code>http://www.w3.org/@@@@/@@/ws-policy</code>.</p><p>The <code class="attr">wsp:PolicyURIs</code>  attribute contains a white
+(07) &lt;/xs:schema&gt;</pre></div><p>The namespace URI [<cite><a href="#XML-NS">XML Namespaces</a></cite>] for this attribute is <code>http://www.w3.org/ns/ws-policy</code>.</p><p>The <code class="attr">wsp:PolicyURIs</code>  attribute contains a white
 space-separated list of one or more IRIs  [<cite><a href="#RFC3987">IETF RFC 3987</a></cite>]. When this attribute is used,
 each of the values identifies a <a title="" href="#policy_expression">policy expression</a> as defined by
 [<cite><a href="#WS-Policy">Web Services Policy Framework</a></cite>]. If more than one IRI is specified, the
@@ -361,10 +363,7 @@
 property. [<a name="element_policy" title="element policy">Definition</a>: The
 	<b>element policy</b> is the <a title="" href="#policy">policy</a> attached to the <a title="" href="#policy_subject">policy subjects</a> associated with
 	the element information item that contains it.]
-</p><p>Note that the <a title="" href="#policy_scope">policy scope</a> of the attachment is specific to the
-<a title="" href="#policy_attachment">policy attachment</a> Mechanism using it; accordingly, any <a title="" href="#policy_attachment">policy
-attachment</a> mechanism using this attribute <span class="rfc2119">MUST</span>
-define the <a title="" href="#policy_scope">policy scope</a> of the attachment.</p><p>An example of <a title="element policy" href="#element_policy">element policy</a> through the use of this global
+</p><p>An example of <a title="element policy" href="#element_policy">element policy</a> through the use of this global
 attribute is given below using the sample policies stated in Section
 <a href="#Example"><b>2.4 Example</b></a>.</p><p>If the <a title="" href="#policy">policies</a> referenced by the following XML element</p><div class="exampleInner"><pre>(01) &lt;MyElement wsp:PolicyURIs="
 (02) &nbsp; &nbsp;http://www.example.com/policies#RmPolicy
@@ -373,7 +372,7 @@
 	whose XML 1.0 representation is listed in <a href="#Table4">Example 3-1</a>:</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><a name="Table4"></a><i><span>Example 3-1. </span>Example Merged Policy Expression.</i></p><div class="exampleInner"><pre>(01) &lt;wsp:Policy
 &nbsp; &nbsp; &nbsp; &nbsp; xmlns:rmp="http://docs.oasis-open.org/ws-rx/wsrmp/200602"
 &nbsp; &nbsp; &nbsp; &nbsp; xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
-&nbsp; &nbsp; &nbsp; &nbsp; xmlns:wsp="http://www.w3.org/@@@@/@@/ws-policy" &gt;
+&nbsp; &nbsp; &nbsp; &nbsp; xmlns:wsp="http://www.w3.org/ns/ws-policy" &gt;
 (02)&nbsp; &nbsp;&lt;rmp:RMAssertion&gt;
 (03)&nbsp; &nbsp; &nbsp;&lt;rmp:InactivityTimeout Milliseconds="600000" /&gt;
 (04)&nbsp; &nbsp; &nbsp; &nbsp;&lt;rmp:BaseRetransmissionInterval Milliseconds="3000" /&gt;
@@ -719,7 +718,7 @@
 &nbsp; &nbsp; &nbsp; &nbsp; xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
 &nbsp; &nbsp; &nbsp; &nbsp; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
 &nbsp; &nbsp; &nbsp; &nbsp; xmlns:wsoap12="http://schemas.xmlsoap.org/wsdl/soap12/"
-&nbsp; &nbsp; &nbsp; &nbsp; xmlns:wsp="http://www.w3.org/@@@@/@@/ws-policy"
+&nbsp; &nbsp; &nbsp; &nbsp; xmlns:wsp="http://www.w3.org/ns/ws-policy"
 &nbsp; &nbsp; &nbsp; &nbsp; xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" &gt;
 (02)&nbsp; &nbsp;&lt;wsp:Policy wsu:Id="RmPolicy" &gt;
 (03)&nbsp; &nbsp; &nbsp;&lt;rmp:RMAssertion&gt;
@@ -773,7 +772,7 @@
 message-level <a title="effective policy" href="#effective_policy">effective policy</a> is in effect for the input message,
 whose XML 1.0 representation is listed in <a href="#Table6">Example 4-2</a>.</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><a name="Table6"></a><i><span>Example 4-2. </span>Example Message Security Policy Expression.</i></p><div class="exampleInner"><pre>(01) &lt;wsp:Policy
 &nbsp; &nbsp; &nbsp; &nbsp; xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
-&nbsp; &nbsp; &nbsp; &nbsp; xmlns:wsp="http://www.w3.org/@@@@/@@/ws-policy"
+&nbsp; &nbsp; &nbsp; &nbsp; xmlns:wsp="http://www.w3.org/ns/ws-policy"
 &nbsp; &nbsp; &nbsp; &nbsp; xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
 &nbsp; &nbsp; &nbsp; &nbsp; wsu:Id="SecureMessagePolicy" &gt;
 (02)&nbsp; &nbsp;&lt;sp:SignedParts&gt;
@@ -1397,7 +1396,7 @@
     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="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="d3e3989"></a>8.1 External Policy Attachment Conformance</h3><p>An element information item whose namespace name is "http://www.w3.org/ns/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/ns/ws-policy.xsd">http://www.w3.org/ns/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">
@@ -1849,4 +1848,8 @@
         <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><tr><td rowspan="1" colspan="1">20070121</td><td rowspan="1" colspan="1">MH</td><td rowspan="1" colspan="1">Completed action item:
+         <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/129">129</a>
+         Resolution for issue  <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4207">4207</a></td></tr><tr><td rowspan="1" colspan="1">20070122</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Implemented the resolution for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4230">4230</a>.
+    Editors' action <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/135">135</a>.
     </td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file

Received on Monday, 22 January 2007 21:39:29 UTC