WWW/2002/ws/ra/edcopies wsmex.html,1.151,1.152 wsmex.xml,1.141,1.142

Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv2682

Modified Files:
	wsmex.html wsmex.xml 
Log Message:
11865


Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.141
retrieving revision 1.142
diff -u -d -r1.141 -r1.142
--- wsmex.xml	14 Feb 2011 19:40:49 -0000	1.141
+++ wsmex.xml	16 Feb 2011 05:05:01 -0000	1.142
@@ -1401,6 +1401,13 @@
     </glist>
 
     <p>
+     Subject to authorization restrictions, services MUST return all the 
+     MetadataSections corresponding to the GetMetadata request.  Note 
+     that there can be multiple MetadataSections returned for any one 
+     combination of Dialect, Identifier and Content values.
+    </p>
+
+    <p>
      If an endpoint accepts a GetMetadata request, it MUST reply with 
      a GetMetadataResponse message. The normative outline for a 
      GetMetadataResponse is:
@@ -1508,10 +1515,15 @@
 
        <p>
         The mex:Metadata element contains one MetadataSection child for 
-        each distinct unit of metadata to be updated.  The resource 
-        metadata (identified by the dialect and identifier) specified by 
+        each distinct unit of metadata to be updated.  All resource 
+        metadata (identified by the Dialect, Identifier and Content values)
+        specified by 
         each metadata section MUST be replaced in its entirety by the 
-        metadata specified in the PutMetadata request message.
+        metadata specified in the PutMetadata request message;
+        the service MUST treat the incoming MetadataSections as the
+        complete set of metadata for the specified Dialect, Identifier and
+        Content values and any metadata previously associated with that
+        triplet of values MUST be removed.
        </p>
 
        <p>
@@ -1524,12 +1536,7 @@
        </p>
 
        <p>
-        If a MetadataSection child contains a MetadataReference or 
-        MetadataLocation instead of the metadata in-lined, the endpoint 
-        MAY reject the PutMetadata request with an mex:UnsupportedMetadata 
-        fault if it does not support storing of references.  However, 
-        if the endpoint does accept the request then the reference is to
-        be saved and returned in subsequent retrieval requests. The endpoint 
+        When storing references, the endpoint 
         MUST NOT resolve the references in an attempt to persist the
         actual metadata document itself.
        </p>
@@ -1540,8 +1547,9 @@
 
     <p>
      An endpoint MUST reject a PutMetadata request if it is unable to 
-     process all of the metadata updates requested.   If the dialect or 
-     identifier specified in one or more MetadataSections is unsupported 
+     process all of the metadata updates requested.   If the dialect, 
+     identifier or content form specified in one or more MetadataSections 
+     is unsupported 
      by the endpoint, the endpoint MUST generate a mex:UnsupportedMetadata 
      fault.
      If the creation or update of the endpoint's Metadata will render the 
@@ -1709,8 +1717,9 @@
 
     <p>
      An endpoint MUST reject a DeleteMetadata request if it is unable to 
-     process all of the metadata deletes requested.   If the dialect type 
-     or identifier specified in one or more of the Dialect elements is 
+     process all of the metadata deletes requested.   If the dialect, 
+     identifier or content form
+     specified in one or more of the Dialect elements is 
      unsupported by the endpoint, the endpoint MUST generate a 
      mex:UnsupportedMetadata fault.  If the deletion of the specified Metadata 
      will render the endpoint invalid, the endpoint MUST generate an 
@@ -4357,6 +4366,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11899">11899</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2011/02/15 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11865">11865</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.151
retrieving revision 1.152
diff -u -d -r1.151 -r1.152
--- wsmex.html	14 Feb 2011 19:40:49 -0000	1.151
+++ wsmex.html	16 Feb 2011 05:05:01 -0000	1.152
@@ -64,7 +64,7 @@
 7 <a href="#MetadataReferences">Metadata References</a><br/>
 &nbsp;&nbsp;&nbsp;7.1 <a href="#mexLocation">mex:Location</a><br/>
 &nbsp;&nbsp;&nbsp;7.2 <a href="#mexReference">mex:Reference</a><br/>
-&nbsp;&nbsp;&nbsp;7.3 <a href="#iddiv2x1x1500">Examples</a><br/>
+&nbsp;&nbsp;&nbsp;7.3 <a href="#iddiv2x1x1502">Examples</a><br/>
 8 <a href="#Metadata-in-Endpoint-References">Metadata in Endpoint References</a><br/>
 &nbsp;&nbsp;&nbsp;8.1 <a href="#EPRwithMEX">Endpoint References Containing Metadata</a><br/>
 &nbsp;&nbsp;&nbsp;8.2 <a href="#WSPAEPR">Associating Policies with Endpoint References</a><br/>
