- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 29 Sep 2010 03:19:29 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv3619
Modified Files:
wsmex.html wsmex.xml
Log Message:
10768
Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.126
retrieving revision 1.127
diff -u -d -r1.126 -r1.127
--- wsmex.xml 17 Aug 2010 19:59:02 -0000 1.126
+++ wsmex.xml 29 Sep 2010 03:19:27 -0000 1.127
@@ -1172,8 +1172,15 @@
<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.
+ reference to the WSDL metadata document, of the endpoint.
+ While an endpoint MAY choose to return a reference to the WSDL, it is
+ STRONGLY RECOMMENDED that the WSDL metadata document itself be
+ returned.
+ If a requester would like a reference to the WSDL then it can use the
+ GetMetadata operation specifying the appropriate Content URI.
+ </p>
+ <p>
+ 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>
@@ -4226,6 +4233,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=10339">10339</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/09/28 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=10768">10768</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.136
retrieving revision 1.137
diff -u -d -r1.136 -r1.137
--- wsmex.html 17 Aug 2010 19:59:02 -0000 1.136
+++ wsmex.html 29 Sep 2010 03:19:27 -0000 1.137
@@ -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="#iddiv2x1x1469">Examples</a><br/>
+ 7.3 <a href="#iddiv2x1x1471">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="#iddiv2x1x2019">Metadata and Security Bootstrapping</a><br/>
+ 11.1 <a href="#iddiv2x1x2021">Metadata and Security Bootstrapping</a><br/>
12 <a href="#metadata">WS-MetadataExchange Metadata</a><br/>
- 12.1 <a href="#iddiv2x1x2040">MetadataExchange Assertion</a><br/>
+ 12.1 <a href="#iddiv2x1x2042">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/>
- 15.1 <a href="#iddiv2x1x2296">Normative References</a><br/>
+ 15.1 <a href="#iddiv2x1x2298">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/>
@@ -711,8 +711,14 @@
</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.
+ reference to the WSDL metadata document, of the endpoint.
+ While an endpoint MAY choose to return a reference to the WSDL, it is
+ STRONGLY RECOMMENDED that the WSDL metadata document itself be
+ returned.
+ If a requester would like a reference to the WSDL then it can use the
+ GetMetadata operation specifying the appropriate Content URI.
+ </p><p>
+ 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>
@@ -1036,7 +1042,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="iddiv2x1x1469" id="iddiv2x1x1469"/>7.3 Examples</h3><p>
+<h3><a name="iddiv2x1x1471" id="iddiv2x1x1471"/>7.3 Examples</h3><p>
The following examples show how metadata might appear in various
locations:
</p><div class="exampleOuter">
@@ -1067,7 +1073,7 @@
The following example WSDL shows how support for a particular feature
might be indicated:
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexamplex1x1501" id="idexamplex1x1501"/>Example 7-3: Feature Metadata in a Policy Assertion</div><div class="exampleInner"><pre>(01) <wsdl:definitions>
+<div class="exampleHeader"><a name="idexamplex1x1503" id="idexamplex1x1503"/>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="...">
@@ -1479,7 +1485,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="idexamplex1x1762" id="idexamplex1x1762"/>Example 9-2: Sample WS-Eventing Policy with Embedded WSDL </div><div class="exampleInner"><pre>(01) <wsp:Policy>
+<div class="exampleHeader"><a name="idexamplex1x1764" id="idexamplex1x1764"/>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">
@@ -1509,7 +1515,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="idexamplex1x1772" id="idexamplex1x1772"/>Example 9-3: Sample EndpointReference with Embedded Policy </div><div class="exampleInner"><pre>(01) <wse:NotifyTo>
+<div class="exampleHeader"><a name="idexamplex1x1774" id="idexamplex1x1774"/>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>
@@ -1610,7 +1616,7 @@
security analysis to determine their particular threat profile and the
appropriate responses to those threats.
</p><div class="div2">
-<h3><a name="iddiv2x1x2019" id="iddiv2x1x2019"/>11.1 Metadata and Security Bootstrapping</h3><p>
+<h3><a name="iddiv2x1x2021" id="iddiv2x1x2021"/>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
@@ -1648,7 +1654,7 @@
indicate a particular security mechanism used to protect the
WS-MetadataExchange operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2x1x2040" id="iddiv2x1x2040"/>12.1 MetadataExchange Assertion</h3><p>
+<h3><a name="iddiv2x1x2042" id="iddiv2x1x2042"/>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 -
@@ -1868,7 +1874,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="iddiv2x1x2296" id="iddiv2x1x2296"/>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="iddiv2x1x2298" id="iddiv2x1x2298"/>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.
@@ -2403,4 +2409,5 @@
<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><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><tr><td> 2010/08/17 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=10339">10339</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=10339">10339</a></td></tr><tr><td> 2010/09/28 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=10768">10768</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Wednesday, 29 September 2010 03:19:31 UTC