- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 23 Sep 2009 19:37:17 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv17237
Modified Files:
wsmex.html wsmex.xml
Log Message:
6570
Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -d -r1.50 -r1.51
--- wsmex.xml 23 Sep 2009 14:13:55 -0000 1.50
+++ wsmex.xml 23 Sep 2009 19:37:15 -0000 1.51
@@ -107,12 +107,12 @@
<p>
Web services use metadata to describe what other endpoints need to know
- to interact with them. Specifically, <bibref ref='WS-Policy'/>
+ to interact with them. Specifically, <bibref ref='wspolicy'/>
describes the capabilities, requirements, and general characteristics
of Web services; <bibref ref='WSDL11'/> describes abstract message
operations, concrete network protocols, and endpoint addresses used
- by Web services; XML Schema <bibref ref='Schema1'/>,
- <bibref ref='Schema2'/> describes the structure and contents of
+ by Web services; XML Schema <bibref ref='XMLSchema1'/>,
+ <bibref ref='XMLSchema2'/> describes the structure and contents of
XML-based messages received by and sent by Web services.
</p>
@@ -123,7 +123,7 @@
endpoint references, and how Web service endpoints can optionally
support a request-response interaction for the retrieval of metadata.
When the type of metadata sought is clearly known, e.g.,
- <bibref ref='WS-Policy'/>, a requester MAY indicate that only that
+ <bibref ref='wspolicy'/>, a requester MAY indicate that only that
type is to be returned; where additional types of metadata are being
used, or are expected, or when a requester needs to retrieve all of
the metadata relevant to subsequent interactions with an endpoint, a
@@ -163,8 +163,8 @@
<item>
<p>
Define an optional bootstrap mechanism for metadata-driven
- <bibref ref='Schema1'/>, <bibref ref='WSDL11'/>,
- <bibref ref='WS-Policy'/> message exchange.
+ <bibref ref='XMLSchema1'/>, <bibref ref='WSDL11'/>,
+ <bibref ref='wspolicy'/> message exchange.
</p>
</item>
@@ -189,7 +189,7 @@
<item>
<p>
- Support both <bibref ref='SOAP11'/> and <bibref ref='SOAP12'/>
+ Support both <bibref ref='SOAP11'/> and <bibref ref='SOAP121'/>
Envelopes.
</p>
</item>
@@ -343,13 +343,13 @@
contains three Metadata Sections. The first Metadata Section
(lines 18-61) contains the <bibref ref ='WSDL11'/> of the Web
service endpoint. The second Metadata Section (lines 62-68) contains
- the location of the XML Schemas <bibref ref ='Schema1'/>,
- <bibref ref ='Schema2'/> used by the WSDL document. The schemas can
+ the location of the XML Schemas <bibref ref ='XMLSchema1'/>,
+ <bibref ref ='XMLSchema2'/> used by the WSDL document. The schemas can
be retrieved through an HTTP GET request at the identified URL
(lines 65-67). The third Metadata Section (lines 69-77) contains
the <bibref ref ='AddrCore'/> endpoint reference (lines 72-75) of
a <bibref ref ='WS-Transfer'/> resource the representation of
- which is a <bibref ref ='WS-Policy'/> document as indicated by
+ which is a <bibref ref ='wspolicy'/> document as indicated by
the Dialect attribute (line 70). The WS-Policy document is the
same as the one indicated in the WSDL document (lines 39-40).
</p>
@@ -361,7 +361,7 @@
<specref ref="GetResponse"/>,
some endpoints MAY choose to support explicit request for metadata.
<specref ref="GetMexReq"/> illustrates a sample GetMetadata request
- for the <bibref ref ='WS-Policy'/>.
+ for the <bibref ref ='wspolicy'/>.
</p>
<example id="GetMexReq">
@@ -493,7 +493,7 @@
<tr>
<td> s12 </td>
<td> http://www.w3.org/2003/05/soap-envelope </td>
- <td> <bibref ref="SOAP12"/> </td>
+ <td> <bibref ref="SOAP121"/> </td>
</tr>
<tr>
<td> wsa </td>
@@ -508,7 +508,7 @@
<tr>
<td> wsp </td>
<td> http://www.w3.org/ns/ws-policy </td>
- <td> <bibref ref="WS-Policy"/> </td>
+ <td> <bibref ref="wspolicy"/> </td>
</tr>
<tr>
<td> mex </td>
@@ -518,7 +518,7 @@
<tr>
<td> xs </td>
<td> http://www.w3.org/2001/XMLSchema </td>
- <td> <bibref ref="Schema1"/> </td>
+ <td> <bibref ref="XMLSchema1"/> </td>
</tr>
<tr>
<td> wst </td>
@@ -748,8 +748,9 @@
<p>
When the representation of a resource is mex:Metadata, as defined
in Section 4, or any other document format (e.g.
- <bibref ref='Schema1'/>,<bibref ref='Schema2'/>, <bibref ref='WSDL11'/>,
- <bibref ref='WS-Policy'/>) for which a mex:MetadataSection/@Dialect has
+ <bibref ref='XMLSchema1'/>,<bibref ref='XMLSchema2'/>,
+ <bibref ref='WSDL11'/>,
+ <bibref ref='wspolicy'/>) for which a mex:MetadataSection/@Dialect has
been defined, then the resource is referred as 'metadata resource'.
The representation of a metadata resource MAY be retrieved and/or
updated as any other <bibref ref='WS-Transfer'/> resource.
@@ -779,8 +780,8 @@
<p>
The Web service Metadata element is a collection of metadata units
- such as <bibref ref='WSDL11'/> definitions, <bibref ref='Schema1'/>
- documents, <bibref ref='WS-Policy'/> expressions, etc. Each unit
+ such as <bibref ref='WSDL11'/> definitions, <bibref ref='XMLSchema1'/>
+ documents, <bibref ref='wspolicy'/> expressions, etc. Each unit
corresponds to metadata for a given scope, domain, or namespace. The
collection of units is represented by a Metadata element, and units
within the collection are represented by Metadata Section elements.
@@ -875,7 +876,7 @@
</tr>
<tr>
<td> http://www.w3.org/2001/XMLSchema </td>
- <td> xs:schema <bibref ref="Schema1"/> </td>
+ <td> xs:schema <bibref ref="XMLSchema1"/> </td>
</tr>
<tr>
<td> http://schemas.xmlsoap.org/wsdl/ </td>
@@ -883,7 +884,7 @@
</tr>
<tr>
<td> http://www.w3.org/ns/ws-policy </td>
- <td> wsp:Policy <bibref ref="WS-Policy"/> </td>
+ <td> wsp:Policy <bibref ref="wspolicy"/> </td>
</tr>
<tr>
<td> http://www.w3.org/TR/ws-policy-attach </td>
@@ -1060,9 +1061,9 @@
<p>
The representation of a metadata resource MAY also be
- any other document format (e.g. <bibref ref='Schema1'/>,
- <bibref ref='Schema2'/>, <bibref ref='WSDL11'/>,
- <bibref ref='WS-Policy'/>) for which a dialect value is defined.
+ any other document format (e.g. <bibref ref='XMLSchema1'/>,
+ <bibref ref='XMLSchema2'/>, <bibref ref='WSDL11'/>,
+ <bibref ref='wspolicy'/>) for which a dialect value is defined.
</p>
</div2>
@@ -1486,7 +1487,7 @@
<p>
It is strongly RECOMMENDED that the communication between Web services
be secured using the mechanisms described in WS-Security
- <bibref ref='WS-Security'/>. In order to properly secure messages,
+ <bibref ref='WSSecurity'/>. In order to properly secure messages,
the body and all relevant headers need to be included in the
signature. Specifically, any standard messaging headers, such as
those from WS-Addressing
@@ -1500,8 +1501,8 @@
technologies might be adequate for integrity and confidentiality.
However, for high-frequency events, it might be more performant to
establish a security context for the events using the mechanisms
- described in <bibref ref='WS-Trust'/> and
- <bibref ref='WS-SecureConversation'/>. Note that if
+ described in <bibref ref='WSTrust'/> and
+ <bibref ref='WSSecureConversation'/>. Note that if
a shared secret is used it is RECOMMENDED that derived keys be used
to strengthen the secret as described in WS-SecureConversation.
</p>
@@ -1525,7 +1526,7 @@
<p>
Additionally, some metadata formats, such as policies
- <bibref ref='WS-Policy'/>, can have embedded security
+ <bibref ref='wspolicy'/>, can have embedded security
semantics. These SHOULD be verified using the same considerations
outlined in this section.
</p>
@@ -1553,8 +1554,8 @@
<p>
<kw>Key integrity</kw> - Key integrity is maintained by using
the strongest algorithms possible (by comparing secured policies
- - see <bibref ref='WS-Policy'/> and
- <bibref ref='WS-SecurityPolicy'/>)
+ - see <bibref ref='wspolicy'/> and
+ <bibref ref='WSSecurityPolicy'/>)
</p>
</item>
<item>
@@ -1638,136 +1639,171 @@
<div1 id="References">
<head>References</head>
-
- <blist>
- <bibl id="RFC2119" key="RFC 2119"
- href="http://www.ietf.org/rfc/rfc2119.txt">
- <titleref>
- Key words for use in RFCs to Indicate Requirement Levels
- </titleref>
- , S. Bradner, Harvard University, March 1997.
- </bibl>
- <bibl id="RFC3986" key="RFC 3986"
- href="http://www.ietf.org/rfc/rfc3986.txt">
- <titleref>
- Uniform Resource Identifier (URI): Generic Syntax
- </titleref>
- , T. Berners-Lee, W3C/MIT, January 2005.
- </bibl>
+ <div2>
+ <head>Normative References</head>
- <bibl id="SOAP11" key="SOAP 1.1"
- href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">
- <titleref>
- Simple Object Access Protocol (SOAP) 1.1
- </titleref>
- , D. Box, et al, May 2000.
- </bibl>
+ <blist>
+ <bibl key="RFC 2119" id="RFC2119"
+ href="http://www.ietf.org/rfc/rfc2119.txt">
+ <titleref>
+ Key words for use in RFCs to Indicate Requirement Levels
+ </titleref>
+ , S. Bradner, Author.
+ Internet Engineering Task Force, March 1997.
+ </bibl>
- <bibl id="SOAP12" key="SOAP 1.2"
- href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/">
- <titleref>
- "SOAP Version 1.2 Part 1: Messaging Framework
- </titleref>
- , M. Gudgin, et al, June 2003.
- </bibl>
+ <bibl key="RFC 3986" id="RFC3986"
+ href="http://www.ietf.org/rfc/rfc3986.txt">
+ <titleref>
+ Uniform Resource Identifier (URI): Generic Syntax
+ </titleref>
+ , T. Berners-Lee, R. Fields and L. Masinter, Authors.
+ Network Working Group, January 2005.
+ </bibl>
- <bibl key="WS-Addressing" id="AddrCore"
- href="http://www.w3.org/2005/08/addressing/">
+ <bibl key="SOAP11" id="SOAP11"
+ href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">
+ <titleref>
+ W3C Note, "Simple Object Access Protocol (SOAP) 1.1"
+ </titleref>
+ , D. Box, et al, Editors.
+ World Wide Web Consortium (W3C), 8 May 2000.
+ </bibl>
+
+ <bibl key="SOAP12" id="SOAP121"
+ href="http://www.w3.org/TR/soap12-part1/">
+ <titleref>
+ W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
+ </titleref>
+ , M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielson,
+ Editors.
+ World Wide Web Consortium (W3C), 27 April 2007.
+ </bibl>
+
+ <bibl key="WS-Addressing" id="AddrCore"
+ href="http://www.w3.org/TR/ws-addr-core">
+ <titleref>
+ W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
+ </titleref>
+ , M. Gudgin, M. Hadley, T. Rogers, Editors.
+ World Wide Web Consortium (W3C), 9 May 2006.
+ </bibl>
+
+ <bibl key="WS-Policy" id="wspolicy"
+ href="http://www.w3.org/TR/ws-policy/">
+ <titleref>
+ W3C Recommendation, "Web Services Policy (WS-Policy) 1.5 - Framework"
+ </titleref>
+ , A. Vedamuthu, et al., Editors.
+ World Wide Web Consortium (W3C), 4 September 2007.
+ </bibl>
+
+ <bibl id="WS-PolicyAttachment" key="WS-PolicyAttachment"
+ href="http://www.w3.org/TR/ws-policy-attach/">
<titleref>
- W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
+ W3C Recommendation, "Web Services Policy (WS-Policy) 1.5 - Attachment"
</titleref>
- , May 2006.
- </bibl>
-
- <bibl id="WS-Policy" key="WS-Policy"
- href="http://www.w3.org/TR/ws-policy/">
- <titleref>
- W3C Recommendation, "Web Services Policy 1.5 - Framework"
- </titleref>
- , September 2007.
- </bibl>
+ , A. Vedamuthu, et al., Editors.
+ World Wide Web Consortium (W3C), 4 September 2007.
+ </bibl>
- <bibl id="WS-PolicyAttachment" key="WS-PolicyAttachment"
- href="http://www.w3.org/TR/ws-policy-attach/">
- <titleref>
- W3C Recommendation, "Web Services Policy 1.5 - Attachment"
- </titleref>
- , September 2007.
- </bibl>
+ <bibl id="WS-Transfer" key="WS-Transfer"
+ href="http://www.w3.org/TR/ws-transfer">
+ <titleref>
+ W3C Working Group Draft, "Web Services Transfer (WS-Transfer)1.1"
+ </titleref>
+ , D. Davis, et al., Editors.
+ World Wide Web Consortium (W3C), 15 September 2009.
+ </bibl>
- <bibl id="WS-SecureConversation" key="WS-SecureConversation"
- href="http://www.oasis-open.org/committees/download.php/17364.">
- <titleref>
- Web Services Secure Conversation Language (WS-SecureConversation)
- </titleref>
- , S. Anderson, et al, February 2005.
- </bibl>
+ <bibl key="WSDL11" id="WSDL11"
+ href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">
+ <titleref>
+ W3C Note, "Web Services Description Language (WSDL) 1.1"
+ </titleref>
+ , E. Christensen, et al., Editors.
+ World Wide Web Consortium (W3C), 15 March 2001
+ </bibl>
- <bibl id="WS-Security" key="WS-Security"
- href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf">
- <titleref>
- Web Services Security: SOAP Message Security 1.0 (WS-Security 2004)
- </titleref>
- , A. Nadalin, et al, March 2004.
- </bibl>
+ <bibl key="XML Infoset" id="XMLInfoset"
+ href="http://www.w3.org/TR/xml-infoset">
+ <titleref>
+ W3C Recommendation, "XML Information Set (Second Edition)"
+ </titleref>
+ , J. Cowan, R. Tobin, Editors.
+ World Wide Web Consortium (W3C), 4 February 2004.
+ </bibl>
- <bibl id="WS-SecurityPolicy" key="WS-SecurityPolicy"
- href="http://www.oasis-open.org/committees/download.php/16569/">
- <titleref>
- Web Services Security Policy Language (WS-SecurityPolicy)
- </titleref>
- , G. Della-Libera, et al, July 2005.
- </bibl>
+ <bibl key="XMLSchema - Part 1" id="XMLSchema1"
+ href="http://www.w3.org/TR/xmlschema-1/">
+ <titleref>
+ W3C Recommendation, "XML Schema Part 1: Structures (Second Edition)"
+ </titleref>
+ , H. Thompson, et al., Editors.
+ World Wide Web Consortium (W3C), 28 October 2004.
+ </bibl>
- <bibl id="WS-Transfer" key="WS-Transfer"
- href="http://www.w3.org/Submission/2006/SUBM-WS-Transfer-20060315/">
- <titleref>
- Web Services Transfer (WS-Transfer)
- </titleref>
- , J. Alexander, et al, September 2004.
- </bibl>
+ <bibl key="XMLSchema - Part 2" id="XMLSchema2"
+ href="http://www.w3.org/TR/xmlschema-2/">
+ <titleref>
+ W3C Recommendation, "XML Schema Part 2: Datatypes (Second Edition)"
+ </titleref>
+ , P. Biron, A. Malhotra, Editors.
+ World Wide Web Consortium (W3C), 28 October 2004.
+ </bibl>
- <bibl id="WS-Trust" key="WS-Trust"
- href="http://www.oasis-open.org/committees/download.php/17364">
- <titleref>
- Web Services Trust Language (WS-Trust)
- </titleref>
- , S. Anderson, et al, February 2005.
- </bibl>
+ </blist>
+ </div2>
+
+ <div2>
+ <head>Informative References</head>
- <bibl id="WSDL11" key="WSDL 1.1"
- href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">
- <titleref>
- Web Services Description Language (WSDL) 1.1
- </titleref>
- , E. Christensen, et al, March 2001
- </bibl>
+ <blist>
+ <bibl key="WS-SecureConversation" id="WSSecureConversation"
+ href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc">
+ <titleref>
+ OASIS Standard, "Web Services Secure Conversation
+ (WS-SecureConversation) 1.4"
+ </titleref>
+ , A. Nadalin, et al., Editors.
+ Organization for the Advancement of Structured Information Standards
+ (OASIS), 2 February 2009.
+ </bibl>
- <bibl key="XML Infoset" id="XMLInfoset"
- href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/">
- <titleref>
- XML Information Set
- </titleref>
- , J. Cowan, et al, February 2004.
- </bibl>
+ <bibl key="WS-Security" id="WSSecurity"
+ href="http://docs.oasis-open.org/wss/v1.1/wss-v1.1-spec-os-SOAPMessageSecurity.pdf">
+ <titleref>
+ OASIS Standard, "Web Services Security: SOAP Message Security 1.1"
+ </titleref>
+ , K. Lawrence, C. Kaler, Editors.
+ Organization for the Advancement of Structured Information Standards
+ (OASIS), 1 February 2006.
+ </bibl>
- <bibl id="Schema1" key="XML Schema: Structures"
- href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">
- <titleref>
- XML Schema Part 1: Structures
- </titleref>
- , H. Thompson, et al, October 2004.
- </bibl>
+ <bibl key="WS-SecurityPolicy" id="WSSecurityPolicy"
+ href="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/v1.3/os/ws-securitypolicy-1.3-spec-os.doc">
+ <titleref>
+ OASIS Standard, "Web Services Security Policy (WS-SecurityPolicy) 1.3,
+ Version 1.1"
+ </titleref>
+ , K. Lawrence, C. Kaler, Editors.
+ Organization for the Advancement of Structured Information Standards
+ (OASIS), 2 February 2009.
+ </bibl>
- <bibl id="Schema2" key="XML Schema: Datatypes"
- href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">
- <titleref>
- XML Schema Part 2: Datatypes
- </titleref>
- , P. Biron, et al, October 2004.
- </bibl>
- </blist>
+ <bibl key="WS-Trust" id="WSTrust"
+ href="http://docs.oasis-open.org/ws-sx/ws-trust/v1.4/os/ws-trust-1.4-spec-os.doc">
+ <titleref>
+ OASIS Standard, "Web Services Trust (WS-Trust) 1.4"
+ </titleref>
+ , K. Lawrence, C. Kaler, Editors.
+ Organization for the Advancement of Structured Information Standards
+ (OASIS), 2 February 2009.
+ </bibl>
+ </blist>
+ </div2>
+
</div1>
</body>
@@ -1776,8 +1812,8 @@
<head>XML Schema</head>
<p>
- A normative copy of the XML Schema <bibref ref='Schema1'/>,
- <bibref ref='Schema2'/> description for this specification can be
+ A normative copy of the XML Schema <bibref ref='XMLSchema1'/>,
+ <bibref ref='XMLSchema2'/> description for this specification can be
retrieved from the following address:
</p>
@@ -2144,6 +2180,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533">6533</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/09/23 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6570">6570</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -d -r1.61 -r1.62
--- wsmex.html 23 Sep 2009 14:13:55 -0000 1.61
+++ wsmex.html 23 Sep 2009 19:37:15 -0000 1.62
@@ -62,6 +62,8 @@
10 <a href="#policy">WS-MetadataExchange Policy Assertion(s)</a><br/>
11 <a href="#Acknowledgements">Acknowledgements</a><br/>
12 <a href="#References">References</a><br/>
+ 12.1 <a href="#iddiv2_1_1331">Normative References</a><br/>
+ 12.2 <a href="#iddiv2_1_1491">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/>
@@ -76,12 +78,12 @@
</p></div><div class="div1">
<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>
+ to interact with them. Specifically, <a href="#wspolicy">[WS-Policy]</a>
describes the capabilities, requirements, and general characteristics
- of Web services; <a href="#WSDL11">[WSDL 1.1]</a> describes abstract message
+ of Web services; <a href="#WSDL11">[WSDL11]</a> describes abstract message
operations, concrete network protocols, and endpoint addresses used
- by Web services; XML Schema <a href="#Schema1">[XML Schema: Structures]</a>,
- <a href="#Schema2">[XML Schema: Datatypes]</a> describes the structure and contents of
+ by Web services; XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>,
+ <a href="#XMLSchema2">[XMLSchema - Part 2]</a> describes the structure and contents of
XML-based messages received by and sent by Web services.
</p><p>
To bootstrap communication with Web services this specification defines
@@ -90,7 +92,7 @@
endpoint references, and how Web service endpoints can optionally
support a request-response interaction for the retrieval of metadata.
When the type of metadata sought is clearly known, e.g.,
- <a href="#WS-Policy">[WS-Policy]</a>, a requester MAY indicate that only that
+ <a href="#wspolicy">[WS-Policy]</a>, a requester MAY indicate that only that
type is to be returned; where additional types of metadata are being
used, or are expected, or when a requester needs to retrieve all of
the metadata relevant to subsequent interactions with an endpoint, a
@@ -112,8 +114,8 @@
<a href="#WS-Transfer">[WS-Transfer]</a> resources.
</p></li><li><p>
Define an optional bootstrap mechanism for metadata-driven
- <a href="#Schema1">[XML Schema: Structures]</a>, <a href="#WSDL11">[WSDL 1.1]</a>,
- <a href="#WS-Policy">[WS-Policy]</a> message exchange.
+ <a href="#XMLSchema1">[XMLSchema - Part 1]</a>, <a href="#WSDL11">[WSDL11]</a>,
+ <a href="#wspolicy">[WS-Policy]</a> message exchange.
</p></li><li><p>
Support future versions of known metadata formats.
</p></li><li><p>
@@ -122,10 +124,10 @@
Leverage other Web service specifications for secure, reliable,
transacted message delivery.
</p></li><li><p>
- Support both <a href="#SOAP11">[SOAP 1.1]</a> and <a href="#SOAP12">[SOAP 1.2]</a>
+ Support both <a href="#SOAP11">[SOAP11]</a> and <a href="#SOAP121">[SOAP12]</a>
Envelopes.
</p></li><li><p>
- Enable description in <a href="#WSDL11">[WSDL 1.1]</a> of the optional
+ Enable description in <a href="#WSDL11">[WSDL11]</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
@@ -245,15 +247,15 @@
metadata
about the Web service endpoint (lines 17-78). The mex:Metadata
contains three Metadata Sections. The first Metadata Section
- (lines 18-61) contains the <a href="#WSDL11">[WSDL 1.1]</a> of the Web
+ (lines 18-61) contains the <a href="#WSDL11">[WSDL11]</a> of the Web
service endpoint. The second Metadata Section (lines 62-68) contains
- the location of the XML Schemas <a href="#Schema1">[XML Schema: Structures]</a>,
- <a href="#Schema2">[XML Schema: Datatypes]</a> used by the WSDL document. The schemas can
+ the location of the XML Schemas <a href="#XMLSchema1">[XMLSchema - Part 1]</a>,
+ <a href="#XMLSchema2">[XMLSchema - Part 2]</a> used by the WSDL document. The schemas can
be retrieved through an HTTP GET request at the identified URL
(lines 65-67). The third Metadata Section (lines 69-77) contains
the <a href="#AddrCore">[WS-Addressing]</a> endpoint reference (lines 72-75) of
a <a href="#WS-Transfer">[WS-Transfer]</a> resource the representation of
- which is a <a href="#WS-Policy">[WS-Policy]</a> document as indicated by
+ which is a <a href="#wspolicy">[WS-Policy]</a> document as indicated by
the Dialect attribute (line 70). The WS-Policy document is the
same as the one indicated in the WSDL document (lines 39-40).
</p><p>
@@ -263,7 +265,7 @@
<a href="#GetResponse">Example 2-2</a>,
some endpoints MAY choose to support explicit request for metadata.
<a href="#GetMexReq">Example 2-3</a> illustrates a sample GetMetadata request
- for the <a href="#WS-Policy">[WS-Policy]</a>.
+ for the <a href="#wspolicy">[WS-Policy]</a>.
</p><div class="exampleOuter">
<div class="exampleHeader"><a name="GetMexReq" id="GetMexReq"/>Example 2-3: Sample GetMetadata request message</div><div class="exampleInner"><pre>(01) <s11:Envelope
(02) xmlns:s11='http://schemas.xmlsoap.org/soap/envelope/'
@@ -339,7 +341,7 @@
</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
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]</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://www.w3.org/ns/ws-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 specification </td></tr><tr><t> 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">[SOAP11]</a></td></tr><tr><td> s12 </td><td> http://www.w3.org/2003/05/soap-envelope </td><td><a href="#SOAP121">[SOAP12]</a></td></tr><tr><td> wsa </td><td> http://www.w3.org/2005/08/addressing </td><td><a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td> wsdl </td><td> http://schemas.xmlsoap.org/wsdl/ </td><td><a href="#WSDL11">[WSDL11]</a></td></tr><tr><td> wsp </td><td> http://www.w3.org/ns/ws-policy </td><td><a href="#wspolicy">[WS-Policy]</a></td></tr><tr><td> mex </td><td> http://www.w3.org/2009/02/ws-mex </td><td> This specification </td></tr><tr><td> xs /td><td> http://www.w3.org/2001/XMLSchema </td><td><a href="#XMLSchema1">[XMLSchema - Part 1]</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
@@ -458,8 +460,9 @@
</p><p>
When the representation of a resource is mex:Metadata, as defined
in Section 4, or any other document format (e.g.
- <a href="#Schema1">[XML Schema: Structures]</a>,<a href="#Schema2">[XML Schema: Datatypes]</a>, <a href="#WSDL11">[WSDL 1.1]</a>,
- <a href="#WS-Policy">[WS-Policy]</a>) for which a mex:MetadataSection/@Dialect has
+ <a href="#XMLSchema1">[XMLSchema - Part 1]</a>,<a href="#XMLSchema2">[XMLSchema - Part 2]</a>,
+ <a href="#WSDL11">[WSDL11]</a>,
+ <a href="#wspolicy">[WS-Policy]</a>) for which a mex:MetadataSection/@Dialect has
been defined, then the resource is referred as 'metadata resource'.
The representation of a metadata resource MAY be retrieved and/or
updated as any other <a href="#WS-Transfer">[WS-Transfer]</a> resource.
@@ -479,8 +482,8 @@
</p></div><div class="div1">
<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
+ such as <a href="#WSDL11">[WSDL11]</a> definitions, <a href="#XMLSchema1">[XMLSchema - Part 1]</a>
+ documents, <a href="#wspolicy">[WS-Policy]</a> expressions, etc. Each unit
corresponds to metadata for a given scope, domain, or namespace. The
collection of units is represented by a Metadata element, and units
within the collection are represented by Metadata Section elements.
@@ -530,7 +533,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://www.w3.org/ns/ws-policy </td><td> wsp:Policy <a href="#WS-Policy">[WS-Policy]</a></td></tr><tr><td> http://www.w3.org/TR/ws-policy-attach </td><td> wsp:PolicyAttachment <a href="#WS-PolicyAttachment">[WS-PolicyAttachment]</a></td></tr><tr><td> http://www.w3.org/2009/02/ws-mex/Dialects/ws-mex </td><td> mex:Metadata [Defined in this specification] </td></tr><tr><td> http://www.w3.org/2009/02/ws-mex/Dialects/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>
+ </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="#XMLSchema1">[XMLSchema - Part 1]</a></td></tr><tr><td> http://schemas.xmlsoap.org/wsdl/ </td><td> wsdl:definitions <a href="#WSDL11">[WSDL11]</a></td></tr><tr><td> http://www.w3.org/ns/ws-policy </td><td> wsp:Policy <a href="#wspolicy">[WS-Policy]</a></td></tr><tr><td> http://www.w3.org/TR/ws-policy-attach </td><td> wsp:PolicyAttachment <a href="#WS-PolicyAttachment">[WS-PolicyAttachment]</a></td></tr><tr><td> http://www.w3.org/2009/02/ws-mex/Dialects/ws-mex </td><td> mex:Metadata [Defined in this specification] </td></tr><tr><td> http://www.w3.org/2009/02/ws-mex/Dialects/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.
@@ -605,9 +608,9 @@
contains information whose format and content depend on the dialect.
</p><p>
The representation of a metadata resource MAY also be
- any other document format (e.g. <a href="#Schema1">[XML Schema: Structures]</a>,
- <a href="#Schema2">[XML Schema: Datatypes]</a>, <a href="#WSDL11">[WSDL 1.1]</a>,
- <a href="#WS-Policy">[WS-Policy]</a>) for which a dialect value is defined.
+ any other document format (e.g. <a href="#XMLSchema1">[XMLSchema - Part 1]</a>,
+ <a href="#XMLSchema2">[XMLSchema - Part 2]</a>, <a href="#WSDL11">[WSDL11]</a>,
+ <a href="#wspolicy">[WS-Policy]</a>) for which a dialect value is defined.
</p></div><div class="div2">
<h3><a name="Get-Metadata" id="Get-Metadata"/>6.2 Get Metadata</h3><p>
A requester MAY send a GetMetadata request message to an endpoint to
@@ -872,7 +875,7 @@
<h2><a name="Security" id="Security"/>9 Security Considerations</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,
+ <a href="#WSSecurity">[WS-Security]</a>. In order to properly secure messages,
the body and all relevant headers need to be included in the
signature. Specifically, any standard messaging headers, such as
those from WS-Addressing
@@ -884,8 +887,8 @@
technologies might be adequate for integrity and confidentiality.
However, for high-frequency events, it might be more performant to
establish a security context for the events using the mechanisms
- described in <a href="#WS-Trust">[WS-Trust]</a> and
- <a href="#WS-SecureConversation">[WS-SecureConversation]</a>. Note that if
+ described in <a href="#WSTrust">[WS-Trust]</a> and
+ <a href="#WSSecureConversation">[WS-SecureConversation]</a>. Note that if
a shared secret is used it is RECOMMENDED that derived keys be used
to strengthen the secret as described in WS-SecureConversation.
</p><p>
@@ -903,7 +906,7 @@
of the sender.
</p><p>
Additionally, some metadata formats, such as policies
- <a href="#WS-Policy">[WS-Policy]</a>, can have embedded security
+ <a href="#wspolicy">[WS-Policy]</a>, can have embedded security
semantics. These SHOULD be verified using the same considerations
outlined in this section.
</p><p>
@@ -916,8 +919,8 @@
encrypting sensitive data using WS-Security.
</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>)
+ - see <a href="#wspolicy">[WS-Policy]</a> and
+ <a href="#WSSecurityPolicy">[WS-SecurityPolicy]</a>)
</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
@@ -969,74 +972,99 @@
Wu Chou (Avaya Communications),
Yves Lafon (W3C).
</p></div><div class="div1">
-<h2><a name="References" id="References"/>12 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>
- Key words for use in RFCs to Indicate Requirement Levels
- </cite></a>
- , S. Bradner, Harvard University, March 1997.
- Available at <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>.</dd><dt class="label"><a name="RFC3986" id="RFC3986"/>RFC 3986</dt><dd><a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>
- Uniform Resource Identifier (URI): Generic Syntax
- </cite></a>
- , T. Berners-Lee, W3C/MIT, January 2005.
- Available at <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>.</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>
- Simple Object Access Protocol (SOAP) 1.1
- </cite></a>
- , D. Box, et al, May 2000.
- Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</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>
- "SOAP Version 1.2 Part 1: Messaging Framework
- </cite></a>
- , M. Gudgin, et al, June 2003.
- Available at <a href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/">http://www.w3.org/TR/2003/REC-soap12-part1-20030624/</a>.</dd><dt class="label"><a name="AddrCore" id="AddrCore"/>WS-Addressing</dt><dd><a href="http://www.w3.org/2005/08/addressing/"><cite>
- W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
+<h2><a name="References" id="References"/>12 References</h2><div class="div2">
+<h3><a name="iddiv2_1_1331" id="iddiv2_1_1331"/>12.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.
+ Internet Engineering Task Force, March 1997.
+ Available at <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>.</dd><dt class="label"><a name="RFC3986" id="RFC3986"/>RFC 3986</dt><dd><a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>
+ Uniform Resource Identifier (URI): Generic Syntax
+ </cite></a>
+ , T. Berners-Lee, R. Fields and L. Masinter, Authors.
+ Network Working Group, January 2005.
+ Available at <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>.</dd><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
+ W3C Note, "Simple Object Access Protocol (SOAP) 1.1"
+ </cite></a>
+ , D. Box, et al, Editors.
+ World Wide Web Consortium (W3C), 8 May 2000.
+ Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP121" id="SOAP121"/>SOAP12</dt><dd><a href="http://www.w3.org/TR/soap12-part1/"><cite>
+ W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
+ </cite></a>
+ , M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielson,
+ Editors.
+ World Wide Web Consortium (W3C), 27 April 2007.
+ Available at <a href="http://www.w3.org/TR/soap12-part1/">http://www.w3.org/TR/soap12-part1/</a>.</dd><dt class="label"><a name="AddrCore" id="AddrCore"/>WS-Addressing</dt><dd><a href="http://www.w3.org/TR/ws-addr-core"><cite>
+ W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
+ </cite></a>
+ , M. Gudgin, M. Hadley, T. Rogers, Editors.
+ World Wide Web Consortium (W3C), 9 May 2006.
+ Available at <a href="http://www.w3.org/TR/ws-addr-core">http://www.w3.org/TR/ws-addr-core</a>.</dd><dt class="label"><a name="wspolicy" id="wspolicy"/>WS-Policy</dt><dd><a href="http://www.w3.org/TR/ws-policy/"><cite>
+ W3C Recommendation, "Web Services Policy (WS-Policy) 1.5 - Framework"
+ </cite></a>
+ , A. Vedamuthu, et al., Editors.
+ World Wide Web Consortium (W3C), 4 September 2007.
+ Available at <a href="http://www.w3.org/TR/ws-policy/">http://www.w3.org/TR/ws-policy/</a>.</dd><dt class="label"><a name="WS-PolicyAttachment" id="WS-PolicyAttachment"/>WS-PolicyAttachment</dt><dd><a href="http://www.w3.org/TR/ws-policy-attach/"><cite>
+ W3C Recommendation, "Web Services Policy (WS-Policy) 1.5 - Attachment"
</cite></a>
- , May 2006.
- Available at <a href="http://www.w3.org/2005/08/addressing/">http://www.w3.org/2005/08/addressing/</a>.</dd><dt class="label"><a name="WS-Policy" id="WS-Policy"/>WS-Policy</dt><dd><a href="http://www.w3.org/TR/ws-policy/"><cite>
- W3C Recommendation, "Web Services Policy 1.5 - Framework"
- </cite></a>
- , September 2007.
- Available at <a href="http://www.w3.org/TR/ws-policy/">http://www.w3.org/TR/ws-policy/</a>.</dd><dt class="label"><a name="WS-PolicyAttachment" id="WS-PolicyAttachment"/>WS-PolicyAttachment</dt><dd><a href="http://www.w3.org/TR/ws-policy-attach/"><cite>
- W3C Recommendation, "Web Services Policy 1.5 - Attachment"
- </cite></a>
- , September 2007.
- Available at <a href="http://www.w3.org/TR/ws-policy-attach/">http://www.w3.org/TR/ws-policy-attach/</a>.</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>
- Web Services Secure Conversation Language (WS-SecureConversation)
- </cite></a>
- , S. Anderson, et al, February 2005.
- Available at <a href="http://www.oasis-open.org/committees/download.php/17364.">http://www.oasis-open.org/committees/download.php/17364.</a>.</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>
- Web Services Security: SOAP Message Security 1.0 (WS-Security 2004)
- </cite></a>
- , A. Nadalin, et al, March 2004.
- Available at <a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf">http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf</a>.</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>
- Web Services Security Policy Language (WS-SecurityPolicy)
- </cite></a>
- , G. Della-Libera, et al, July 2005.
- Available at <a href="http://www.oasis-open.org/committees/download.php/16569/">http://www.oasis-open.org/committees/download.php/16569/</a>.</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>
- Web Services Transfer (WS-Transfer)
- </cite></a>
- , J. Alexander, et al, September 2004.
- Available at <a href="http://www.w3.org/Submission/2006/SUBM-WS-Transfer-20060315/">http://www.w3.org/Submission/2006/SUBM-WS-Transfer-20060315/</a>.</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>
- Web Services Trust Language (WS-Trust)
- </cite></a>
- , S. Anderson, et al, February 2005.
- Available at <a href="http://www.oasis-open.org/committees/download.php/17364">http://www.oasis-open.org/committees/download.php/17364</a>.</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>
- Web Services Description Language (WSDL) 1.1
- </cite></a>
- , E. Christensen, et al, March 2001
- Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"/>XML Infoset</dt><dd><a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/"><cite>
- XML Information Set
- </cite></a>
- , J. Cowan, et al, February 2004.
- Available at <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/">http://www.w3.org/TR/2004/REC-xml-infoset-20040204/</a>.</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>
- XML Schema Part 1: Structures
- </cite></a>
- , H. Thompson, et al, October 2004.
- Available at <a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/</a>.</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>
- XML Schema Part 2: Datatypes
- </cite></a>
- , P. Biron, et al, October 2004.
- Available at <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/</a>.</dd></dl></div></div><div class="back"><div class="div1">
+ , A. Vedamuthu, et al., Editors.
+ World Wide Web Consortium (W3C), 4 September 2007.
+ Available at <a href="http://www.w3.org/TR/ws-policy-attach/">http://www.w3.org/TR/ws-policy-attach/</a>.</dd><dt class="label"><a name="WS-Transfer" id="WS-Transfer"/>WS-Transfer</dt><dd><a href="http://www.w3.org/TR/ws-transfer"><cite>
+ W3C Working Group Draft, "Web Services Transfer (WS-Transfer)1.1"
+ </cite></a>
+ , D. Davis, et al., Editors.
+ World Wide Web Consortium (W3C), 15 September 2009.
+ Available at <a href="http://www.w3.org/TR/ws-transfer">http://www.w3.org/TR/ws-transfer</a>.</dd><dt class="label"><a name="WSDL11" id="WSDL11"/>WSDL11</dt><dd><a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
+ W3C Note, "Web Services Description Language (WSDL) 1.1"
+ </cite></a>
+ , E. Christensen, et al., Editors.
+ World Wide Web Consortium (W3C), 15 March 2001
+ Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"/>XML Infoset</dt><dd><a href="http://www.w3.org/TR/xml-infoset"><cite>
+ W3C Recommendation, "XML Information Set (Second Edition)"
+ </cite></a>
+ , J. Cowan, R. Tobin, Editors.
+ World Wide Web Consortium (W3C), 4 February 2004.
+ Available at <a href="http://www.w3.org/TR/xml-infoset">http://www.w3.org/TR/xml-infoset</a>.</dd><dt class="label"><a name="XMLSchema1" id="XMLSchema1"/>XMLSchema - Part 1</dt><dd><a href="http://www.w3.org/TR/xmlschema-1/"><cite>
+ W3C Recommendation, "XML Schema Part 1: Structures (Second Edition)"
+ </cite></a>
+ , H. Thompson, et al., Editors.
+ World Wide Web Consortium (W3C), 28 October 2004.
+ Available at <a href="http://www.w3.org/TR/xmlschema-1/">http://www.w3.org/TR/xmlschema-1/</a>.</dd><dt class="label"><a name="XMLSchema2" id="XMLSchema2"/>XMLSchema - Part 2</dt><dd><a href="http://www.w3.org/TR/xmlschema-2/"><cite>
+ W3C Recommendation, "XML Schema Part 2: Datatypes (Second Edition)"
+ </cite></a>
+ , 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_1491" id="iddiv2_1_1491"/>12.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>
+ , A. Nadalin, et al., Editors.
+ Organization for the Advancement of Structured Information Standards
+ (OASIS), 2 February 2009.
+ Available at <a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc">http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc</a>.</dd><dt class="label"><a name="WSSecurity" id="WSSecurity"/>WS-Security</dt><dd><a href="http://docs.oasis-open.org/wss/v1.1/wss-v1.1-spec-os-SOAPMessageSecurity.pdf"><cite>
+ OASIS Standard, "Web Services Security: SOAP Message Security 1.1"
+ </cite></a>
+ , K. Lawrence, C. Kaler, Editors.
+ Organization for the Advancement of Structured Information Standards
+ (OASIS), 1 February 2006.
+ Available at <a href="http://docs.oasis-open.org/wss/v1.1/wss-v1.1-spec-os-SOAPMessageSecurity.pdf">http://docs.oasis-open.org/wss/v1.1/wss-v1.1-spec-os-SOAPMessageSecurity.pdf</a>.</dd><dt class="label"><a name="WSSecurityPolicy" id="WSSecurityPolicy"/>WS-SecurityPolicy</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/v1.3/os/ws-securitypolicy-1.3-spec-os.doc"><cite>
+ OASIS Standard, "Web Services Security Policy (WS-SecurityPolicy) 1.3,
+ Version 1.1"
+ </cite></a>
+ , K. Lawrence, C. Kaler, Editors.
+ Organization for the Advancement of Structured Information Standards
+ (OASIS), 2 February 2009.
+ Available at <a href="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/v1.3/os/ws-securitypolicy-1.3-spec-os.doc">http://docs.oasis-open.org/ws-sx/ws-securitypolicy/v1.3/os/ws-securitypolicy-1.3-spec-os.doc</a>.</dd><dt class="label"><a name="WSTrust" id="WSTrust"/>WS-Trust</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-trust/v1.4/os/ws-trust-1.4-spec-os.doc"><cite>
+ OASIS Standard, "Web Services Trust (WS-Trust) 1.4"
+ </cite></a>
+ , K. Lawrence, C. Kaler, Editors.
+ Organization for the Advancement of Structured Information Standards
+ (OASIS), 2 February 2009.
+ Available at <a href="http://docs.oasis-open.org/ws-sx/ws-trust/v1.4/os/ws-trust-1.4-spec-os.doc">http://docs.oasis-open.org/ws-sx/ws-trust/v1.4/os/ws-trust-1.4-spec-os.doc</a>.</dd></dl></div></div></div><div class="back"><div class="div1">
<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 can be
+ A normative copy of the XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>,
+ <a href="#XMLSchema2">[XMLSchema - Part 2]</a> description for this specification can 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>
A non-normative copy of the XML Schema description is listed below for
@@ -1117,7 +1145,7 @@
<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>
- A normative copy of the WSDL <a href="#WSDL11">[WSDL 1.1]</a> description for
+ A normative copy of the WSDL <a href="#WSDL11">[WSDL11]</a> description for
this specification can 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>
A non-normative copy of the WSDL description is listed below for
@@ -1187,4 +1215,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7270">7270</a></td></tr><tr><td> 2009/09/01 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6702">6702</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533">6533</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=6533">6533</a></td></tr><tr><td> 2009/09/23 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6570">6570</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Wednesday, 23 September 2009 19:48:00 UTC