@@ -73,13 +73,13 @@
 &nbsp;&nbsp;&nbsp;10.1 <a href="#UnsupportedMetadata">UnsupportedMetadata</a><br/>
 &nbsp;&nbsp;&nbsp;10.2 <a href="#InvalidMetadata">UnknownDialect</a><br/>
 11 <a href="#Security">Security Considerations</a><br/>
-&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2x1x2018">Metadata and Security Bootstrapping</a><br/>
+&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2x1x2020">Metadata and Security Bootstrapping</a><br/>
 12 <a href="#metadata">WS-MetadataExchange Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2x1x2039">MetadataExchange Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2x1x2041">MetadataExchange Assertion</a><br/>
 13 <a href="#bootstrapping">Bootstrapping Metadata Retrieval</a><br/>
 14 <a href="#acks">Acknowledgements</a><br/>
 15 <a href="#References">References</a><br/>
-&nbsp;&nbsp;&nbsp;15.1 <a href="#iddiv2x1x2295">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;15.1 <a href="#iddiv2x1x2297">Normative References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix-A">XML Schema</a><br/>
 B <a href="#Appendix-B">WSDL</a><br/>
@@ -818,6 +818,11 @@
         then the response MUST include zero
         MetadataSections of the specified form for this QName/Identifier pair.
        </p></dd></dl><p>
+     Subject to authorization restrictions, services MUST return all the 
+     MetadataSections corresponding to the GetMetadata request.  Note 
+     that there can be multiple MetadataSections returned for any one 
+     combination of Dialect, Identifier and Content values.
+    </p><p>
      If an endpoint accepts a GetMetadata request, it MUST reply with 
      a GetMetadataResponse message. The normative outline for a 
      GetMetadataResponse is:
@@ -877,10 +882,15 @@
         <a href="#web-services-metadata"><b>4 Web Services Metadata Collection</b></a>.
        </p><p>
         The mex:Metadata element contains one MetadataSection child for 
-        each distinct unit of metadata to be updated.  The resource 
-        metadata (identified by the dialect and identifier) specified by 
+        each distinct unit of metadata to be updated.  All resource 
+        metadata (identified by the Dialect, Identifier and Content values)
+        specified by 
         each metadata section MUST be replaced in its entirety by the 
-        metadata specified in the PutMetadata request message.
+        metadata specified in the PutMetadata request message;
+        the service MUST treat the incoming MetadataSections as the
+        complete set of metadata for the specified Dialect, Identifier and
+        Content values and any metadata previously associated with that
+        triplet of values MUST be removed.
        </p><p>
         If there is no Metadata associated with the resource that 
         corresponds to a MetadataSection child contained within the 
@@ -889,18 +899,14 @@
         endpoint and if the creation of the Metadata will not invalidate 
         the endpoint.
        </p><p>
-        If a MetadataSection child contains a MetadataReference or 
-        MetadataLocation instead of the metadata in-lined, the endpoint 
-        MAY reject the PutMetadata request with an mex:UnsupportedMetadata 
-        fault if it does not support storing of references.  However, 
-        if the endpoint does accept the request then the reference is to
-        be saved and returned in subsequent retrieval requests. The endpoint 
+        When storing references, the endpoint 
         MUST NOT resolve the references in an attempt to persist the
         actual metadata document itself.
        </p></dd></dl><p>
      An endpoint MUST reject a PutMetadata request if it is unable to 
-     process all of the metadata updates requested.   If the dialect or 
-     identifier specified in one or more MetadataSections is unsupported 
+     process all of the metadata updates requested.   If the dialect, 
+     identifier or content form specified in one or more MetadataSections 
+     is unsupported 
      by the endpoint, the endpoint MUST generate a mex:UnsupportedMetadata 
      fault.
      If the creation or update of the endpoint's Metadata will render the 
@@ -987,8 +993,9 @@
         specific content form is to be deleted.
        </p></dd></dl><p>
      An endpoint MUST reject a DeleteMetadata request if it is unable to 
-     process all of the metadata deletes requested.   If the dialect type 
-     or identifier specified in one or more of the Dialect elements is 
+     process all of the metadata deletes requested.   If the dialect, 
+     identifier or content form
+     specified in one or more of the Dialect elements is 
      unsupported by the endpoint, the endpoint MUST generate a 
      mex:UnsupportedMetadata fault.  If the deletion of the specified Metadata 
      will render the endpoint invalid, the endpoint MUST generate an 
@@ -1075,7 +1082,7 @@
         being referenced. Identifier is an absolute IRI. If omitted, there 
         is no implied value.
        </p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2x1x1500" id="iddiv2x1x1500"/>7.3 Examples</h3><p>
