W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > May 2010

WWW/2002/ws/ra/edcopies wsmex.html,1.129,1.130 wsmex.xml,1.116,1.117

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 12 May 2010 17:33:30 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1OCFoI-0002Rd-Sb@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv9306

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


Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.116
retrieving revision 1.117
diff -u -d -r1.116 -r1.117
--- wsmex.xml	12 May 2010 16:03:43 -0000	1.116
+++ wsmex.xml	12 May 2010 17:33:28 -0000	1.117
@@ -1167,13 +1167,45 @@
 
     <glist>
      <gitem>
+      <label> <kw>[Body]</kw>/mex:GetWSDLResponse/xs:any </label>
+      <def>
+       <p>
+        When the GetWSDLResponse element contains any child elements, the 
+        first element MUST either be the WSDL metadata document, or a 
+        reference to the WSDL metadata document, of the endpoint. Any 
+        extension elements MUST appear after the WSDL document/reference. 
+        The absence of any child elements indicates that the endpoint does 
+        not have any WSDL document, or additional metadata, associated with it. 
+       </p>
+      </def>
+     </gitem>
+
+     <gitem>
       <label> <kw>[Body]</kw>/mex:GetWSDLResponse/wsdl:definitions </label>
       <def>
        <p>
         When present this OPTIONAL element contains the WSDL metadata 
-        document of the endpoint. The absence of this element indicates 
-        that the endpoint does not have any WSDL document, or additional 
-        metadata, associated with it.
+        document of the endpoint.
+       </p>
+      </def>
+     </gitem>
+
+     <gitem>
+      <label> <kw>[Body]</kw>/mex:GetWSDLResponse/mex:Location </label>
+      <def>
+       <p>
+        When present this OPTIONAL element contains a reference to the 
+        WSDL metadata document of the endpoint.
+       </p>
+      </def>
+     </gitem>
+
+     <gitem>
+      <label> <kw>[Body]</kw>/mex:GetWSDLResponse/mex:Reference </label>
+      <def>
+       <p>
+        When present this OPTIONAL element contains a reference to the 
+        WSDL metadata document of the endpoint.
        </p>
       </def>
      </gitem>
@@ -4235,6 +4267,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9671">9671</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2010/05/12 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9709">9709</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.129
retrieving revision 1.130
diff -u -d -r1.129 -r1.130
--- wsmex.html	12 May 2010 16:03:43 -0000	1.129
+++ wsmex.html	12 May 2010 17:33:28 -0000	1.130
@@ -63,7 +63,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="#iddiv2_1_1445">Examples</a><br/>
+&nbsp;&nbsp;&nbsp;7.3 <a href="#iddiv2_1_1469">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/>
@@ -72,14 +72,14 @@
 &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="#iddiv2_1_1991">Metadata and Security Bootstrapping</a><br/>
+&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2_1_2015">Metadata and Security Bootstrapping</a><br/>
 12 <a href="#metadata">WS-MetadataExchange Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2_1_2012">MetadataExchange Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2_1_2036">MetadataExchange Assertion</a><br/>
 13 <a href="#bootstrapping">Boostrapping 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="#iddiv2_1_2268">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;15.2 <a href="#iddiv2_1_2467">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;15.1 <a href="#iddiv2_1_2292">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;15.2 <a href="#iddiv2_1_2491">Informative 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/>
@@ -708,11 +708,22 @@
   &lt;/mex:GetWSDLResponse&gt; </pre></div></div><p>
      The following describes additional, normative constraints on the 
      outline listed above: 
-    </p><dl><dt class="label"><b>[Body]</b>/mex:GetWSDLResponse/wsdl:definitions </dt><dd><p>
+    </p><dl><dt class="label"><b>[Body]</b>/mex:GetWSDLResponse/xs:any </dt><dd><p>
+        When the GetWSDLResponse element contains any child elements, the 
+        first element MUST either be the WSDL metadata document, or a 
+        reference to the WSDL metadata document, of the endpoint. Any 
+        extension elements MUST appear after the WSDL document/reference. 
+        The absence of any child elements indicates that the endpoint does 
+        not have any WSDL document, or additional metadata, associated with it. 
+       </p></dd><dt class="label"><b>[Body]</b>/mex:GetWSDLResponse/wsdl:definitions </dt><dd><p>
         When present this OPTIONAL element contains the WSDL metadata 
