- From: Ashok Malhotra via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 18 Mar 2009 17:13:28 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv20246
Modified Files:
wsmex.html
Log Message:
Applied bug 6404
Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -d -r1.25 -r1.26
--- wsmex.html 18 Mar 2009 02:46:44 -0000 1.25
+++ wsmex.html 18 Mar 2009 17:13:26 -0000 1.26
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml" lang="en"><head><title>Web Services Metadata Exchange (WS-MetadataExchange)</title><style type="text/css">
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html lang="en" xmlns="http://www.w3.org/1999/xhtml"><head><title>Web Services Metadata Exchange (WS-MetadataExchange)</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
@@ -28,11 +28,16 @@
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
margin: 4px}
-</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>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> © 2009 <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>
+</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 18 March 2009</h2><dl><dt>This version:</dt><dd>
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7B@href%7D">http://www.w3.org/TR/2009/WD-ws-metadata-exchange-20090318
+ </a>
+ </dd><dt>Latest version:</dt><dd>
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7B@href%7D">http://www.w3.org/TR/ws-metadata-exchange
+ </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> © 2009 <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, how metadata can
@@ -40,39 +45,44 @@
endpoint references, and how metadata could be
retrieved from a Web service endpoint.
</p></div><div>
-<h2><a name="status" id="status"/>Status of this Document</h2><p><strong>This document is an editors' copy that has
- no official standing.</strong></p></div><div class="toc">
-<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#Composable">Composable Architecture</a><br/>
-2 <a href="#Introduction">Introduction</a><br/>
- 2.1 <a href="#Requirements">Requirements</a><br/>
- 2.2 <a href="#Example">Example</a><br/>
-3 <a href="#Notation">Notation</a><br/>
- 3.1 <a href="#Namespaces">XML Namespaces</a><br/>
- 3.2 <a href="#Conventions">Notational Conventions</a><br/>
- 3.3 <a href="#Compliance">Compliance</a><br/>
-4 <a href="#metadata-resources">Metadata Resources</a><br/>
-5 <a href="#web-services-metadata">Web Services Metadata</a><br/>
-6 <a href="#Retrieving-Metadata">Retrieving Metadata</a><br/>
- 6.1 <a href="#WS-Transfer-Get">WS-Transfer Get</a><br/>
- 6.2 <a href="#Get-Metadata">Get Metadata</a><br/>
-7 <a href="#Metadata-in-Endpoint-References">Metadata in Endpoint References</a><br/>
-8 <a href="#Bootstrapping-Metadata-Retrieval">Bootstrapping Metadata Retrieval</a><br/>
-9 <a href="#Security">Security</a><br/>
-10 <a href="#Acknowledgements">Acknowledgements</a><br/>
-11 <a href="#References">References</a><br/>
+<h2><a name="status" id="status" />Status of this Document</h2><p><strong>This document is an editors' copy that has
+ no official standing.</strong></p><p>This is the First Public Working Draft.</p><p>
+ Publication as a Working Draft does not imply endorsement by the
+ W3C Membership. This is a draft document and may be updated, replaced
+ or obsoleted by other documents at any time. It is inappropriate to
+ cite this document as other than work in progress.
+ </p></div><div class="toc">
+<h2><a name="contents" id="contents" />Table of Contents</h2><p class="toc">1 <a href="#Composable">Composable Architecture</a><br />
+2 <a href="#Introduction">Introduction</a><br />
+ 2.1 <a href="#Requirements">Requirements</a><br />
+ 2.2 <a href="#Example">Example</a><br />
+3 <a href="#Notation">Notation</a><br />
+ 3.1 <a href="#Namespaces">XML Namespaces</a><br />
+ 3.2 <a href="#Conventions">Notational Conventions</a><br />
+ 3.3 <a href="#Compliance">Compliance</a><br />
+4 <a href="#metadata-resources">Metadata Resources</a><br />
+5 <a href="#web-services-metadata">Web Services Metadata</a><br />
+6 <a href="#Retrieving-Metadata">Retrieving Metadata</a><br />
+ 6.1 <a href="#WS-Transfer-Get">WS-Transfer Get</a><br />
+ 6.2 <a href="#Get-Metadata">Get Metadata</a><br />
+7 <a href="#Metadata-in-Endpoint-References">Metadata in Endpoint References</a><br />
+8 <a href="#Bootstrapping-Metadata-Retrieval">Bootstrapping Metadata Retrieval</a><br />
+9 <a href="#Security">Security</a><br />
+10 <a href="#Acknowledgements">Acknowledgements</a><br />
+11 <a href="#References">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/>
-C <a href="#changelog">Change Log</a><br/>
-</p></div><hr/><div class="body"><div class="div1">
-<h2><a name="Composable" id="Composable"/>1 Composable Architecture</h2><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 />
+C <a href="#changelog">Change Log</a><br />
+</p></div><hr /><div class="body"><div class="div1">
+<h2><a name="Composable" id="Composable" />1 Composable Architecture</h2><p>
The Web services specifications (WS-*) are designed to be composed with
each other to provide a rich set of tools for the Web services
environment. This specification specifically relies on other Web
services specifications to provide secure, reliable, and/or transacted
message delivery and to express Web service metadata.
</p></div><div class="div1">
-<h2><a name="Introduction" id="Introduction"/>2 Introduction</h2><p>
+<h2><a name="Introduction" id="Introduction" />2 Introduction</h2><p>
Web services use metadata to describe what other endpoints need to know
to interact with them. Specifically, <a href="#WS-Policy">[WS-Policy]</a>
describes the capabilities, requirements, and general characteristics
@@ -101,7 +111,7 @@
mechanism for other types of data associated with a Web service,
such as state data, properties and attribute values, etc.
</p><div class="div2">
-<h3><a name="Requirements" id="Requirements"/>2.1 Requirements</h3><p>
+<h3><a name="Requirements" id="Requirements" />2.1 Requirements</h3><p>
This specification intends to meet the following requirements:
</p><ul><li><p>
Define an encapsulation format for metadata.
@@ -126,11 +136,12 @@
Enable description in <a href="#WSDL11">[WSDL 1.1]</a> of the optional
request-response interaction.
</p></li></ul></div><div class="div2">
-<h3><a name="Example" id="Example"/>2.2 Example</h3><p><a href="#GetRequest">Example 2-1</a> illustrates a sample
+<h3><a name="Example" id="Example" />2.2 Example</h3><p>
+ <a href="#GetRequest">Example 2-1</a> illustrates a sample
<a href="#WS-Transfer">[WS-Transfer]</a> Get request for a resource'
s representation.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="GetRequest" id="GetRequest"/>Example 2-1: Sample Get request message</div><div class="exampleInner"><pre>(01) <s11:Envelope
+<div class="exampleHeader"><a name="GetRequest" id="GetRequest" />Example 2-1: Sample Get request message</div><div class="exampleInner"><pre>(01) <s11:Envelope
(02) xmlns:s11='http://schemas.xmlsoap.org/soap/envelope/'
(03) xmlns:wsa='http://www.w3.org/2005/08/addressing'>
(04) <s11:Header>
@@ -154,10 +165,11 @@
endpoint. The fact that the resource's representation is a
mex:Metadata element may be known to the requestor but is not
explicitly encoded in the request message.
- </p><p><a href="#GetResponse">Example 2-2</a> illustrates a sample response to the
+ </p><p>
+ <a href="#GetResponse">Example 2-2</a> illustrates a sample response to the
request of <a href="#GetRequest">Example 2-1</a>.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="GetResponse" id="GetResponse"/>Example 2-2: Sample response message with metadata</div><div class="exampleInner"><pre>(01) <s11:Envelope
+<div class="exampleHeader"><a name="GetResponse" id="GetResponse" />Example 2-2: Sample response message with metadata</div><div class="exampleInner"><pre>(01) <s11:Envelope
(02) xmlns:s11='http://schemas.xmlsoap.org/soap/envelope/'
(03) xmlns:wsa='http://www.w3.org/2005/08/addressing'
(04) xmlns:mex='http://www.w3.org/2009/02/ws-mex'
@@ -263,7 +275,7 @@
<a href="#GetMexReq">Example 2-3</a> illustrates a sample Get Metadata request
for the <a href="#WS-Policy">[WS-Policy]</a>.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="GetMexReq" id="GetMexReq"/>Example 2-3: Sample Get Metadata request message</div><div class="exampleInner"><pre>(01) <s11:Envelope
+<div class="exampleHeader"><a name="GetMexReq" id="GetMexReq" />Example 2-3: Sample Get Metadata request message</div><div class="exampleInner"><pre>(01) <s11:Envelope
(02) xmlns:s11='http://schemas.xmlsoap.org/soap/envelope/'
(03) xmlns:wsa='http://www.w3.org/2005/08/addressing'
(04) xmlns:mex='http://www.w3.org/2009/02/ws-mex' >
@@ -289,10 +301,11 @@
Lines 7-9 in <a href="#GetMexReq">Example 2-3</a> indicate this is a Get Metadata
request. As lines 18-21 indicate, this request is for the policy of
the Web service endpoint (line 6).
- </p><p><a href="#GetMexRes">Example 2-4</a> lists a sample response to the request in
+ </p><p>
+ <a href="#GetMexRes">Example 2-4</a> lists a sample response to the request in
<a href="#GetMexReq">Example 2-3</a>.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="GetMexRes" id="GetMexRes"/>Example 2-4: Sample Get Metadata response message</div><div class="exampleInner"><pre>(01) <s11:Envelope
+<div class="exampleHeader"><a name="GetMexRes" id="GetMexRes" />Example 2-4: Sample Get Metadata response message</div><div class="exampleInner"><pre>(01) <s11:Envelope
(02) xmlns:s11='http://schemas.xmlsoap.org/soap/envelope/'
(03) xmlns:wsa='http://www.w3.org/2005/08/addressing'
(04) xmlns:wsp='http://schemas.xmlsoap.org/ws/2004/09/policy'
@@ -330,14 +343,15 @@
Web service endpoint to which the Get Metadata request of
<a href="#GetMexReq">Example 2-3</a> was directed.
</p></div></div><div class="div1">
-<h2><a name="Notation" id="Notation"/>3 Notation</h2><div class="div2">
-<h3><a name="Namespaces" id="Namespaces"/>3.1 XML Namespaces</h3><p>
+<h2><a name="Notation" id="Notation" />3 Notation</h2><div class="div2">
+<h3><a name="Namespaces" id="Namespaces" />3.1 XML Namespaces</h3><p>
The XML namespace URI that MUST be used by implementations of this
specification is:
- </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-mex">http://www.w3.org/2009/02/ws-mex</a></pre></div></div><p><a href="#XMLNS">Table 3-1</a> lists XML namespaces that are used in this
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2002/ws/ra/edcopies/%7B@href%7D">http://www.w3.org/2009/02/ws-mex</a></pre></div></div><p>
+ <a href="#XMLNS">Table 3-1</a> lists XML namespaces that are used in this
specification. The choice of any namespace prefix is arbitrary and
not semantically significant.
- </p><a name="XMLNS" id="XMLNS"/><table border="1"><caption>Table 3-1: Prefixes and XML namespaces used in this specification </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespaces </th><th align="left"> Specification(s) </th></tr><tr><td> s </td><td> (Either SOAP 1.1 or 1.2) </td><td> (Either SOAP 1.1 or 1.2) </td></tr><tr><td> s11 </td><td> http://schemas.xmlsoap.org/soap/envelope/ </td><td><a href="#SOAP11">[SOAP 1.1]</a></td></tr><tr><td> s12 </td><td> http://www.w3.org/2003/05/soap-envelope </td><td><a href="#SOAP12">[SOAP 1.2]</a></td></tr><tr><td> wsa </td><td> http://www.w3.org/2005/08/addressing </td><td><a href="#AddrCore">[WS-Addressing 1.0 Core]</a></td></tr><tr><td> wsdl </td><td> http://schemas.xmlsoap.org/wsdl/ </td><td><a href="#WSDL11">[WSDL 1.1]</a></td></tr><tr><td> wsp </td><td> http://schemas.xmlsoap.org/ws/2004/09/policy </td><td><a href="#WS-Policy">[WS-Policy]</a></td></tr><tr><td> mex </td><td> http://www.w3.org/2009/02/ws-mex </td><td> This specifiation </td></tr><tr><td> xs </td><td> http://www.w3.org/2001/XMLSchema </td><td><a href="#Schema1">[XML Schema: Structures]</a></td></tr><tr><td> wst </td><td> http://www.w3.org/2009/02/ws-tra </td><td><a href="#WS-Transfer">[WS-Transfer]</a></td></tr></tbody></table><p>
+ </p><a name="XMLNS" id="XMLNS" /><table border="1"><caption>Table 3-1: Prefixes and XML namespaces used in this specification </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespaces </th><th align="left"> Specification(s) </th></tr><tr><td> s </td><td> (Either SOAP 1.1 or 1.2) </td><td> (Either SOAP 1.1 or 1.2) </td></tr><tr><td> s11 </td><td> http://schemas.xmlsoap.org/soap/envelope/ </td><td> <a href="#SOAP11">[SOAP 1.1]</a> </td></tr><tr><td> s12 </td><td> http://www.w3.org/2003/05/soap-envelope </td><td> <a href="#SOAP12">[SOAP 1.2]</a> </td></tr><tr><td> wsa </td><td> http://www.w3.org/2005/08/addressing </td><td> <a href="#AddrCore">[WS-Addressing 1.0 Core]</a> </td></tr><tr><td> wsdl </td><td> http://schemas.xmlsoap.org/wsdl/ </td><td> <a href="#WSDL11">[WSDL 1.1]</a> </td></tr><tr><td> wsp </td><td> http://schemas.xmlsoap.org/ws/2004/09/policy </td><td> <a href="#WS-Policy">[WS-Policy]</a> </td></tr><tr><td> mex </td><td> http://www.w3.org/2009/02/ws-mex </td><td> Tis specification </td></tr><tr><td> xs </td><td> http://www.w3.org/2001/XMLSchema </td><td> <a href="#Schema1">[XML Schema: Structures]</a> </td></tr><tr><td> wst </td><td> http://www.w3.org/2009/02/ws-tra </td><td> <a href="#WS-Transfer">[WS-Transfer]</a> </td></tr></tbody></table><p>
The working group intends to update the value of the Web Services
Metadata Exchange namespace URI each time a new version of this document is
published until such time that the document reaches Candidate
@@ -347,14 +361,14 @@
Candidate Recommendation unless significant changes are made that
impact the implementation or break post-CR implementations of the
specification. Also see
- <a href="http://www.w3.org/2001/tag/doc/namespaceState.html">
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7B@href%7D">
http://www.w3.org/2001/tag/doc/namespaceState.html
</a> and
- <a href="http://www.w3.org/2005/07/13-nsuri">
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7B@href%7D">
http://www.w3.org/2005/07/13-nsuri
</a>.
</p></div><div class="div2">
-<h3><a name="Conventions" id="Conventions"/>3.2 Notational Conventions</h3><p>
+<h3><a name="Conventions" id="Conventions" />3.2 Notational Conventions</h3><p>
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119
@@ -394,7 +408,7 @@
this specification uses the following properties to define messages:
- </p><dl><dt class="label"><b>[Headers]</b></dt><dd><p>Unordered message headers. </p></dd><dt class="label"><b>[Action]</b></dt><dd><p> The value to be used for the wsa:Action URI. </p></dd><dt class="label"><b>[Body]</b></dt><dd><p> A message body. </p></dd></dl><p>
+ </p><dl><dt class="label"> <b>[Headers]</b> </dt><dd><p>Unordered message headers. </p></dd><dt class="label"> <b>[Action]</b> </dt><dd><p> The value to be used for the wsa:Action URI. </p></dd><dt class="label"> <b>[Body]</b> </dt><dd><p> A message body. </p></dd></dl><p>
These properties bind to a SOAP Envelope as follows:
@@ -413,7 +427,7 @@
fault and defines SOAP bindings for each Fault property.
</p></div><div class="div2">
-<h3><a name="Compliance" id="Compliance"/>3.3 Compliance</h3><p>
+<h3><a name="Compliance" id="Compliance" />3.3 Compliance</h3><p>
An implementation is not compliant with this specification if it
fails to satisfy one or more of the MUST or REQUIRED level
requirements defined herein. A SOAP Node MUST NOT use the XML
@@ -440,7 +454,7 @@
to a Web service that is addressable by an EPR
<a href="#AddrCore">[WS-Addressing 1.0 Core]</a>.
</p></div></div><div class="div1">
-<h2><a name="metadata-resources" id="metadata-resources"/>4 Metadata Resources</h2><p>
+<h2><a name="metadata-resources" id="metadata-resources" />4 Metadata Resources</h2><p>
A resource is a Web service that is addressable by an endpoint
reference <a href="#AddrCore">[WS-Addressing 1.0 Core]</a> and can
be represented by an XML Infoset. The resource's representation can be
@@ -468,7 +482,7 @@
non-static metadata by authorized agents), or other resource management
and access specifications (e.g. HTTP, WS-ResourceFramework).
</p></div><div class="div1">
-<h2><a name="web-services-metadata" id="web-services-metadata"/>5 Web Services Metadata</h2><p>
+<h2><a name="web-services-metadata" id="web-services-metadata" />5 Web Services Metadata</h2><p>
The Web service Metadata element is a collection of metadata units
such as <a href="#WSDL11">[WSDL 1.1]</a> definitions, <a href="#Schema1">[XML Schema: Structures]</a>
documents, <a href="#WS-Policy">[WS-Policy]</a> expressions, etc. Each unit
@@ -523,7 +537,7 @@
This specification defines the following values for Dialect;
other specifications should define values for Dialect for their
metadata format(s).
- </p><table border="1"><tbody><tr><th align="left"> Dialect URI </th><th align="left"> Metadata Format </th></tr><tr><td> http://www.w3.org/2001/XMLSchema </td><td> xs:schema <a href="#Schema1">[XML Schema: Structures]</a></td></tr><tr><td> http://schemas.xmlsoap.org/wsdl/ </td><td> wsdl:definitions <a href="#WSDL11">[WSDL 1.1]</a></td></tr><tr><td> http://schemas.xmlsoap.org/ws/2004/09/policy</td><td> wsp:Policy <a href="#WS-Policy">[WS-Policy]</a></td></tr><tr><td> http://schemas.xmlsoap.org/ws/2004/09/policy/attachment </td><td> wsp:PolicyAttachment <a href="#WS-PolicyAttachment">[WS-PolicyAttachment]</a></td></tr><tr><td> http://www.w3.org/2009/02/ws-mex </td><td> mex:Metadata [This specification] </td></tr></tbody></table><p>
+ </p><table border="1"><tbody><tr><th align="left"> Dialect URI </th><th align="left"> Metadata Format </th></tr><tr><td> http://www.w3.org/2001/XMLSchema </td><td> xs:schema <a href="#Schema1">[XML Schema: Structures]</a> </td></tr><tr><td> http://schemas.xmlsoap.org/wsdl/ </td><td> wsdl:definitions <a href="#WSDL11">[WSDL 1.1]</a> </td></tr><tr><td> http://schemas.xmlsoap.org/ws/2004/09/policy</td><td> wsp:Policy <a href="#WS-Policy">[WS-Policy]</a> </td></tr><tr><td> http://schemas.xmlsoap.org/ws/2004/09/policy/attachment </td><td> wsp:PolicyAttachment <a href="#WS-PolicyAttachment">[WS-PolicyAttachment]</a> </td></tr><tr><td> http://www.w3.org/2009/02/ws-mex </td><td> mex:Metadata [Defined in this specification] </td></tr><tr><td> http://www.w3.org/2009/02/ws-mex-all </td><td> None. [Defined in this specification for use in GetMetadata requests. See <a href="#Get-Metadata"><b>6.2 Get Metadata</b></a>.] </td></tr></tbody></table><p>
If there is more than one metadata unit with the same Dialect, e.g.,
more than one XML Schema document, including them all, one per
Metadata Section, is explicitly encouraged.
@@ -557,7 +571,7 @@
same. For well-known metadata formats, it is RECOMMENDED
that the value of the Identifier comes from the metadata when
that is possible, as the table below shows.
- </p></dd></dl><table border="1"><tbody><tr><th align="left"> Dialect URI </th><th align="left"> @Identifier value </th></tr><tr><td> http://www.w3.org/2001/XMLSchema </td><td> xs:schema/@targetNamespace </td></tr><tr><td> http://schemas.xmlsoap.org/wsdl/ </td><td> wsdl:definitions/@targetNamespace </td></tr><tr><td> http://schemas.xmlsoap.org/ws/2004/09/policy </td><td> wsp:Policy/@Name </td></tr><tr><td> http://schemas.xmlsoap.org/ws/2004/09/policy/attachment </td><td> Not defined </td></tr><tr><td> http://www.w3.org/2009/02/ws-mex </td><td> Not defined </td></tr></tbody></table><p>
+ </p></dd></dl><table border="1"><tbody><tr><th align="left"> Dialect URI </th><th align="left"> @Identifier value </th></tr><tr><td> http://www.w3.org/2001/XMLSchema </td><td> xs:schema/@targetNamespace </td></tr><tr><td> http://schemas.xmlsoap.org/wsdl/ </td><td> wsdl:definitions/@targetNamespace </td></tr><tr><td> http://schemas.xmlsoap.org/ws/2004/09/policy </td><td> wsp:Policy/@Name </td></tr><tr><td> http://schemas.xmlsoap.org/ws/2004/09/policy/attachment </td><td> Not defined </td></tr><tr><td> http://www.w3.org/2009/02/ws-mex </td><td> Not defined </td></tr><tr><td> http://www.w3.org/2009/02/ws-mex-all </td><td> Not defined </td></tr></tbody></table><p>
If there is more than one metadata section with the same
identifier, e.g., more than one XML Schema in the same target
namespace, including them all, one per metadata section, is
@@ -583,8 +597,8 @@
the metadata unit associated with the Metadata Section's Dialect
and Identifier.
</p></dd></dl></div><div class="div1">
-<h2><a name="Retrieving-Metadata" id="Retrieving-Metadata"/>6 Retrieving Metadata</h2><div class="div2">
-<h3><a name="WS-Transfer-Get" id="WS-Transfer-Get"/>6.1 WS-Transfer Get</h3><p>
+<h2><a name="Retrieving-Metadata" id="Retrieving-Metadata" />6 Retrieving Metadata</h2><div class="div2">
+<h3><a name="WS-Transfer-Get" id="WS-Transfer-Get" />6.1 WS-Transfer Get</h3><p>
To retrieve the representation of a metadata resource, a requester
MAY send a <a href="#WS-Transfer">[WS-Transfer]</a> Get request message to the
metadata resource's endpoint. The WS-Transfer Get request fetches a
@@ -600,7 +614,7 @@
<a href="#WS-Policy">[WS-Policy]</a>) for which a mex:MetadataSection/@Dialect
has been defined.
</p></div><div class="div2">
-<h3><a name="Get-Metadata" id="Get-Metadata"/>6.2 Get Metadata</h3><p>
+<h3><a name="Get-Metadata" id="Get-Metadata" />6.2 Get Metadata</h3><p>
When the metadata for an endpoint is not available or is unknown
and there is no information on how to retrieve it (e.g. an endpoint
reference to a <a href="#WS-Transfer">[WS-Transfer]</a> resource representing
@@ -624,21 +638,20 @@
</mex:GetMetadata> </pre></div></div><p>
The following describes additional, normative constraints on the
outline listed above:
- </p><dl><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect </dt><dd><p>
+ </p><dl><dt class="label"> <b>[Body]</b>/mex:GetMetadata/mex:Dialect </dt><dd><p>
When this repeating OPTIONAL element is present,the response
MUST include only Metadata Sections corresponding to the
dialect specified by the URI attribute; if the receiver does
not have any Metadata Sections of the indicated dialect, the
- response MUST include zero Metadata Sections. When this element
- is not present, there is no implied value and so the response
- may include Metadata Sections with any dialect.
- </p></dd><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect@URI </dt><dd><p>
- This REQUIRED attribute specifies the Metadata dialect. The
- response MUST only include Metadata Sections corresponding to
- the dialect specified by this URI. If the receiver does not
- have any Metadata Sections of this indicated dialect, the
- response MUST include zero Metadata Sections for this URI.
- </p></dd><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect@Identifier </dt><dd><p>
+ response MUST include zero Metadata Sections. </p><p>When this element
+ is not present, the endpoint SHOULD return all the types of metadata that it deems necessary to communicate with it.
+ </p></dd><dt class="label"> <b>[Body]</b>/mex:GetMetadata/mex:Dialect@URI </dt><dd><p>
+ This REQUIRED attribute specifies the Metadata dialect. The response MUST only include Metadata Sections corresponding to the dialect specified by this URI. If the receiver does not have any Metadata Sections of this indicated dialect, the response MUST include zero Metadata Sections for this URI.
+ </p></dd><dt class="label"> <b>[Body]</b>/mex:GetMetadata/mex:Dialect@URI="http://www.w3.org/2009/02/ws-mex-all" </dt><dd><p>
+ This value returns all known metadata. The endpoint has the option to optimize the format in which it returns the data.
+ </p></dd><dt class="label"> <b>[Body]</b>/mex:GetMetadata/mex:Dialect@URI="http://www.w3.org/2009/02/ws-mex" </dt><dd><p>
+ This value returns no metadata sections.
+ </p></dd><dt class="label"> <b>[Body]</b>/mex:GetMetadata/mex:Dialect@Identifier </dt><dd><p>
When this OPTIONAL attribute is present, the response MUST include only
Metadata Sections with the indicated identifier; if the receiver
does not have any Metadata Sections of the indicated identifier,
@@ -648,7 +661,7 @@
identifier.
If multiple Metadata Sections have the indicated Dialect
and Identifier then all of them MUST be returned.
- </p></dd><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect@Content </dt><dd><p>
+ </p></dd><dt class="label"> <b>[Body]</b>/mex:GetMetadata/mex:Dialect@Content </dt><dd><p>
When this OPTIONAL attribute is present, the response MUST include only
Metadata Sections of this specified content form. If the specified
content form is not available then the response MUST include zero
@@ -679,11 +692,12 @@
</mex:Metadata></pre></div></div><p>
The following describes additional, normative constraints on the
outline listed above:
- </p><dl><dt class="label"><b>[Body]</b>/mex:Metadata </dt><dd><p>
+ </p><dl><dt class="label"> <b>[Body]</b>/mex:Metadata </dt><dd><p>
The body of the response message MUST contain one mex:Metadata
element as defined in Section 4 of this specification.
</p></dd></dl></div></div><div class="div1">
-<h2><a name="Metadata-in-Endpoint-References" id="Metadata-in-Endpoint-References"/>7 Metadata in Endpoint References</h2><p><a href="#Retrieving-Metadata"><b>6 Retrieving Metadata</b></a> describes two mechanisms that
+<h2><a name="Metadata-in-Endpoint-References" id="Metadata-in-Endpoint-References" />7 Metadata in Endpoint References</h2><p>
+ <a href="#Retrieving-Metadata"><b>6 Retrieving Metadata</b></a> describes two mechanisms that
allow requesters to retrieve ("pull metadata") Web services metadata
from an endpoint (GetMetadata) or a metadata resource
(WS-Transfer Get).
@@ -717,7 +731,7 @@
endpoint reference contains WSDL metadata by value that identifies
the binding used to access the service endpoint:
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="EPRMEX" id="EPRMEX"/>Example 7-1: Endpoint reference with embedded WSDL metadata</div><div class="exampleInner"><pre>(01) <wsa:EndpointReference
+<div class="exampleHeader"><a name="EPRMEX" id="EPRMEX" />Example 7-1: Endpoint reference with embedded WSDL metadata</div><div class="exampleInner"><pre>(01) <wsa:EndpointReference
(02) xmlns:wsa='http://www.w3.org/2005/08/addressing'>
(03) <wsa:Address>http://services.example.org/stockquote</wsa:Address>
(04) <wsa:Metadata>
@@ -801,7 +815,7 @@
to the metadata resource's endpoint, as defined in
<a href="#Bootstrapping-Metadata-Retrieval"><b>8 Bootstrapping Metadata Retrieval</b></a>.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="EPRMD" id="EPRMD"/>Example 7-2: Endpoint reference with embedded metadata about the Metadata Reference</div><div class="exampleInner"><pre>(01) <wsa:EndpointReference
+<div class="exampleHeader"><a name="EPRMD" id="EPRMD" />Example 7-2: Endpoint reference with embedded metadata about the Metadata Reference</div><div class="exampleInner"><pre>(01) <wsa:EndpointReference
(02) xmlns:wsa='http://www.w3.org/2005/08/addressing'>
(03) <wsa:Address>http://services.example.org/stockquote</wsa:Address>
(04) <wsa:Metadata>
@@ -825,7 +839,8 @@
(22) </mex:MetadataSection>
(23) </mex:Metadata>
(24) </wsa:Metadata>
-(25) </wsa:EndpointReference></pre></div></div><p><a href="#EPRMD">Example 7-2</a> shows an example of a Web service endpoint
+(25) </wsa:EndpointReference></pre></div></div><p>
+ <a href="#EPRMD">Example 7-2</a> shows an example of a Web service endpoint
reference in which the Metadata element contains a single
Metadata Reference element to a metadata resource (lines 8-21) the
representation of which is mex:Metadata as hinted by the value of
@@ -838,7 +853,7 @@
WSDL portType and the necessary binding information for communicating
with that resource.
</p></div><div class="div1">
-<h2><a name="Bootstrapping-Metadata-Retrieval" id="Bootstrapping-Metadata-Retrieval"/>8 Bootstrapping Metadata Retrieval</h2><p>
+<h2><a name="Bootstrapping-Metadata-Retrieval" id="Bootstrapping-Metadata-Retrieval" />8 Bootstrapping Metadata Retrieval</h2><p>
This specification provides several mechanisms to aid service
endpoints and service requesters in bootstrapping the interaction.
In particular, the mechanisms described in
@@ -855,7 +870,7 @@
metadata retrieval may be defined by communities within the
context of particular application domains.
</p></div><div class="div1">
-<h2><a name="Security" id="Security"/>9 Security</h2><p>
+<h2><a name="Security" id="Security" />9 Security</h2><p>
It is strongly RECOMMENDED that the communication between Web services
be secured using the mechanisms described in WS-Security
<a href="#WS-Security">[WS-Security]</a>. In order to properly secure messages,
@@ -896,36 +911,43 @@
The following list summarizes common classes of attacks that apply to
this protocol and identifies the mechanism to prevent/mitigate
the attacks:
- </p><ul><li><p><b>Message alteration</b> - Alteration is prevented by including
+ </p><ul><li><p>
+ <b>Message alteration</b> - Alteration is prevented by including
signatures of the message information using WS-Security.
- </p></li><li><p><b>Message disclosure</b> - Confidentiality is preserved by
+ </p></li><li><p>
+ <b>Message disclosure</b> - Confidentiality is preserved by
encrypting sensitive data using WS-Security.
- </p></li><li><p><b>Key integrity</b> - Key integrity is maintained by using
+ </p></li><li><p>
+ <b>Key integrity</b> - Key integrity is maintained by using
the strongest algorithms possible (by comparing secured policies
- see <a href="#WS-Policy">[WS-Policy]</a> and
<a href="#WS-SecurityPolicy">[WS-SecurityPolicy]</a>)
- </p></li><li><p><b>Authentication</b> - Authentication is established using the
+ </p></li><li><p>
+ <b>Authentication</b> - Authentication is established using the
mechanisms described in WS-Security and WS-Trust. Each message is
authenticated using the mechanisms described in WS-Security
- </p></li><li><p><b>Accountability</b> - Accountability is a function of the type
+ </p></li><li><p>
+ <b>Accountability</b> - Accountability is a function of the type
of and strength of the key and algorithms being used. In many
cases, a strong symmetric key provides sufficient accountability.
However, in some environments, strong PKI signatures are required.
- </p></li><li><p><b>Availability</b> - Metadata services are subject to a variety
+ </p></li><li><p>
+ <b>Availability</b> - Metadata services are subject to a variety
of availability attacks such as application-level denial of
service. It is recommended that the mechanisms described in
WS-Security be considered as mitigations for some forms of
attacks. Other attacks, such as network-level denial of service
are harder to avoid. Note that both of these classes of attack
are outside the scope of this specification.
- </p></li><li><p><b>Replay</b> - Messages may be replayed for a variety of
+ </p></li><li><p>
+ <b>Replay</b> - Messages may be replayed for a variety of
reasons. To detect and eliminate this attack, mechanisms should
be used to identify replayed messages such as the timestamp/nonce
outlined in WS-Security. Alternatively, and optionally, other
technologies, such as sequencing, can also be used to prevent
replay of application messages.
</p></li></ul></div><div class="div1">
-<h2><a name="Acknowledgements" id="Acknowledgements"/>10 Acknowledgements</h2><p>
+<h2><a name="Acknowledgements" id="Acknowledgements" />10 Acknowledgements</h2><p>
This specification has been developed as a result of joint
work with many individuals and teams, including:
Ashok Malhotra (Oracle Corp.),
@@ -947,68 +969,82 @@
Wu Chou (Avaya Communications),
Yves Lafon (W3C)
</p></div><div class="div1">
-<h2><a name="References" id="References"/>11 References</h2><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h2><a name="References" id="References" />11 References</h2><dl><dt class="label"><a name="RFC2119" id="RFC2119" />RFC 2119</dt><dd>
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7Bancestor::bibl/@href%7D"><cite>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Harvard University, March 1997.
- (See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP 1.1</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
+ (See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a name="SOAP11" id="SOAP11" />SOAP 1.1</dt><dd>
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7Bancestor::bibl/@href%7D"><cite>
Simple Object Access Protocol (SOAP) 1.1
</cite></a>
, D. Box, et al, May 2000.
- (See http://www.w3.org/TR/2000/NOTE-SOAP-20000508/.)</dd><dt class="label"><a name="SOAP12" id="SOAP12"/>SOAP 1.2</dt><dd><a href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/"><cite>
+ (See http://www.w3.org/TR/2000/NOTE-SOAP-20000508/.)</dd><dt class="label"><a name="SOAP12" id="SOAP12" />SOAP 1.2</dt><dd>
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7Bancestor::bibl/@href%7D"><cite>
"SOAP Version 1.2 Part 1: Messaging Framework
</cite></a>
, M. Gudgin, et al, June 2003.
- (See http://www.w3.org/TR/2003/REC-soap12-part1-20030624/.)</dd><dt class="label"><a name="AddrCore" id="AddrCore"/>WS-Addressing 1.0 Core</dt><dd><a href="http://www.w3.org/TR/2006/PR-ws-addr-core-20060321/"><cite>
+ (See http://www.w3.org/TR/2003/REC-soap12-part1-20030624/.)</dd><dt class="label"><a name="AddrCore" id="AddrCore" />WS-Addressing 1.0 Core</dt><dd>
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7Bancestor::bibl/@href%7D"><cite>
Web Services Addressing 1.0 - Core" (Proposed Recommendation)
</cite></a>
, M. Gudgin, M. Hadley, T. Rogers (editors), March 2006.
- (See http://www.w3.org/TR/2006/PR-ws-addr-core-20060321/.)</dd><dt class="label"><a name="WS-Policy" id="WS-Policy"/>WS-Policy</dt><dd><a href="http://www.w3.org/Submission/2006/SUBM-WS-Policy-20060425/"><cite>
+ (See http://www.w3.org/TR/2006/PR-ws-addr-core-20060321/.)</dd><dt class="label"><a name="WS-Policy" id="WS-Policy" />WS-Policy</dt><dd>
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7Bancestor::bibl/@href%7D"><cite>
Web Services Policy Framework (WS-Policy)
</cite></a>
, S. Bajaj, et al, March 2006.
- (See http://www.w3.org/Submission/2006/SUBM-WS-Policy-20060425/.)</dd><dt class="label"><a name="WS-PolicyAttachment" id="WS-PolicyAttachment"/>WS-PolicyAttachment</dt><dd><a href="http://www.w3.org/Submission/2006/SUBM-WS-PolicyAttachment-20060425/"><cite>
+ (See http://www.w3.org/Submission/2006/SUBM-WS-Policy-20060425/.)</dd><dt class="label"><a name="WS-PolicyAttachment" id="WS-PolicyAttachment" />WS-PolicyAttachment</dt><dd>
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7Bancestor::bibl/@href%7D"><cite>
Web Services Policy Attachment (WS-PolicyAttachment)
</cite></a>
, S. Bajaj, et al, March 2006.
- (See http://www.w3.org/Submission/2006/SUBM-WS-PolicyAttachment-20060425/.)</dd><dt class="label"><a name="WS-SecureConversation" id="WS-SecureConversation"/>WS-SecureConversation</dt><dd><a href="http://www.oasis-open.org/committees/download.php/17364."><cite>
+ (See http://www.w3.org/Submission/2006/SUBM-WS-PolicyAttachment-20060425/.)</dd><dt class="label"><a name="WS-SecureConversation" id="WS-SecureConversation" />WS-SecureConversation</dt><dd>
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7Bancestor::bibl/@href%7D"><cite>
Web Services Secure Conversation Language (WS-SecureConversation)
</cite></a>
, S. Anderson, et al, February 2005.
- (See http://www.oasis-open.org/committees/download.php/17364..)</dd><dt class="label"><a name="WS-Security" id="WS-Security"/>WS-Security</dt><dd><a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"><cite>
+ (See http://www.oasis-open.org/committees/download.php/17364..)</dd><dt class="label"><a name="WS-Security" id="WS-Security" />WS-Security</dt><dd>
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7Bancestor::bibl/@href%7D"><cite>
Web Services Security: SOAP Message Security 1.0 (WS-Security 2004)
</cite></a>
, A. Nadalin, et al, March 2004.
- (See http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf.)</dd><dt class="label"><a name="WS-SecurityPolicy" id="WS-SecurityPolicy"/>WS-SecurityPolicy</dt><dd><a href="http://www.oasis-open.org/committees/download.php/16569/"><cite>
+ (See http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf.)</dd><dt class="label"><a name="WS-SecurityPolicy" id="WS-SecurityPolicy" />WS-SecurityPolicy</dt><dd>
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7Bancestor::bibl/@href%7D"><cite>
Web Services Security Policy Language (WS-SecurityPolicy)
</cite></a>
, G. Della-Libera, et al, July 2005.
- (See http://www.oasis-open.org/committees/download.php/16569/.)</dd><dt class="label"><a name="WS-Transfer" id="WS-Transfer"/>WS-Transfer</dt><dd><a href="http://www.w3.org/Submission/2006/SUBM-WS-Transfer-20060315/"><cite>
+ (See http://www.oasis-open.org/committees/download.php/16569/.)</dd><dt class="label"><a name="WS-Transfer" id="WS-Transfer" />WS-Transfer</dt><dd>
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7Bancestor::bibl/@href%7D"><cite>
Web Services Transfer (WS-Transfer)
</cite></a>
, J. Alexander, et al, September 2004.
- (See http://www.w3.org/Submission/2006/SUBM-WS-Transfer-20060315/.)</dd><dt class="label"><a name="WS-Trust" id="WS-Trust"/>WS-Trust</dt><dd><a href="http://www.oasis-open.org/committees/download.php/17364"><cite>
+ (See http://www.w3.org/Submission/2006/SUBM-WS-Transfer-20060315/.)</dd><dt class="label"><a name="WS-Trust" id="WS-Trust" />WS-Trust</dt><dd>
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7Bancestor::bibl/@href%7D"><cite>
Web Services Trust Language (WS-Trust)
</cite></a>
, S. Anderson, et al, February 2005.
- (See http://www.oasis-open.org/committees/download.php/17364.)</dd><dt class="label"><a name="WSDL11" id="WSDL11"/>WSDL 1.1</dt><dd><a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
+ (See http://www.oasis-open.org/committees/download.php/17364.)</dd><dt class="label"><a name="WSDL11" id="WSDL11" />WSDL 1.1</dt><dd>
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7Bancestor::bibl/@href%7D"><cite>
Web Services Description Language (WSDL) 1.1
</cite></a>
, E. Christensen, et al, March 2001
- (See http://www.w3.org/TR/2001/NOTE-wsdl-20010315.)</dd><dt class="label"><a name="Schema1" id="Schema1"/>XML Schema: Structures</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"><cite>
+ (See http://www.w3.org/TR/2001/NOTE-wsdl-20010315.)</dd><dt class="label"><a name="Schema1" id="Schema1" />XML Schema: Structures</dt><dd>
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7Bancestor::bibl/@href%7D"><cite>
XML Schema Part 1: Structures
</cite></a>
, H. Thompson, et al, October 2004.
- (See http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/.)</dd><dt class="label"><a name="Schema2" id="Schema2"/>XML Schema: Datatypes</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>
+ (See http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/.)</dd><dt class="label"><a name="Schema2" id="Schema2" />XML Schema: Datatypes</dt><dd>
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7Bancestor::bibl/@href%7D"><cite>
XML Schema Part 2: Datatypes
</cite></a>
, P. Biron, et al, October 2004.
(See http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/.)</dd></dl></div></div><div class="back"><div class="div1">
-<h2><a name="Appendix-A" id="Appendix-A"/>A XML Schema</h2><p>
+<h2><a name="Appendix-A" id="Appendix-A" />A XML Schema</h2><p>
A normative copy of the XML Schema <a href="#Schema1">[XML Schema: Structures]</a>,
<a href="#Schema2">[XML Schema: Datatypes]</a> description for this specification may be
retrieved from the following address:
- </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-mex/MetadataExchange.xsd">http://www.w3.org/2009/02/ws-mex/MetadataExchange.xsd</a></pre></div></div><p>
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2002/ws/ra/edcopies/%7B@href%7D">http://www.w3.org/2009/02/ws-mex/MetadataExchange.xsd</a></pre></div></div><p>
A non-normative copy of the XML Schema description is listed below for
convenience.
</p><div class="exampleOuter"><div class="exampleInner"><pre><xs:schema
@@ -1073,10 +1109,10 @@
<xs:element name='MetadataReference' type='wsa:EndpointReferenceType'/>
<xs:element name='Location' type='xs:anyURI'/>
</xs:schema></pre></div></div></div><div class="div1">
-<h2><a name="Appendix-B" id="Appendix-B"/>B WSDL</h2><p>
+<h2><a name="Appendix-B" id="Appendix-B" />B WSDL</h2><p>
A normative copy of the WSDL <a href="#WSDL11">[WSDL 1.1]</a> description for
this specification may be retrieved from the following address:
- </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-mex/metadataexchange.wsdl">http://www.w3.org/2009/02/ws-mex/metadataexchange.wsdl</a></pre></div></div><p>
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2002/ws/ra/edcopies/%7B@href%7D">http://www.w3.org/2009/02/ws-mex/metadataexchange.wsdl</a></pre></div></div><p>
A non-normative copy of the WSDL description is listed below for
convenience.
</p><div class="exampleOuter"><div class="exampleInner"><pre><wsdl:definitions
@@ -1114,11 +1150,20 @@
</wsdl:portType>
</wsdl:definitions></pre></div></div></div><div class="div1">
-<h2><a name="changelog" id="changelog"/>C Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6391">6391</a></td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6519">6519</a></td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added change log </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6639">6639</a></td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6425">6425</a></td></tr><tr><td> 2009/03/16 </td><td> KW </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6587">6587</a></td></tr><tr><td> 2009/03/17 </td><td> KW </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6405">6405</a></td></tr><tr><td> 2009/03/17 </td><td> KW </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6604">6604</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+<h2><a name="changelog" id="changelog" />C Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7B@href%7D">6391</a>
+ </td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7B@href%7D">6519</a>
+ </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added change log </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7B@href%7D">6639</a>
+ </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7B@href%7D">6425</a>
+ </td></tr><tr><td> 2009/03/16 </td><td> KW </td><td> Added resolution of issue
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7B@href%7D">6587</a>
+ </td></tr><tr><td> 2009/03/17 </td><td> KW </td><td> Added resolution of issue
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7B@href%7D">6405</a>
+ </td></tr><tr><td> 2009/03/17 </td><td> KW </td><td> Added resolution of issue
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7B@href%7D">6604</a>
+ </td></tr><tr><td> 2009/03/18 </td><td> AM </td><td> Added resolution of issue
+ <a href="http://www.w3.org/2002/ws/ra/edcopies/%7B@href%7D">6404</a>
+ </td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Wednesday, 18 March 2009 17:13:38 UTC