+<h3><a name="iddiv2x1x1502" id="iddiv2x1x1502"/>7.3 Examples</h3><p>
      The following examples show how metadata might appear in various 
      locations:
     </p><div class="exampleOuter">
@@ -1106,7 +1113,7 @@
      The following example WSDL shows how support for a particular feature 
      might be indicated:
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexamplex1x1532" id="idexamplex1x1532"/>Example 7-3: Feature Metadata in a Policy Assertion</div><div class="exampleInner"><pre>(01) &lt;wsdl:definitions&gt;
+<div class="exampleHeader"><a name="idexamplex1x1534" id="idexamplex1x1534"/>Example 7-3: Feature Metadata in a Policy Assertion</div><div class="exampleInner"><pre>(01) &lt;wsdl:definitions&gt;
 (02)   ...
 (03)   &lt;wsdl:service name="stockQuote"&gt;
 (04)     &lt;wsdl:port binding="..." name="..."&gt;
@@ -1518,7 +1525,7 @@
     WS-Eventing WSDL.  As discussed above, this WSDL might be annotated to 
     specify additional constrains on the WS-Eventing message exchanges.
    </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexamplex1x1793" id="idexamplex1x1793"/>Example 9-2:  Sample WS-Eventing Policy with Embedded WSDL </div><div class="exampleInner"><pre>(01) &lt;wsp:Policy&gt;
+<div class="exampleHeader"><a name="idexamplex1x1795" id="idexamplex1x1795"/>Example 9-2:  Sample WS-Eventing Policy with Embedded WSDL </div><div class="exampleInner"><pre>(01) &lt;wsp:Policy&gt;
 (02)  &lt;wse:EventSource&gt;
 (03)   &lt;wse:FormatName
 (04)     URI="http://www.w3.org/2002/ws/ra/edcopies/ws-evt/DeliveryFormats/Unwrap"&gt;
@@ -1548,7 +1555,7 @@
     specific endpoint to which those protocol messages are to be sent - if 
     it is different from the address specified on line 02.
    </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexamplex1x1803" id="idexamplex1x1803"/>Example 9-3:  Sample EndpointReference with Embedded Policy </div><div class="exampleInner"><pre>(01) &lt;wse:NotifyTo&gt;
+<div class="exampleHeader"><a name="idexamplex1x1805" id="idexamplex1x1805"/>Example 9-3:  Sample EndpointReference with Embedded Policy </div><div class="exampleInner"><pre>(01) &lt;wse:NotifyTo&gt;
 (02)   &lt;wsa:Address&gt; http://example.com &lt;/wsa:Address&gt;
 (03)   &lt;wsa:Metadata&gt;
 (04)     &lt;wsp:Policy&gt;
@@ -1645,7 +1652,7 @@
     security analysis to determine their particular threat profile and the 
     appropriate responses to those threats.
    </p><div class="div2">
-<h3><a name="iddiv2x1x2018" id="iddiv2x1x2018"/>11.1 Metadata and Security Bootstrapping</h3><p>
+<h3><a name="iddiv2x1x2020" id="iddiv2x1x2020"/>11.1 Metadata and Security Bootstrapping</h3><p>
      There are cases in which the metadata used to describe a service might 
      be considered sensitive information. In these cases it is advisable 
      for services to authenticate and authorize consumers as part of the 
@@ -1683,7 +1690,7 @@
     indicate a particular security mechanism used to protect the
     WS-MetadataExchange operations supported by this endpoint.
    </p><div class="div2">
-<h3><a name="iddiv2x1x2039" id="iddiv2x1x2039"/>12.1 MetadataExchange Assertion</h3><p>
+<h3><a name="iddiv2x1x2041" id="iddiv2x1x2041"/>12.1 MetadataExchange Assertion</h3><p>
      Services indicate support for the WS-MetadataExchange specification 
      through the use of the Web Services
      Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1906,7 +1913,7 @@
      Yves Lafon (W3C/ERCIM).
    </p></div><div class="div1">
 <h2><a name="References" id="References"/>15 References</h2><div class="div2">
-<h3><a name="iddiv2x1x2295" id="iddiv2x1x2295"/>15.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
+<h3><a name="iddiv2x1x2297" id="iddiv2x1x2297"/>15.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
          WS-I Profile, Basic Profile Version 1.2
         </cite></a>
         , R. Chumbley, et al, Editors.
@@ -2462,4 +2469,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11867">11867</a></td></tr><tr><td> 2011/02/01 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11850">11850</a></td></tr><tr><td> 2011/02/01 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11882">11882</a></td></tr><tr><td> 2011/02/07 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11899">11899</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11899">11899</a></td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11865">11865</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Received on Wednesday, 16 February 2011 05:05:05 UTC