- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 01 Feb 2011 23:57:45 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv1068
Modified Files:
wsmex.html wsmex.xml
Log Message:
11850
Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.137
retrieving revision 1.138
diff -u -d -r1.137 -r1.138
--- wsmex.xml 26 Jan 2011 19:53:07 -0000 1.137
+++ wsmex.xml 1 Feb 2011 23:57:43 -0000 1.138
@@ -1430,6 +1430,13 @@
The body of the response message MUST contain one mex:Metadata
element as defined in <specref ref="web-services-metadata"/>.
</p>
+
+ <p>
+ Note, in cases where the requester, through the use of @Content
+ and/or mex:Dialect sub-elements in the GetMetadata request, has
+ excluded all the metadata maintained by the service, this
+ element will be empty.
+ </p>
</def>
</gitem>
</glist>
@@ -4352,6 +4359,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11867">11867</loc>
</td>
</tr>
+ <tr>
+ <td> 2011/02/01 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11850">11850</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.147
retrieving revision 1.148
diff -u -d -r1.147 -r1.148
--- wsmex.html 26 Jan 2011 19:53:07 -0000 1.147
+++ wsmex.html 1 Feb 2011 23:57:42 -0000 1.148
@@ -64,7 +64,7 @@
7 <a href="#MetadataReferences">Metadata References</a><br/>
7.1 <a href="#mexLocation">mex:Location</a><br/>
7.2 <a href="#mexReference">mex:Reference</a><br/>
- 7.3 <a href="#iddiv2x1x1498">Examples</a><br/>
+ 7.3 <a href="#iddiv2x1x1500">Examples</a><br/>
8 <a href="#Metadata-in-Endpoint-References">Metadata in Endpoint References</a><br/>
8.1 <a href="#EPRwithMEX">Endpoint References Containing Metadata</a><br/>
8.2 <a href="#WSPAEPR">Associating Policies with Endpoint References</a><br/>
@@ -73,13 +73,13 @@
10.1 <a href="#UnsupportedMetadata">UnsupportedMetadata</a><br/>
10.2 <a href="#InvalidMetadata">UnknownDialect</a><br/>
11 <a href="#Security">Security Considerations</a><br/>
- 11.1 <a href="#iddiv2x1x2048">Metadata and Security Bootstrapping</a><br/>
+ 11.1 <a href="#iddiv2x1x2050">Metadata and Security Bootstrapping</a><br/>
12 <a href="#metadata">WS-MetadataExchange Metadata</a><br/>
- 12.1 <a href="#iddiv2x1x2069">MetadataExchange Assertion</a><br/>
+ 12.1 <a href="#iddiv2x1x2071">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/>
- 15.1 <a href="#iddiv2x1x2325">Normative References</a><br/>
+ 15.1 <a href="#iddiv2x1x2327">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/>
@@ -834,6 +834,11 @@
</p><dl><dt class="label"><b>[Body]</b>/mex:GetMetadataResponse/mex:Metadata </dt><dd><p>
The body of the response message MUST contain one mex:Metadata
element as defined in <a href="#web-services-metadata"><b>4 Web Services Metadata Collection</b></a>.
+ </p><p>
+ Note, in cases where the requester, through the use of @Content
+ and/or mex:Dialect sub-elements in the GetMetadata request, has
+ excluded all the metadata maintained by the service, this
+ element will be empty.
</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
@@ -1070,7 +1075,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="iddiv2x1x1498" id="iddiv2x1x1498"/>7.3 Examples</h3><p>
+<h3><a name="iddiv2x1x1500" id="iddiv2x1x1500"/>7.3 Examples</h3><p>
The following examples show how metadata might appear in various
locations:
</p><div class="exampleOuter">
@@ -1101,7 +1106,7 @@
The following example WSDL shows how support for a particular feature
might be indicated:
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexamplex1x1530" id="idexamplex1x1530"/>Example 7-3: Feature Metadata in a Policy Assertion</div><div class="exampleInner"><pre>(01) <wsdl:definitions>
+<div class="exampleHeader"><a name="idexamplex1x1532" id="idexamplex1x1532"/>Example 7-3: Feature Metadata in a Policy Assertion</div><div class="exampleInner"><pre>(01) <wsdl:definitions>
(02) ...
(03) <wsdl:service name="stockQuote">
(04) <wsdl:port binding="..." name="...">
@@ -1513,7 +1518,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="idexamplex1x1791" id="idexamplex1x1791"/>Example 9-2: Sample WS-Eventing Policy with Embedded WSDL </div><div class="exampleInner"><pre>(01) <wsp:Policy>
+<div class="exampleHeader"><a name="idexamplex1x1793" id="idexamplex1x1793"/>Example 9-2: Sample WS-Eventing Policy with Embedded WSDL </div><div class="exampleInner"><pre>(01) <wsp:Policy>
(02) <wse:EventSource>
(03) <wse:FormatName
(04) URI="http://www.w3.org/2002/ws/ra/edcopies/ws-evt/DeliveryFormats/Unwrap">
@@ -1543,7 +1548,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="idexamplex1x1801" id="idexamplex1x1801"/>Example 9-3: Sample EndpointReference with Embedded Policy </div><div class="exampleInner"><pre>(01) <wse:NotifyTo>
+<div class="exampleHeader"><a name="idexamplex1x1803" id="idexamplex1x1803"/>Example 9-3: Sample EndpointReference with Embedded Policy </div><div class="exampleInner"><pre>(01) <wse:NotifyTo>
(02) <wsa:Address> http://example.com </wsa:Address>
(03) <wsa:Metadata>
(04) <wsp:Policy>
@@ -1644,7 +1649,7 @@
security analysis to determine their particular threat profile and the
appropriate responses to those threats.
</p><div class="div2">
-<h3><a name="iddiv2x1x2048" id="iddiv2x1x2048"/>11.1 Metadata and Security Bootstrapping</h3><p>
+<h3><a name="iddiv2x1x2050" id="iddiv2x1x2050"/>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
@@ -1682,7 +1687,7 @@
indicate a particular security mechanism used to protect the
WS-MetadataExchange operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2x1x2069" id="iddiv2x1x2069"/>12.1 MetadataExchange Assertion</h3><p>
+<h3><a name="iddiv2x1x2071" id="iddiv2x1x2071"/>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 -
@@ -1905,7 +1910,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="iddiv2x1x2325" id="iddiv2x1x2325"/>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="iddiv2x1x2327" id="iddiv2x1x2327"/>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.
@@ -2458,4 +2463,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11189">11189</a></td></tr><tr><td> 2011/01/26 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11625">11625</a></td></tr><tr><td> 2011/01/26 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11849">11849</a></td></tr><tr><td> 2011/01/26 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11867">11867</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=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></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Tuesday, 1 February 2011 23:57:49 UTC