- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 17 Mar 2009 22:41:53 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv30645
Modified Files:
wst.html wst.xml
Log Message:
fix a bad bib ref
Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -d -r1.18 -r1.19
--- wst.xml 12 Mar 2009 13:22:10 -0000 1.18
+++ wst.xml 17 Mar 2009 22:41:51 -0000 1.19
@@ -1514,8 +1514,8 @@
<head>XML Schema</head>
<p>
- A normative copy of the XML Schema <bibref ref='Schema1'/>,
- <bibref ref='Schema2'/> description for this specification may be
+ A normative copy of the XML Schema <bibref ref='XmlSchemaPart1'/>,
+ <bibref ref='XmlSchemaPart2'/> description for this specification may be
retrieved from the following address:
</p>
Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -d -r1.22 -r1.23
--- wst.html 16 Mar 2009 10:26:21 -0000 1.22
+++ wst.html 17 Mar 2009 22:41:51 -0000 1.23
@@ -1,6 +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" xml:lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Web Services Transfer (WS-Transfer)</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 xmlns="http://www.w3.org/1999/xhtml" lang="en"><head><title>Web Services Transfer (WS-Transfer)</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
@@ -30,42 +28,40 @@
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"></a>Web Services Transfer (WS-Transfer)</h1>
-<h2><a name="w3c-doctype" id="w3c-doctype"></a>Editor's Draft $Date$</h2><dl><dt>Latest version:</dt><dd>
- <a href="http://www.w3.org/TR/ws-transfer">http://www.w3.org/TR/ws-transfer
- </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"></a>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 Transfer (WS-Transfer)</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-transfer">http://www.w3.org/TR/ws-transfer
+ </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 describes a general SOAP-based protocol for accessing
XML representations of Web service-based resources.
</p></div><div>
-<h2><a name="status" id="status"></a>Status of this Document</h2><p><strong>This document is an editors' copy that has
+<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"></a>Table of Contents</h2><p class="toc">1 <a href="#intro">Introduction</a><br />
- 1.1 <a href="#reqs">Requirements</a><br />
-2 <a href="#Notations_and_Terminology">Terminology and Notation</a><br />
- 2.1 <a href="#terminology">Terminology</a><br />
- 2.2 <a href="#namespaces">XML Namespaces</a><br />
- 2.3 <a href="#conven">Notational Conventions</a><br />
- 2.4 <a href="#compliance">Compliance</a><br />
-3 <a href="#resourceOperations">Resource Operations</a><br />
- 3.1 <a href="#Get">Get</a><br />
- 3.2 <a href="#Put">Put</a><br />
- 3.3 <a href="#Delete">Delete</a><br />
-4 <a href="#Resource_Factory_Operations">Resource Factory Operations</a><br />
- 4.1 <a href="#Factory_Create">Create</a><br />
-5 <a href="#Faults">Faults</a><br />
- 5.1 <a href="#InvalidRepresentation">InvalidRepresentation</a><br />
-6 <a href="#Security_Considerations">Security Considerations</a><br />
-7 <a href="#acks">Acknowledgements</a><br />
-8 <a href="#refs">References</a><br />
+<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#intro">Introduction</a><br/>
+ 1.1 <a href="#reqs">Requirements</a><br/>
+2 <a href="#Notations_and_Terminology">Terminology and Notation</a><br/>
+ 2.1 <a href="#terminology">Terminology</a><br/>
+ 2.2 <a href="#namespaces">XML Namespaces</a><br/>
+ 2.3 <a href="#conven">Notational Conventions</a><br/>
+ 2.4 <a href="#compliance">Compliance</a><br/>
+3 <a href="#resourceOperations">Resource Operations</a><br/>
+ 3.1 <a href="#Get">Get</a><br/>
+ 3.2 <a href="#Put">Put</a><br/>
+ 3.3 <a href="#Delete">Delete</a><br/>
+4 <a href="#Resource_Factory_Operations">Resource Factory Operations</a><br/>
+ 4.1 <a href="#Factory_Create">Create</a><br/>
+5 <a href="#Faults">Faults</a><br/>
+ 5.1 <a href="#InvalidRepresentation">InvalidRepresentation</a><br/>
+6 <a href="#Security_Considerations">Security Considerations</a><br/>
+7 <a href="#acks">Acknowledgements</a><br/>
+8 <a href="#refs">References</a><br/>
</p>
-<h3><a name="appendices" id="appendices"></a>Appendices</h3><p class="toc">A <a href="#Appendix_I__E2_80_93_XSD">XML Schema</a><br />
-B <a href="#Appendix_II__E2_80_93_WSDL">WSDL</a><br />
-C <a href="#ChangeLog">Change Log</a><br />
-</p></div><hr /><div class="body"><div class="div1">
-<h2><a name="intro" id="intro"></a>1 Introduction</h2><p>This specification defines a mechanism for acquiring XML-based
+<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix_I__E2_80_93_XSD">XML Schema</a><br/>
+B <a href="#Appendix_II__E2_80_93_WSDL">WSDL</a><br/>
+C <a href="#ChangeLog">Change Log</a><br/>
+</p></div><hr/><div class="body"><div class="div1">
+<h2><a name="intro" id="intro"/>1 Introduction</h2><p>This specification defines a mechanism for acquiring XML-based
representations of entities using the Web service infrastructure. It defines
two types of entities:</p><ul><li><p>Resources, which are entities addressable by an endpoint reference that
provide an XML representation</p></li><li><p>Resource factories, which are Web services that can create a new
@@ -103,51 +99,29 @@
associated with the endpoint reference. When the Action URIs defined by
this specification are used, such extension specifications must also allow
the basic processing models defined herein.</p><div class="div2">
-<h3><a name="reqs" id="reqs"></a>1.1 Requirements</h3><p>This specification intends to meet the following requirements:</p><ul><li><p>Provide a SOAP-based protocol for managing resources and their
+<h3><a name="reqs" id="reqs"/>1.1 Requirements</h3><p>This specification intends to meet the following requirements:</p><ul><li><p>Provide a SOAP-based protocol for managing resources and their
representations.
</p></li><li><p>Minimize additional mechanism beyond the current Web Services
architecture.
</p></li></ul></div></div><div class="div1">
-<h2><a name="Notations_and_Terminology" id="Notations_and_Terminology"></a>2 Terminology and Notation</h2><div class="div2">
-<h3><a name="terminology" id="terminology"></a>2.1 Terminology</h3><dl><dt class="label">Resource</dt><dd><p>A Web service that is addressable by an endpoint reference as defined
+<h2><a name="Notations_and_Terminology" id="Notations_and_Terminology"/>2 Terminology and Notation</h2><div class="div2">
+<h3><a name="terminology" id="terminology"/>2.1 Terminology</h3><dl><dt class="label">Resource</dt><dd><p>A Web service that is addressable by an endpoint reference as defined
in WS-Addressing and that can be represented by an XML Infoset using
the Get and Put operations defined in this specification.</p></dd><dt class="label">Resource factory</dt><dd><p>A Web service that is capable of creating new resources using the
Create operation defined in this specification.</p></dd></dl></div><div class="div2">
-<h3><a name="namespaces" id="namespaces"></a>2.2 XML Namespaces</h3><p>
+<h3><a name="namespaces" id="namespaces"/>2.2 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-tra">http://www.w3.org/2009/02/ws-tra</a></pre></div></div><p>
- <a href="#xmlnamespaces">Table 2-1</a> lists XML namespaces that are
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-tra">http://www.w3.org/2009/02/ws-tra</a></pre></div></div><p><a href="#xmlnamespaces">Table 2-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="xmlnamespaces" id="xmlnamespaces"></a><table border="1" cellpadding="5"><caption>Table 2-1:
+ </p><a name="xmlnamespaces" id="xmlnamespaces"/><table border="1" cellpadding="5"><caption>Table 2-1:
Prefixes and XML Namespaces used in this specification.
- </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespace </th><th align="left"> Specification(s) </th></tr><tr><td> wst </td><td>
- <a href="http://www.w3.org/2009/02/ws-tra">http://www.w3.org/2009/02/ws-tra</a>
- </td><td>
+ </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespace </th><th align="left"> Specification(s) </th></tr><tr><td> wst </td><td><a href="http://www.w3.org/2009/02/ws-tra">http://www.w3.org/2009/02/ws-tra</a></td><td>
This specification
- </td></tr><tr><td> s </td><td> Either SOAP 1.1 or 1.2 </td><td> SOAP </td></tr><tr><td> s11 </td><td>
- <a href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</a>
- </td><td>
- <a href="#Soap11">[SOAP 1.1]</a>
- </td></tr><tr><td> s12 </td><td>
- <a href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</a>
- </td><td>
- <a href="#Soap12">[SOAP 1.2]</a>
- </td></tr><tr><td> wsa </td><td>
- <a href="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/08/addressing</a>
- </td><td>
- <a href="#WsAddressing">[WS-Addressing]</a>
- </td></tr><tr><td> wsdl </td><td>
- <a href="http://schemas.xmlsoap.org/wsdl/">http://schemas.xmlsoap.org/wsdl/</a>
- </td><td>
- <a href="#Wsdl11">[WSDL 1.1]</a>
- </td></tr><tr><td> xs </td><td>
- <a href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001/XMLSchema</a>
- </td><td>
- XML Schema <a href="#XmlSchemaPart1">[XML Schema, Part 1]</a>, <a href="#XmlSchemaPart2">[XML Schema, Part 2]</a>
- </td></tr></tbody></table><p>
+ </td></tr><tr><td> s </td><td> Either SOAP 1.1 or 1.2 </td><td> SOAP </td></tr><tr><td> s11 </td><td><a href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</a></td><td><a href="#Soap11">[SOAP 1.1]</a></td></tr><tr><td> s12 </td><td><a href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</a></td><td><a href="#Soap12">[SOAP 1.2]</a></td></tr><tr><td> wsa </td><td><a href="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/08/addressing</a></td><td><a href="#WsAddressing">[WS-Addressing]</a></td></tr><tr><td> wsdl </td><td><a href="http://schemas.xmlsoap.org/wsdl/">http://schemas.xmlsoap.org/wsdl/</a></td><td><a href="#Wsdl11">[WSDL 1.1]</a></td></tr><tr><td> xs </td><td><a href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001/XMLSchema</a></td><td>
+ XML Schema <a href="#XmlSchemaPart1">[XML Schema, Part 1]</a>, <a href="#XmlSchemaPart2">[XML Schema, Part 2]</a></td></tr></tbody></table><p>
The working group intends to update the value of the Web Services
Enumeration namespace URI each time a new version of this document is
published until such time that the document reaches Candidate
@@ -164,7 +138,7 @@
http://www.w3.org/2005/07/13-nsuri
</a>.
</p></div><div class="div2">
-<h3><a name="conven" id="conven"></a>2.3 Notational Conventions</h3><p>
+<h3><a name="conven" id="conven"/>2.3 Notational Conventions</h3><p>
The keywords "MUST", "MUST NOT",
"REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED",
@@ -201,7 +175,7 @@
XML namespace prefixes (see <a href="#xmlnamespaces">Table 2-1</a>) are used
to indicate the namespace of the element being defined.
</p></li></ul></div><div class="div2">
-<h3><a name="compliance" id="compliance"></a>2.4 Compliance</h3><p>An implementation is not compliant with this specification if it fails to
+<h3><a name="compliance" id="compliance"/>2.4 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 namespace identifier for this
specification (listed in <a href="#xmlnamespaces">Table 2-1</a>) within
@@ -214,12 +188,12 @@
request-response message exchange, the responses generated by the service
server MUST use the same WS-Addressing namespace binding that was used in the
request.</p></div></div><div class="div1">
-<h2><a name="resourceOperations" id="resourceOperations"></a>3 Resource Operations</h2><p>
+<h2><a name="resourceOperations" id="resourceOperations"/>3 Resource Operations</h2><p>
All messages defined by this specification MUST be sent
to a Web service that is addressable by an EPR
<a href="#WsAddressing">[WS-Addressing]</a>.
</p><div class="div2">
-<h3><a name="Get" id="Get"></a>3.1 Get</h3><p>This specification defines one Web service operation (Get) for fetching a
+<h3><a name="Get" id="Get"/>3.1 Get</h3><p>This specification defines one Web service operation (Get) for fetching a
one-time snapshot of the representation of a resource.</p><p>The Get request message MUST be of the following form:</p><div class="exampleOuter"><div class="exampleInner"><pre><s:Envelope ...>
<s:Header ...>
<wsa:Action>
@@ -235,16 +209,12 @@
</wst:Get>
</s:Body>
</s:Envelope></pre></div></div><p>The following describes additional, normative constraints on the outline
-listed above:</p><dl><dt class="label">
- <code>/s:Envelope/s:Header/wsa:Action</code>
- </dt><dd><p>
+listed above:</p><dl><dt class="label"><code>/s:Envelope/s:Header/wsa:Action</code></dt><dd><p>
This required element MUST contain the value
<code>http://www.w3.org/2009/02/ws-tra/Get</code>. If a
SOAP Action URI is also present in the underlying transport,
its value MUST convey the same value.
- </p></dd><dt class="label">
- <code>/s:Envelope/s:Body/wst:Get</code>
- </dt><dd><p>
+ </p></dd><dt class="label"><code>/s:Envelope/s:Body/wst:Get</code></dt><dd><p>
This REQUIRED element MAY contain child elements that
can be used for extensibility purposes.
</p></dd></dl><p>A Get request MUST be targeted at the resource whose representation is
@@ -280,16 +250,12 @@
</s:Envelope> </pre></div></div><p>
The following describes additional, normative constraints on the
outline listed above:
- </p><dl><dt class="label">
- <code>/s:Envelope/s:Header/wsa:Action</code>
- </dt><dd><p>
+ </p><dl><dt class="label"><code>/s:Envelope/s:Header/wsa:Action</code></dt><dd><p>
This required element MUST contain the value
http://www.w3.org/2009/02/ws-tra/GetResponse. If a SOAP
Action URI is also present in the underlying transport, its
value MUST convey the same value.
- </p></dd><dt class="label">
- <code>/s:Envelope/s:Body/wst:GetResponse</code>
- </dt><dd><p>
+ </p></dd><dt class="label"><code>/s:Envelope/s:Body/wst:GetResponse</code></dt><dd><p>
This REQUIRED element MUST contain at least one child
element - the representation of the resource. The
presence of subsequent child elements is service-specific and
@@ -359,7 +325,7 @@
<xxx:state>CA</xxx:state>
<xxx:zip>90266</xxx:zip>
</xxx:Customer></pre></div></div></div><div class="div2">
-<h3><a name="Put" id="Put"></a>3.2 Put</h3><p>This specification defines one Web service operation (Put) for updating a
+<h3><a name="Put" id="Put"/>3.2 Put</h3><p>This specification defines one Web service operation (Put) for updating a
resource by providing a replacement representation. A resource MAY accept
updates that provide different XML representations than that returned by the
resource; in such a case, the semantics of the update operation is defined by
@@ -380,16 +346,12 @@
</s:Envelope> </pre></div></div><p>
The following describes additional, normative constraints on the
outline listed above:
- </p><dl><dt class="label">
- <code>/s:Envelope/s:Header/wsa:Action</code>
- </dt><dd><p>
+ </p><dl><dt class="label"><code>/s:Envelope/s:Header/wsa:Action</code></dt><dd><p>
This required element MUST contain the value
http://www.w3.org/2009/02/ws-tra/Put. If a SOAP Action
URI is also present in the underlying transport, its value
MUST convey the same value.
- </p></dd><dt class="label">
- <code>/s:Envelope/s:Body/Put</code>
- </dt><dd><p>
+ </p></dd><dt class="label"><code>/s:Envelope/s:Body/Put</code></dt><dd><p>
This REQUIRED element MUST contain at least one child element -
the representation to be used for the update.
All other children SHOULD be ignored by the service.
@@ -433,16 +395,12 @@
<em>xs:any ?</em>
</wst:PutResponse>
</s:Body>
-</s:Envelope> </pre></div></div><dl><dt class="label">
- <code>/s:Envelope/s:Header/wsa:Action</code>
- </dt><dd><p>
+</s:Envelope> </pre></div></div><dl><dt class="label"><code>/s:Envelope/s:Header/wsa:Action</code></dt><dd><p>
This required element MUST contain the value
http://www.w3.org/2009/02/ws-tra/PutResponse. If a SOAP
Action URI is also present in the underlying transport,
its value MUST convey the same value.
- </p></dd><dt class="label">
- <code>/s:Envelope/s:Body/PutResponse</code>
- </dt><dd><p>
+ </p></dd><dt class="label"><code>/s:Envelope/s:Body/PutResponse</code></dt><dd><p>
This REQUIRED element MUST contain at least one child element
(the current representation of the resource) if the updated
representation differs from the representation sent in the
@@ -528,7 +486,7 @@
<wst:PutResponse/>
</s:Body/>
</s:Envelope> </pre></div></div></div><div class="div2">
-<h3><a name="Delete" id="Delete"></a>3.3 Delete</h3><p>This specification defines one Web service operation (Delete) for deleting
+<h3><a name="Delete" id="Delete"/>3.3 Delete</h3><p>This specification defines one Web service operation (Delete) for deleting
a resource in its entirety.</p><p>Extension specifications MAY define extensions to the Delete request,
enabled by OPTIONAL header values, which specifically control preconditions
for the Delete to succeed and which may control the nature or format of the
@@ -550,16 +508,12 @@
</wst:Delete>
</s:Body>
</s:Envelope> </pre></div></div><p>The following describes additional, normative constraints on the outline
-listed above:</p><dl><dt class="label">
- <code>/s:Envelope/s:Header/wsa:Action</code>
- </dt><dd><p>
+listed above:</p><dl><dt class="label"><code>/s:Envelope/s:Header/wsa:Action</code></dt><dd><p>
This required element MUST contain the value
<code>http://www.w3.org/2009/02/ws-tra/Delete</code>. If
a SOAP Action URI is also present in the underlying transport,
its value MUST convey the same value.
- </p></dd><dt class="label">
- <code>/s:Envelope/s:Body/wst:Delete</code>
- </dt><dd><p>
+ </p></dd><dt class="label"><code>/s:Envelope/s:Body/wst:Delete</code></dt><dd><p>
This REQUIRED element MAY contain child elements that
can be used for extensibility purposes.
</p></dd></dl><p>A Delete request MUST be targeted at the resource to be deleted as
@@ -583,16 +537,12 @@
<em>xs:any ?</em>
</wst:DeleteResponse>
</s:Body>
-</s:Envelope> </pre></div></div><dl><dt class="label">
- <code>/s:Envelope/s:Header/wsa:Action</code>
- </dt><dd><p>
+</s:Envelope> </pre></div></div><dl><dt class="label"><code>/s:Envelope/s:Header/wsa:Action</code></dt><dd><p>
This required element MUST contain the value
<code>http://www.w3.org/2009/02/ws-tra/DeleteResponse</code>.
If a SOAP Action URI is also present in the underlying
transport, its value MUST convey the same value.
- </p></dd><dt class="label">
- <code>/s:Envelope/s:Body/wst:DeleteResponse</code>
- </dt><dd><p>
+ </p></dd><dt class="label"><code>/s:Envelope/s:Body/wst:DeleteResponse</code></dt><dd><p>
This REQUIRED element MAY contain a child element that
can be used for extensibility purposes.
</p></dd></dl><p>
@@ -647,8 +597,8 @@
</wst:DeleteResponse>
</s:Body>
</s:Envelope> </pre></div></div></div></div><div class="div1">
-<h2><a name="Resource_Factory_Operations" id="Resource_Factory_Operations"></a>4 Resource Factory Operations</h2><div class="div2">
-<h3><a name="Factory_Create" id="Factory_Create"></a>4.1 Create</h3><p>This specification defines one Web service operation (Create) for creating
+<h2><a name="Resource_Factory_Operations" id="Resource_Factory_Operations"/>4 Resource Factory Operations</h2><div class="div2">
+<h3><a name="Factory_Create" id="Factory_Create"/>4.1 Create</h3><p>This specification defines one Web service operation (Create) for creating
a resource and providing its initial representation. In some cases, the
initial representation MAY constitute the representation of a logical
constructor for the resource and may thus differ structurally from the
@@ -678,16 +628,12 @@
</s:Envelope> </pre></div></div><p>
The following describes additional, normative constraints on the
outline listed above:
- </p><dl><dt class="label">
- <code>/s:Envelope/s:Header/wsa:Action</code>
- </dt><dd><p>
+ </p><dl><dt class="label"><code>/s:Envelope/s:Header/wsa:Action</code></dt><dd><p>
This required element MUST contain the value
<code>http://www.w3.org/2009/02/ws-tra/Create</code>. If
a SOAP Action URI is also present in the underlying transport,
its value MUST convey the same value.
- </p></dd><dt class="label">
- <code>/s:Envelope/s:Body/Create</code>
- </dt><dd><p>
+ </p></dd><dt class="label"><code>/s:Envelope/s:Body/Create</code></dt><dd><p>
If this REQUIRED element contains children then the first child
MUST be the literal resource representation, a representation
of the constructor for the resource, or other instructions for
@@ -725,16 +671,12 @@
<em>xs:any ?</em>
</wst:CreateResponse>
</s:Body>
-</s:Envelope></pre></div></div><dl><dt class="label">
- <code>/s:Envelope/s:Header/wsa:Action</code>
- </dt><dd><p>
+</s:Envelope></pre></div></div><dl><dt class="label"><code>/s:Envelope/s:Header/wsa:Action</code></dt><dd><p>
This required element MUST contain the value
http://www.w3.org/2009/02/ws-tra/CreateResponse. If a
SOAP Action URI is also present in the underlying transport,
its value MUST convey the same value.
- </p></dd><dt class="label">
- <code>/s:Envelope/wst:CreateResponse</code>
- </dt><dd><p>
+ </p></dd><dt class="label"><code>/s:Envelope/wst:CreateResponse</code></dt><dd><p>
This REQUIRED element MUST contain, at a minimum,
a resource reference (wst:ResourceCreated element)
to the newly created resource.
@@ -780,9 +722,7 @@
consider adding a corresponding SOAP header value in
the response to signal to the receiver that the
extension is being used.
- </p></dd><dt class="label">
- <code>/s:Envelope/wst:CreateResponse/wst:ResourceCreated</code>
- </dt><dd><p>
+ </p></dd><dt class="label"><code>/s:Envelope/wst:CreateResponse/wst:ResourceCreated</code></dt><dd><p>
This required element MUST contain a resource reference for the
newly created resource. This resource reference, represented
as an endpoint reference as defined in WS-Addressing, MUST
@@ -849,14 +789,14 @@
</wst:CreateResponse>
</s:Body>
</s:Envelope></pre></div></div></div></div><div class="div1">
-<h2><a name="Faults" id="Faults"></a>5 Faults</h2><p>All fault messages defined in this specification MUST be sent according to
+<h2><a name="Faults" id="Faults"/>5 Faults</h2><p>All fault messages defined in this specification MUST be sent according to
the rules and usage described in <a href="http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509/">WS-Addressing 1.0 SOAP Binding</a>
Section 6 for encoding SOAP 1.1 and SOAP 1.2 faults.
The <b>[action]</b> property below SHOULD be used for faults
defined in this specification:</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-tra/fault">http://www.w3.org/2009/02/ws-tra/fault</a></pre></div></div><div class="div2">
-<h3><a name="InvalidRepresentation" id="InvalidRepresentation"></a>5.1 InvalidRepresentation</h3><p>This fault is returned when an incorrect representation is sent in a
- wst:Put or wst:Create message. </p><a name="Table2" id="Table2"></a><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:InvalidRepresentation</td></tr><tr><th align="left"><b>[Reason]</b></th><td>The supplied representation is invalid</td></tr><tr><th align="left"><b>[Detail]</b></th><td>none</td></tr></tbody></table></div></div><div class="div1">
-<h2><a name="Security_Considerations" id="Security_Considerations"></a>6 Security Considerations</h2><p>It is strongly recommended that the communication between services be
+<h3><a name="InvalidRepresentation" id="InvalidRepresentation"/>5.1 InvalidRepresentation</h3><p>This fault is returned when an incorrect representation is sent in a
+ wst:Put or wst:Create message. </p><a name="Table2" id="Table2"/><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:InvalidRepresentation</td></tr><tr><th align="left"><b>[Reason]</b></th><td>The supplied representation is invalid</td></tr><tr><th align="left"><b>[Detail]</b></th><td>none</td></tr></tbody></table></div></div><div class="div1">
+<h2><a name="Security_Considerations" id="Security_Considerations"/>6 Security Considerations</h2><p>It is strongly recommended that the communication between services be
secured using the mechanisms described in <a href="#WsSec">[WS-Security]</a>.</p><p>In order to properly secure messages, the body (even if empty) and all
relevant headers need to be included in the signature. Specifically, the
WS-Addressing header blocks, WS-Security timestamp, and any header blocks
@@ -872,50 +812,41 @@
(e.g. embedded signatures and encryption) are also out-of-scope.</p><p>It is recommended that the security considerations of WS-Security also be
considered.</p><p>While a comprehensive listing of attacks is not feasible, the following
list summarizes common classes of attacks that apply to this protocol and
- identifies the mechanism(s) to prevent/mitigate the attacks.</p><ul><li><p>
- <em>Replay</em> - Messages, or portions of messages, can be
+ identifies the mechanism(s) to prevent/mitigate the attacks.</p><ul><li><p><em>Replay</em> - Messages, or portions of messages, can be
replayed in an attempt to gain access or disrupt services. Freshness
checks such as timestamps, digests, and sequences can be used to detect
duplicate messages.
- </p></li><li><p>
- <em>Invalid tokens</em> - There are a number of token attacks
+ </p></li><li><p><em>Invalid tokens</em> - There are a number of token attacks
including certificate authorities, false signatures, and PKI attacks.
Care should be taken to ensure each token is valid (usage window, digest,
signing authority, revocation, ...), and that the appropriate delegation
- policies are in compliance.</p></li><li><p>
- <em>Man-in-the-middle</em> - The message exchanges in this
+ policies are in compliance.</p></li><li><p><em>Man-in-the-middle</em> - The message exchanges in this
specification could be subject to man-in-the-middle attacks so care
should be taken to reduce possibilities here such as establishing a
secure channel and verifying that the security tokens user represent
identities authorized to speak for, or on behalf of, the desired resource
- reference.</p></li><li><p>
- <em>Message alteration</em> - Alteration is prevented by
+ reference.</p></li><li><p><em>Message alteration</em> - Alteration is prevented by
including signatures of the message information using WS-Security. Care
should be taken to review message part references to ensure they haven't
- been forged (e.g. ID duplication).</p></li><li><p>
- <em>Message disclosure</em> - Confidentiality is preserved by
- encrypting sensitive data using WS-Security.</p></li><li><p>
- <em>Key integrity</em> - Key integrity is maintained by using
+ been forged (e.g. ID duplication).</p></li><li><p><em>Message disclosure</em> - Confidentiality is preserved by
+ encrypting sensitive data using WS-Security.</p></li><li><p><em>Key integrity</em> - Key integrity is maintained by using
the strongest algorithms possible (by comparing secured policies - see
<a href="#WsPolicy">[WS-Policy]</a>
and <a href="#WsSecPolicy">[WS-SecurityPolicy]</a>
and by using derived keys (<a href="#WsSecConv">[WS-SecureConversation]</a>).
- </p></li><li><p>
- <em>Authentication</em> - Authentication is established using
+ </p></li><li><p><em>Authentication</em> - 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>
- <em>Accountability</em> - Accountability is a function of the
+ authenticated using the mechanisms described in WS-Security.</p></li><li><p><em>Accountability</em> - Accountability is a function of the
type of and string 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>
- <em>Availability</em> - All reliable messaging services are
+ environments, strong PKI signatures are required.</p></li><li><p><em>Availability</em> - All reliable messaging services are
subject to a variety of availability attacks. Replay detection is a
common attack and it is recommended that this be addressed by the
mechanisms described in WS-Security. Other attacks, such as network-level
denial of service attacks are harder to avoid and are outside the scope
of this specification. That said, care should be taken to ensure that
minimal state is saved prior to any authenticating sequences.</p></li></ul></div><div class="div1">
-<h2><a name="acks" id="acks"></a>7 Acknowledgements</h2><p>
+<h2><a name="acks" id="acks"/>7 Acknowledgements</h2><p>
This specification has been developed as a result of joint
work with many individuals and teams, including:
Ashok Malhotra (Oracle Corp.),
@@ -937,71 +868,60 @@
Wu Chou (Avaya Communications),
Yves Lafon (W3C)
</p></div><div class="div1">
-<h2><a name="refs" id="refs"></a>8 References</h2><dl><dt class="label"><a name="Rfc2119" id="Rfc2119"></a>RFC 2119</dt><dd>
- <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h2><a name="refs" id="refs"/>8 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.
- (See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a name="Soap11" id="Soap11"></a>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/TR/2000/NOTE-SOAP-20000508/"><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"></a>SOAP 1.2</dt><dd>
- <a href="http://www.w3.org/TR/soap12-part1/"><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/TR/soap12-part1/"><cite>
SOAP Version 1.2 Part 1: Messaging Framework
</cite></a>
, M. Gudgin, et al, June 2003.
- (See http://www.w3.org/TR/soap12-part1/.)</dd><dt class="label"><a name="WsAddressing" id="WsAddressing"></a>WS-Addressing</dt><dd>
- <a href="http://www.w3.org/2005/08/addressing/"><cite>
+ (See http://www.w3.org/TR/soap12-part1/.)</dd><dt class="label"><a name="WsAddressing" id="WsAddressing"/>WS-Addressing</dt><dd><a href="http://www.w3.org/2005/08/addressing/"><cite>
W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
</cite></a>
, May 2006.
- (See http://www.w3.org/2005/08/addressing/.)</dd><dt class="label"><a name="WsPolicy" id="WsPolicy"></a>WS-Policy</dt><dd>
- <a href="http://schemas.xmlsoap.org/ws/2004/09/policy"><cite>
+ (See http://www.w3.org/2005/08/addressing/.)</dd><dt class="label"><a name="WsPolicy" id="WsPolicy"/>WS-Policy</dt><dd><a href="http://schemas.xmlsoap.org/ws/2004/09/policy"><cite>
S. Bajaj, et al, "Web Services Policy Framework (WS-Policy),"
</cite></a>
, September 2004.
- (See http://schemas.xmlsoap.org/ws/2004/09/policy.)</dd><dt class="label"><a name="WsSecConv" id="WsSecConv"></a>WS-SecureConversation</dt><dd>
+ (See http://schemas.xmlsoap.org/ws/2004/09/policy.)</dd><dt class="label"><a name="WsSecConv" id="WsSecConv"/>WS-SecureConversation</dt><dd>
href="http://schemas.xmlsoap.org/ws/2005/02/sc/">
<cite>
Web Services Secure Conversation Language (WS-SecureConversation)
</cite>
, S. Anderson, et al, February 2005.
- </dd><dt class="label"><a name="WsSec" id="WsSec"></a>WS-Security</dt><dd>
- <a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"><cite>
+ </dd><dt class="label"><a name="WsSec" id="WsSec"/>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
</cite></a>
, OASIS standard.
- (See http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf.)</dd><dt class="label"><a name="WsSecPolicy" id="WsSecPolicy"></a>WS-SecurityPolicy</dt><dd>
- <a href="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"><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="WsSecPolicy" id="WsSecPolicy"/>WS-SecurityPolicy</dt><dd><a href="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"><cite>
G. Della-Libera, et al, "Web Services Security Policy Language (WS-SecurityPolicy), Version 1.1"
</cite></a>
, July 2005.
- (See http://schemas.xmlsoap.org/ws/2005/07/securitypolicy.)</dd><dt class="label"><a name="Wsdl11" id="Wsdl11"></a>WSDL 1.1</dt><dd>
- <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
+ (See http://schemas.xmlsoap.org/ws/2005/07/securitypolicy.)</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.
- (See http://www.w3.org/TR/2001/NOTE-wsdl-20010315.)</dd><dt class="label"><a name="XMLInfoSet" id="XMLInfoSet"></a>XML Infoset</dt><dd>
- <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/"><cite>
+ (See http://www.w3.org/TR/2001/NOTE-wsdl-20010315.)</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>
J. Cowan, et al, "XML Information Set"
</cite></a>
, February 2004.
- (See http://www.w3.org/TR/2004/REC-xml-infoset-20040204/.)</dd><dt class="label"><a name="XmlSchemaPart1" id="XmlSchemaPart1"></a>XML Schema, Part 1</dt><dd>
- <a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"><cite>
+ (See http://www.w3.org/TR/2004/REC-xml-infoset-20040204/.)</dd><dt class="label"><a name="XmlSchemaPart1" id="XmlSchemaPart1"/>XML Schema, Part 1</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.
- (See http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/.)</dd><dt class="label"><a name="XmlSchemaPart2" id="XmlSchemaPart2"></a>XML Schema, Part 2</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="XmlSchemaPart2" id="XmlSchemaPart2"/>XML Schema, Part 2</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>
XML Schema Part 2: Datatypes
</cite></a>
, James Clark, et al, November 1999.
(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_I__E2_80_93_XSD" id="Appendix_I__E2_80_93_XSD"></a>A XML Schema</h2><p>
- A normative copy of the XML Schema <a href="#">[Schema1]</a>,
- <a href="#">[Schema2]</a> description for this specification may be
+<h2><a name="Appendix_I__E2_80_93_XSD" id="Appendix_I__E2_80_93_XSD"/>A XML Schema</h2><p>
+ A normative copy of the XML Schema <a href="#XmlSchemaPart1">[XML Schema, Part 1]</a>,
+ <a href="#XmlSchemaPart2">[XML Schema, Part 2]</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-tra/transfer.xsd">http://www.w3.org/2009/02/ws-tra/transfer.xsd</a></pre></div></div><p>A non-normative copy of the XML schema is listed below for
convenience.</p><div class="exampleOuter"><div class="exampleInner"><pre><xs:schema
@@ -1098,7 +1018,7 @@
</xs:element>
</xs:schema> </pre></div></div></div><div class="div1">
-<h2><a name="Appendix_II__E2_80_93_WSDL" id="Appendix_II__E2_80_93_WSDL"></a>B WSDL</h2><p>A normative copy of the WSDL <a href="#Wsdl11">[WSDL 1.1]</a> description
+<h2><a name="Appendix_II__E2_80_93_WSDL" id="Appendix_II__E2_80_93_WSDL"/>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-tra/transfer.wsdl">http://www.w3.org/2009/02/ws-tra/transfer.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
targetNamespace="http://www.w3.org/2009/02/ws-tra"
@@ -1192,16 +1112,10 @@
</wsdl:portType>
</wsdl:definitions></pre></div></div></div><div class="div1">
-<h2><a name="ChangeLog" id="ChangeLog"></a>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=6388">6388</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/09 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6398">6398</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=6641">6641</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></tbody></table></div></div></body></html>
+<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=6388">6388</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/09 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6398">6398</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=6641">6641</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></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Tuesday, 17 March 2009 22:42:04 UTC