- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 28 Jun 2010 12:13:16 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv14664
Modified Files:
wsmex.html wsmex.xml
Log Message:
remove an extra "and"
Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.118
retrieving revision 1.119
diff -u -d -r1.118 -r1.119
--- wsmex.xml 12 May 2010 20:50:05 -0000 1.118
+++ wsmex.xml 28 Jun 2010 12:13:14 -0000 1.119
@@ -74,7 +74,7 @@
associated with a Web service endpoint can be represented as
<bibref ref='WS-Transfer'/> resources or HTTP resources, how metadata can
be embedded in <bibref ref='AddrCore'/>
- endpoint references, and how metadata could be
+ endpoint references, how metadata could be
retrieved from a metadata resource, and how metadata associated with
implicit features can be advertised.
</p>
Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.131
retrieving revision 1.132
diff -u -d -r1.131 -r1.132
--- wsmex.html 12 May 2010 20:50:05 -0000 1.131
+++ wsmex.html 28 Jun 2010 12:13:14 -0000 1.132
@@ -31,13 +31,14 @@
</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"/></head><body><div class="head">
<h1><a name="title" id="title"/>Web Services Metadata Exchange (WS-MetadataExchange)</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"/>Editor's Draft $Date$</h2><dl><dt>Latest version:</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange">http://www.w3.org/TR/ws-metadata-exchange
- </a></dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2009/WD-ws-metadata-exchange-20090317">http://www.w3.org/TR/2009/WD-ws-metadata-exchange-20090317</a></dd><dt>Editors:</dt><dd>Doug Davis, IBM</dd><dd>Ashok Malhotra, Oracle</dd><dd>Katy Warr, IBM</dd><dd>Wu Chou, Avaya</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2010 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http//www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
+ </a></dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2009/WD-ws-metadata-exchange-20090317">http://www.w3.org/TR/2009/WD-ws-metadata-exchange-20090317
+ </a></dd><dt>Editors:</dt><dd>Doug Davis, IBM</dd><dd>Ashok Malhotra, Oracle</dd><dd>Katy Warr, IBM</dd><dd>Wu Chou, Avaya</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2010 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
<h2><a name="abstract" id="abstract"/>Abstract</h2><p>
This specification defines how metadata
associated with a Web service endpoint can be represented as
<a href="#WS-Transfer">[WS-Transfer]</a> resources or HTTP resources, how metadata can
be embedded in <a href="#AddrCore">[WS-Addressing]</a>
- endpoint references, and how metadata could be
+ endpoint references, how metadata could be
retrieved from a metadata resource, and how metadata associated with
implicit features can be advertised.
</p></div><div>
@@ -63,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="#iddiv2_1_1469">Examples</a><br/>
+ 7.3 <a href="#iddiv2x1x1469">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/>
@@ -72,14 +73,14 @@
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="#iddiv2_1_2015">Metadata and Security Bootstrapping</a><br/>
+ 11.1 <a href="#iddiv2x1x2015">Metadata and Security Bootstrapping</a><br/>
12 <a href="#metadata">WS-MetadataExchange Metadata</a><br/>
- 12.1 <a href="#iddiv2_1_2036">MetadataExchange Assertion</a><br/>
+ 12.1 <a href="#iddiv2x1x2036">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="#iddiv2_1_2292">Normative References</a><br/>
- 15.2 <a href="#iddiv2_1_2491">Informative References</a><br/>
+ 15.1 <a href="#iddiv2x1x2292">Normative References</a><br/>
+ 15.2 <a href="#iddiv2x1x2491">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/>
@@ -1036,7 +1037,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_1469" id="iddiv2_1_1469"/>7.3 Examples</h3><p>
+<h3><a name="iddiv2x1x1469" id="iddiv2x1x1469"/>7.3 Examples</h3><p>
The following examples show how metadata might appear in various
locations:
</p><div class="exampleOuter">
@@ -1067,7 +1068,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_1501" id="idexample_1_1501"/>Example 7-3: Feature Metadata in a Policy Assertion</div><div class="exampleInner"><pre>(01) <wsdl:definitions>
+<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>
(02) ...
(03) <wsdl:service name="stockQuote">
(04) <wsdl:port binding="..." name="...">
@@ -1607,7 +1608,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_2015" id="iddiv2_1_2015"/>11.1 Metadata and Security Bootstrapping</h3><p>
+<h3><a name="iddiv2x1x2015" id="iddiv2x1x2015"/>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
@@ -1645,7 +1646,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_2036" id="iddiv2_1_2036"/>12.1 MetadataExchange Assertion</h3><p>
+<h3><a name="iddiv2x1x2036" id="iddiv2x1x2036"/>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 -
@@ -1865,7 +1866,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_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>
+<h3><a name="iddiv2x1x2292" id="iddiv2x1x2292"/>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.
@@ -1942,7 +1943,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_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>
+<h3><a name="iddiv2x1x2491" id="iddiv2x1x2491"/>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>
Received on Monday, 28 June 2010 12:13:27 UTC