-        document of the endpoint. The absence of this element indicates 
-        that the endpoint does not have any WSDL document, or additional 
-        metadata, associated with it.
+        document of the endpoint.
+       </p></dd><dt class="label"><b>[Body]</b>/mex:GetWSDLResponse/mex:Location </dt><dd><p>
+        When present this OPTIONAL element contains a reference to the 
+        WSDL metadata document of the endpoint.
+       </p></dd><dt class="label"><b>[Body]</b>/mex:GetWSDLResponse/mex:Reference </dt><dd><p>
+        When present this OPTIONAL element contains a reference to the 
+        WSDL metadata document of the endpoint.
        </p></dd></dl><p>
      This operation is safe; it will not result in any side effect
      imputable to the requester. This means that in case of an underlying
@@ -1025,7 +1036,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="iddiv2_1_1445" id="iddiv2_1_1445"/>7.3 Examples</h3><p>
+<h3><a name="iddiv2_1_1469" id="iddiv2_1_1469"/>7.3 Examples</h3><p>
      The following examples show how metadata might appear in various 
      locations:
     </p><div class="exampleOuter">
@@ -1056,7 +1067,7 @@
      The following example WSDL shows how support for a particular feature 
      might be indicated:
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_1477" id="idexample_1_1477"/>Example 7-3: Feature Metadata in a Policy Assertion</div><div class="exampleInner"><pre>(01) &lt;wsdl:definitions&gt;
+<div class="exampleHeader"><a name="idexample_1_1501" id="idexample_1_1501"/>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;
@@ -1596,7 +1607,7 @@
     security analysis to determine their particular threat profile and the 
     appropriate responses to those threats.
    </p><div class="div2">
-<h3><a name="iddiv2_1_1991" id="iddiv2_1_1991"/>11.1 Metadata and Security Bootstrapping</h3><p>
+<h3><a name="iddiv2_1_2015" id="iddiv2_1_2015"/>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 
@@ -1634,7 +1645,7 @@
     indicate a particular security mechanism used to protect the
     WS-MetadataExchange operations supported by this endpoint.
    </p><div class="div2">
-<h3><a name="iddiv2_1_2012" id="iddiv2_1_2012"/>12.1 MetadataExchange Assertion</h3><p>
+<h3><a name="iddiv2_1_2036" id="iddiv2_1_2036"/>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 -
@@ -1854,7 +1865,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="iddiv2_1_2268" id="iddiv2_1_2268"/>15.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2_1_2292" id="iddiv2_1_2292"/>15.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
         Key words for use in RFCs to Indicate Requirement Levels
        </cite></a>
        , S. Bradner, Author.
@@ -1931,7 +1942,7 @@
        , P. Biron, A. Malhotra, Editors.
        World Wide Web Consortium (W3C), 28 October 2004.
       Available at <a href="http://www.w3.org/TR/xmlschema-2/">http://www.w3.org/TR/xmlschema-2/</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2467" id="iddiv2_1_2467"/>15.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
+<h3><a name="iddiv2_1_2491" id="iddiv2_1_2491"/>15.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
         OASIS Standard, "Web Services Secure Conversation
           (WS-SecureConversation) 1.4"
        </cite></a>
@@ -2420,4 +2431,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</a></td></tr><tr><td> 2010/05/11 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9570">9570</a></td></tr><tr><td> 2010/05/11 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9699">9699</a></td></tr><tr><td> 2010/05/11 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9671">9671</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=9671">9671</a></td></tr><tr><td> 2010/05/12 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9709">9709</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Wednesday, 12 May 2010 17:33:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 12 May 2010 17:33:33 GMT