REC-ws-transfer-20111213 97.8 KB

Raw Blame History Permalink

<?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">
code           { font-family: monospace; }

div.constraint,
div.issue,
div.note,
div.notice     { margin-left: 2em; }

ol.enumar      { list-style-type: decimal; }
ol.enumla      { list-style-type: lower-alpha; }
ol.enumlr      { list-style-type: lower-roman; }
ol.enumua      { list-style-type: upper-alpha; }
ol.enumur      { list-style-type: upper-roman; }


div.exampleInner pre { margin-left: 1em;
                       margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
                  margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
                   border-top-width: 4px;
                   border-top-style: double;
                   border-top-color: #d3d3d3;
                   border-bottom-width: 4px;
                   border-bottom-style: double;
                   border-bottom-color: #d3d3d3;
                   padding: 4px; margin: 0em }
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/W3C-REC.css" /></head><body><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72" /></a></p>
<h1><a name="title" id="title"></a>Web Services Transfer (WS-Transfer)</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Recommendation 13 December 2011</h2><dl><dt>This version:</dt><dd>
   <a href="http://www.w3.org/TR/2011/REC-ws-transfer-20111213">http://www.w3.org/TR/2011/REC-ws-transfer-20111213
   </a>
  </dd><dt>Latest version:</dt><dd>
   <a href="http://www.w3.org/TR/ws-transfer">http://www.w3.org/TR/ws-transfer
   </a>
  </dd><dt>Previous version:</dt><dd>
   <a href="http://www.w3.org/TR/2011/PR-ws-transfer-20110927">http://www.w3.org/TR/2011/PR-ws-transfer-20110927
   </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>Please refer to the <a href="http://www.w3.org/2002/ws/ra/errata/ws-transfer-20111213-errata"><strong>errata</strong></a> for this document, which may
      include normative corrections.</p><p>See also <a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=ws-transfer"><strong>translations</strong></a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</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>
    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><em>
	    This section describes the status of this document at the time
	    of its publication. Other documents may supersede this document.
	    A list of current W3C publications and the latest revision of
	    this technical report can be found in the
	    <a href="http://www.w3.org/TR/">W3C technical reports index</a>
	    at http://www.w3.org/TR/.
	  </em></p><p>
	  This is the 13 December 2011 Recommendation of the <em>Web Services Transfer (WS-Transfer)</em> specification.
          It has been produced by the
          <a href="http://www.w3.org/2002/ws/ra/">Web
          Services Resource Access Working Group</a> (WG), which is part of the
          <a href="http://www.w3.org/2002/ws/Activity">W3C Web Services
          Activity</a>.
        </p><p>
          The public is encouraged to send comments to the Working Group's public mailing list
          <a href="mailto:public-ws-resource-access-comments@w3.org">
          public-ws-resource-access-comments@w3.org</a>
          mailing list (<a href="http://lists.w3.org/Archives/Public/public-ws-resource-access-comments/">public
          archive</a>). See <a href="http://www.w3.org/Mail/">W3C mailing list and archive usage guidelines</a>.
        </p><p>No substantive changes were made as a result of the Proposed Recommendation phase (see also <a href="diff-ws-tra.html">diff</a>, <a href="http://www.w3.org/2002/ws/ra/test/scenario.html">test scenario</a> and <a href="http://www.w3.org/2002/ws/ra/test/testResults.html">implementation report</a>).</p><p>This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.</p><p>
	  This document was produced by a group operating under the
	  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
	  February 2004 W3C Patent Policy</a>. W3C maintains a
	  <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/43088/status">public
	  list of any patent disclosures</a> made in connection with the
	  deliverables of the group; that page also includes instructions for
	  disclosing a patent. An individual who has actual knowledge of a
	  patent which the individual believes contains
	  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
	  Claim(s)</a> must disclose the information in accordance with
	  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
	  6 of the W3C Patent Policy</a>.
	</p></div><div class="toc">
<h2><a name="contents" id="contents"></a>Table of Contents</h2><p class="toc">1 <a href="#composable">Composable Architecture</a><br />
2 <a href="#intro">Introduction</a><br />
&nbsp;&nbsp;&nbsp;2.1 <a href="#reqs">Requirements</a><br />
3 <a href="#Notations_and_Terminology">Terminology and Notation</a><br />
&nbsp;&nbsp;&nbsp;3.1 <a href="#conven">Notational Conventions</a><br />
&nbsp;&nbsp;&nbsp;3.2 <a href="#extensions">Considerations on the Use of Extensibility Points</a><br />
&nbsp;&nbsp;&nbsp;3.3 <a href="#terminology">Terminology</a><br />
&nbsp;&nbsp;&nbsp;3.4 <a href="#compliance">Compliance</a><br />
&nbsp;&nbsp;&nbsp;3.5 <a href="#namespaces">XML Namespaces</a><br />
4 <a href="#resourceOperations">Resource Operations</a><br />
&nbsp;&nbsp;&nbsp;4.1 <a href="#Get">Get</a><br />
&nbsp;&nbsp;&nbsp;4.2 <a href="#Put">Put</a><br />
&nbsp;&nbsp;&nbsp;4.3 <a href="#Delete">Delete</a><br />
5 <a href="#Resource_Factory_Operations">Resource Factory Operations</a><br />
&nbsp;&nbsp;&nbsp;5.1 <a href="#Factory_Create">Create</a><br />
6 <a href="#Faults">Faults</a><br />
&nbsp;&nbsp;&nbsp;6.1 <a href="#InvalidRepresentation">InvalidRepresentation</a><br />
&nbsp;&nbsp;&nbsp;6.2 <a href="#UnknownDialect">UnknownDialect</a><br />
&nbsp;&nbsp;&nbsp;6.3 <a href="#PutDenied">PutDenied</a><br />
&nbsp;&nbsp;&nbsp;6.4 <a href="#UnknownResource">UnknownResource</a><br />
7 <a href="#Security_Considerations">Security Considerations</a><br />
&nbsp;&nbsp;&nbsp;7.1 <a href="#idp1511840">Protecting Resources</a><br />
&nbsp;&nbsp;&nbsp;7.2 <a href="#idp1513520">Protecting Resource Factories</a><br />
8 <a href="#metadata">WS-Transfer Metadata</a><br />
&nbsp;&nbsp;&nbsp;8.1 <a href="#idp1518960">TransferResource Assertion</a><br />
&nbsp;&nbsp;&nbsp;8.2 <a href="#idp1541536">TransferResourceFactory Assertion</a><br />
9 <a href="#acks">Acknowledgements</a><br />
10 <a href="#refs">References</a><br />
&nbsp;&nbsp;&nbsp;10.1 <a href="#idp1561872">Normative References</a><br />
&nbsp;&nbsp;&nbsp;10.2 <a href="#idp1609696">Informative 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="#WSDL">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"></a>1 Composable Architecture</h2><p>
    By using the XML, SOAP <a href="#SOAP11">[SOAP11]</a>,
    <a href="#SOAP12">[SOAP12]</a>, and WSDL <a href="#WSDL11">[WSDL11]</a>
    extensibility models, the Web service
    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 service specifications to provide secure, reliable,
    and/or transacted message delivery and to express Web service and
    client policy.
   </p></div><div class="div1">
<h2><a name="intro" id="intro"></a>2 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 new
      resources
     </p></li></ul><p>
    Specifically, it defines two operations for sending and receiving the
    representation of a given resource and two operations for creating and
    deleting a resource and its corresponding representation.
   </p><p>
    Note that the state maintenance of a resource is at most
    subject to the "best efforts" of the hosting server. When a client
    receives the server's acceptance of a request to create or update a
    resource, it can reasonably expect that the resource now exists at
    the confirmed location and with the confirmed representation, but this
    is not a guarantee, even in the absence of any third parties. The
    server MAY change the representation of a resource, MAY remove a
    resource entirely, or MAY bring back a resource that was deleted.
   </p><p>
    For instance, the server might store resource state information on a
    disk drive. If that drive crashes and the server recovers state
    information from a backup tape, changes that occurred after the
    backup was made will be lost.
   </p><p>
    A server might have other operational processes that change resource
    state information. For example, a server could purge resources that
    have not been accessed for some period of time.
   </p><p>
    In addition to this, there might be application or process specific
    reasons for a server to augment or transform the representation
    provided by an update or create operation. For example, the server
    might populate the optional properties of a newly created resource
    with meaningful default values.
   </p><p>
    Finally all clients need to be aware that there might be other clients
    simultaneously accessing, creating, and updating the same resources.
   </p><p>
    In essence, the confirmation by a service of having processed a
    request to create, modify, or delete a resource implies a commitment
    only at the instant that the confirmation was generated. While the
    usual case is that resources are long-lived and stable, there are no
    guarantees, and clients are advised to code defensively.
   </p><p>
    There is no requirement for uniformity in resource representations
    between the messages defined in this specification. For example, the
    representations used by Create or Put can differ from the representation
    returned by Get, depending on the semantic requirements of the service.
    Additionally, there is no requirement that the resource content is
    fixed for any given endpoint reference. The resource content can vary
    based on environmental factors, such as the security context, time
    of day, configuration, or the dynamic state of the service.
   </p><div class="div2">
<h3><a name="reqs" id="reqs"></a>2.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>3 Terminology and Notation</h2><div class="div2">
<h3><a name="conven" id="conven"></a>3.1 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
     <a href="#RFC2119">[RFC 2119]</a>.
    </p><p>
     This specification uses the following syntax to define outlines for
     messages:
    </p><ul><li><p>
       The syntax appears as an XML instance, but values in italics
       indicate data types instead of literal values.
      </p></li><li><p>
       Characters are appended to elements and attributes to indicate
       cardinality:
      </p><ul><li><p> "?" (0 or 1) </p></li><li><p> "*" (0 or more) </p></li><li><p> "+" (1 or more) </p></li></ul></li><li><p>
       The character "|" is used to indicate a choice between
       alternatives.
      </p></li><li><p>
       The characters "(" and ")" are used to
       indicate that contained items are to be treated as a group with
       respect to cardinality or choice.
      </p></li><li><p>
       The characters "[" and "]" are used to call
       out references and property names.
      </p></li><li><p>
       Ellipsis (i.e. "...") indicate points of extensibility.
      </p></li><li><p>
       XML namespace prefixes (see <a href="#xmlnamespaces">Table 3-1</a>) are used
       to indicate the namespace of the element being defined.
      </p></li></ul><p>
     In addition to Message Information Header properties
     <a href="#AddrCore">[WS-Addressing]</a>,
     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 IRI. </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:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope&gt;
  &lt;s:Header&gt;
    <b>[Headers]</b>
    &lt;wsa:Action&gt;<b>[Action]</b>&lt;/wsa:Action&gt;
    ...
  &lt;/s:Header&gt;
  &lt;s:Body&gt;<b>[Body]</b>&lt;/s:Body&gt;
&lt;/s:Envelope&gt;</pre></div></div><p>
     This specification can be used in terms of XML Information Set (Infoset)
     <a href="#XMLInfoset">[XML Infoset]</a>, even though the specification uses XML 1.0
     terminology. Valid Infoset for this specification is the one
     serializable in XML 1.0, hence the use of XML 1.0.
    </p><p>
     The term "generate" is used in relation to the various faults defined
     by this specification to imply that a fault is produced and no
     further processing SHOULD be performed. In these cases the fault
     SHOULD be transmitted. However, there might be reasons when a compliant
     implementation can choose not to transmit the fault - for example,
     security concerns - in these situations the service MAY choose
     not to transmit the fault.
    </p></div><div class="div2">
<h3><a name="extensions" id="extensions"></a>3.2 Considerations on the Use of Extensibility Points</h3><p>
     The elements defined in this specification MAY be extended at the
     points indicated by their outlines and schema. Implementations MAY
     add child elements and/or attributes at the indicated extension
     points but MUST NOT contradict the semantics of the parent and/or
     owner, respectively. If a receiver does not recognize an extension,
     the receiver SHOULD ignore that extension. Senders MAY indicate
     the presence of an extension that has to be understood through the use
     of a corresponding SOAP Header with a soap:mustUnderstand attribute
     with the value "1".
    </p><p>
     In cases where it is either desirable or necessary for the receiver
     of a request that has been extended to indicate that it has
     recognized and accepted the semantics associated with that extension,
     it is RECOMMENDED that the receiver add a corresponding extension
     to the response message.  The definition of an extension SHOULD clearly
     specify how the extension that appears in the response correlates
     with that in the corresponding request.
    </p><p>
     Extension elements and attributes MUST NOT use the Web Services
     Transfer namespace URI.
    </p></div><div class="div2">
<h3><a name="terminology" id="terminology"></a>3.3 Terminology</h3><dl><dt class="label">Resource</dt><dd><p>
        A Web service that is addressable using an endpoint reference
        and can be represented by an XML Information Set.
       </p><p>
        The resource's representation MUST be representable by either zero or
        one Document Information items.  The following Information items MUST
        NOT appear as children anywhere within the Document Information item's
        children: Processing Instruction, Unexpanded Entity Reference, Document
        Type Declaration, Unparsed Entity and Notation.  The representation
        of the resource can be in any XML version supported by the resource
        manager, however, when transmitted within a SOAP Envelope the entire
        envelope (including the representation of the resource) MUST use
        the same XML version.
       </p><p>
        The representation can be retrieved using the Get operation
        and can be manipulated using the Put and Delete operations.
       </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="compliance" id="compliance"></a>3.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="#namespaces"><b>3.5 XML Namespaces</b></a>) within SOAP
     Envelopes unless it is compliant with this specification.
    </p><p>
     Normative text within this specification takes precedence over the XML
     Schema and WSDL descriptions, which in turn take precedence over outlines,
     which in turn take precedence over examples.
    </p><p>
     All messages defined by this specification MUST conform to the
     WS-Addressing specifications and be sent to a Web service that
     is addressable by an EPR (see <a href="#AddrCore">[WS-Addressing]</a>).
    </p><p>
     Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
     MUST be performed according to <a href="#RFC3987">[RFC 3987]</a> section 5.3.1.
    </p><p>
     For any message defined by this specification, any OPTIONAL elements
     or attributes in the message MAY be used by senders of the message;
     however receivers of those messages MUST support those OPTIONAL
     elements and attributes, unless other behavior is explicitly defined
     by this specification.
    </p><p>
     Implementations are expected to support both UTF-8 and UTF-16 as
     described in XML 1.0.
    </p><p>
     Implementations of this specification MUST conform to the corrected
     version of WSDL as defined by the 'WSDL Correction' sections of WS-I
     Basic Profile 1.2 <a href="#BP12">[BP12]</a> and WS-I Basic Profile 2.0
     <a href="#BP20">[BP20]</a>.
    </p></div><div class="div2">
<h3><a name="namespaces" id="namespaces"></a>3.5 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/2011/03/ws-tra">http://www.w3.org/2011/03/ws-tra</a></pre></div></div><p>
     <a href="#xmlnamespaces">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="xmlnamespaces" id="xmlnamespaces"></a><table border="1" cellpadding="5"><caption>Table 3-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/2011/03/ws-tra">http://www.w3.org/2011/03/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">[SOAP11]</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">[SOAP12]</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="#AddrCore">[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">[WSDL11]</a>
       </td></tr><tr><td> wsp </td><td>
        <a href="http://www.w3.org/ns/ws-policy">http://www.w3.org/ns/ws-policy</a>
       </td><td> <a href="#wspolicy">[WS-Policy]</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="#XMLSchema1">[XMLSchema - Part 1]</a>, <a href="#XMLSchema2">[XMLSchema - Part 2]</a>
       </td></tr></tbody></table><p>
     The working group intends to update the value of the Web Services
     Transfer namespace URI each time a new version of this document is
     published until such time that the document reaches Candidate
     Recommendation status. Once it has reached Candidate Recommendation
     status, the working group intends to maintain the value of the
     Web Services Transfer namespace URI that was assigned in the
     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">
     http://www.w3.org/2001/tag/doc/namespaceState.html
     </a> and
     <a href="http://www.w3.org/2005/07/13-nsuri">
     http://www.w3.org/2005/07/13-nsuri
     </a>.
    </p></div></div><div class="div1">
<h2><a name="resourceOperations" id="resourceOperations"></a>4 Resource Operations</h2><div class="div2">
<h3><a name="Get" id="Get"></a>4.1 Get</h3><p>
     This specification defines one Web service operation (Get) for
     fetching a one-time snapshot of the representation of a resource.
     This operation MUST be supported by compliant WS-Transfer resources.
    </p><p>
     The Get request message MUST be of the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
  http://www.w3.org/2011/03/ws-tra/Get

<b>[Body]</b>
  &lt;wst:Get Dialect="<em>xs:anyURI</em>"? ...&gt;
    <em>xs:any</em>*
  &lt;/wst:Get&gt;</pre></div></div><p>
     The following describes additional, normative constraints on the
     outline listed above:
    </p><dl><dt class="label"> <b>[Body]</b>/wst:Get </dt><dd><p>
        This is a REQUIRED element that has no defined child element
        content.
       </p></dd><dt class="label"> <b>[Body]</b>/wst:Get@Dialect </dt><dd><p>
        When this OPTIONAL attribute is present it contains a IRI that
        refers to additional information for the service on how to
        process this element.  If the attribute is present but the
        dialect IRI is not known then the service MUST generate an
        wst:UnknownDialect fault. There is no default value for the
        attribute. If the attribute is absent, then the base
        behavior is used.
       </p></dd><dt class="label"> <b>[Body]</b>/wst:Get@Dialect="http://www.w3.org/2011/03/ws-fra" </dt><dd><p>
        The WS-Fragment <a href="#WsFrag">[WS-Fragment]</a> specification defines
        this dialect IRI. Use of this IRI indicates that the contents
        of the Get element MUST be processed as specified by the
        WS-Fragment <a href="#WsFrag">[WS-Fragment]</a> specification.
       </p></dd></dl><p>
     If the request message reaches a conformant implementation of
     WS-Transfer and the message refers to an unknown resource, then the
     implementation MUST generate a wst:UnknownResource fault.
    </p><p>
     A Get request MUST be targeted at the resource whose representation is
     desired as described in <a href="#Notations_and_Terminology"><b>3 Terminology and Notation</b></a> of
     this specification.
    </p><p>
     If the resource accepts a Get request, it MUST reply with a response
     of the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
  http://www.w3.org/2011/03/ws-tra/GetResponse

<b>[Body]</b>
  &lt;wst:GetResponse ...&gt;
    &lt;wst:Representation ...&gt;
      <em>xs:any</em>?
    &lt;/wst:Representation&gt;?
    <em>xs:any</em>*
  &lt;/wst:GetResponse&gt;</pre></div></div><p>
     The following describes additional, normative constraints on the
     outline listed above:
    </p><dl><dt class="label"> <b>[Body]</b>/wst:GetResponse/wst:Representation </dt><dd><p>
        This OPTIONAL element acts as a container for the
        full representation of
        the resource. This element MUST be present if the corresponding
        Get request did not specify a Dialect attribute. This element
        MAY have no children in cases where there is no resource
        representation.
       </p></dd></dl><p>
     Other components of the outline above are not further constrained
     by this specification.
    </p><p>
     This operation is safe; it will not result in any side effect
     imputable to the requester. This means that in case of an underlying
     protocol error that might get unnoticed, resending the same request
     can be done automatically.
    </p><p>
     The following shows a sample SOAP envelope containing a Get
     request:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope
    xmlns:s="http://www.w3.org/2003/05/soap-envelope"
    xmlns:wsa="http://www.w3.org/2005/08/addressing"
    xmlns:xxx="http://fabrikam123.example.com/resource-model" &gt;
  &lt;s:Header&gt;
    &lt;wsa:ReplyTo&gt;
      &lt;wsa:Address&gt;
        http://www.fabrikam123.example.org/pullport
      &lt;/wsa:Address&gt;
    &lt;/wsa:ReplyTo&gt;
    &lt;wsa:To&gt;http://www.example.org/repository&lt;/wsa:To&gt;
    &lt;xxx:CustomerID wsa:IsReferenceParameter="true"&gt;
      732199
    &lt;/xxx:CustomerID&gt;
    &lt;xxx:Region wsa:IsReferenceParameter="true"&gt;
      EMEA
    &lt;/xxx:Region&gt;
    &lt;wsa:Action&gt;
      http://www.w3.org/2011/03/ws-tra/Get
    &lt;/wsa:Action&gt;
    &lt;wsa:MessageID&gt;
      urn:uuid:00000000-0000-0000-C000-000000000046
    &lt;/wsa:MessageID&gt;
  &lt;/s:Header&gt;
  &lt;s:Body&gt;
    &lt;wst:Get/&gt;
  &lt;/s:Body&gt;
&lt;/s:Envelope&gt;</pre></div></div><p>
     The following shows the corresponding response message:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope
    xmlns:s="http://www.w3.org/2003/05/soap-envelope"
    xmlns:wsa="http://www.w3.org/2005/08/addressing"
    xmlns:xxx="http://fabrikam123.example.com/resource-model" &gt;
  &lt;s:Header&gt;
    &lt;wsa:To&gt;http://www.fabrikam123.example.org/pullport&lt;/wsa:To&gt;
    &lt;wsa:Action&gt;
      http://www.w3.org/2011/03/ws-tra/GetResponse
    &lt;/wsa:Action&gt;
    &lt;wsa:MessageID&gt;
      urn:uuid:0000010e-0000-0000-C000-000000000046
    &lt;/wsa:MessageID&gt;
    &lt;wsa:RelatesTo&gt;
      urn:uuid:00000000-0000-0000-C000-000000000046
    &lt;/wsa:RelatesTo&gt;
  &lt;/s:Header&gt;
  &lt;s:Body&gt;
    &lt;wst:GetResponse&gt;
      &lt;wst:Representation&gt;
        &lt;xxx:Customer&gt;
          &lt;xxx:first&gt;Roy&lt;/xxx:first&gt;&lt;xxx:last&gt;Hill&lt;/xxx:last&gt;
          &lt;xxx:address&gt;123 Main Street&lt;/xxx:address&gt;
          &lt;xxx:city&gt;Manhattan Beach&lt;/xxx:city&gt;
          &lt;xxx:state&gt;CA&lt;/xxx:state&gt;
          &lt;xxx:zip&gt;90266&lt;/xxx:zip&gt;
        &lt;/xxx:Customer&gt;
      &lt;/wst:Representation&gt;
    &lt;/wst:GetResponse&gt;
  &lt;/s:Body&gt;
&lt;/s:Envelope&gt;</pre></div></div><p>
     In this example, the representation of the resource is the following XML
     element:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>  &lt;xxx:Customer&gt;
    &lt;xxx:first&gt;Roy&lt;/xxx:first&gt;&lt;xxx:last&gt;Hill&lt;/xxx:last&gt;
    &lt;xxx:address&gt;123 Main Street&lt;/xxx:address&gt;
    &lt;xxx:city&gt;Manhattan Beach&lt;/xxx:city&gt;
    &lt;xxx:state&gt;CA&lt;/xxx:state&gt;
    &lt;xxx:zip&gt;90266&lt;/xxx:zip&gt;
  &lt;/xxx:Customer&gt;</pre></div></div></div><div class="div2">
<h3><a name="Put" id="Put"></a>4.2 Put</h3><p>
     This specification defines one Web service operation (Put) for
     updating a resource.
     This operation MAY be supported by compliant WS-Transfer resources.
     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
     the resource.
    </p><p>
     Unless otherwise specified by an extension, this operation will
     replace the entire XML representation of the
     resource with the resource representation in the Put request message,
     or if the Put request message contains instructions, update the XML
     representation based on those instructions. When this operation is
     used to replace the entire XML representation, any OPTIONAL values
     (elements or attributes) not
     specified in the Put request message MUST be set to a
     resource-specific default value.
    </p><p>
     The Put request message MUST be of the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
  http://www.w3.org/2011/03/ws-tra/Put

<b>[Body]</b>
  &lt;wst:Put Dialect="<em>xs:anyURI</em>"? ...&gt;
    &lt;wst:Representation ...&gt;
      <em>xs:any</em>?
    &lt;wst:Representation&gt;?
    <em>xs:any</em>*
  &lt;/wst:Put&gt;</pre></div></div><p>
     The following describes additional, normative constraints on the
     outline listed above:
    </p><dl><dt class="label"> <b>[Body]</b>/wst:Put@Dialect </dt><dd><p>
        When this OPTIONAL attribute is present it contains a IRI that
        refers to additional information for the service on how to
        process this element.  If the attribute is present but the
        dialect IRI is not known then the service MUST generate an
        wst:UnknownDialect fault. There is no default value for the
        attribute. If the attribute is absent, then the base
        behavior is used.
       </p></dd><dt class="label"> <b>[Body]</b>/wst:Put@Dialect="http://www.w3.org/2011/03/ws-fra" </dt><dd><p>
        The WS-Fragment <a href="#WsFrag">[WS-Fragment]</a> specification defines
        this dialect IRI. Use of this IRI indicates that the contents
        of the Put element MUST be processed as specified by the
        WS-Fragment <a href="#WsFrag">[WS-Fragment]</a> specification.
       </p></dd><dt class="label"> <b>[Body]</b>/wst:Put/wst:Representation </dt><dd><p>
        This OPTIONAL element acts as a container for the
        full representation
        of the resource. This element MUST be present if the Dialect
        attribute is absent.  This element MAY have no children. This
        case MUST be interpreted as a request to remove the
        resource's representation, not the resource itself.
       </p></dd></dl><p>
     If the request message reaches a conformant implementation of
     WS-Transfer and the message refers to an unknown resource, then the
     implementation MUST generate a wst:UnknownResource fault.
    </p><p>
     A Put request MUST be targeted at the resource whose representation is
     desired to be updated, as described in
     <a href="#Notations_and_Terminology"><b>3 Terminology and Notation</b></a> of this specification.
    </p><p>
     The replacement representation could be considered to be invalid if
     it does not conform to the schema(s) for the target resource, is
     empty and the implementation does not support empty representations, or
     otherwise violates some cardinality or type constraint.
     If an implementation that validates the presented representation
     detects that the presented representation is
     invalid for the target resource, then the implementation MUST generate
     a wst:InvalidRepresentation fault.
    </p><p>
     The replacement representation could contain within it element or
     attribute values that are different than their corresponding values in
     the current representation. Such changes could affect elements or
     attributes that, for whatever reason, the implementation does not wish
     to allow the client to change. An implementation MAY choose to ignore
     such elements or attributes. If an implementation does not ignore
     those elements or attributes, it MUST generate a wst:PutDenied fault.
     See <a href="#Faults"><b>6 Faults</b></a>.
    </p><p>
     Other components of the outline above are not
     further constrained by this specification.
    </p><p>
     A successful Put operation updates the current representation
     associated with the targeted resource. An unsuccessful Put operation
     does not affect the resource.
    </p><p>
     If the resource accepts a Put request and performs the requested
     update, it MUST reply with a response of the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
  http://www.w3.org/2011/03/ws-tra/PutResponse

<b>[Body]</b>
  &lt;wst:PutResponse ...&gt;
    &lt;wst:Representation ...&gt;
      <em>xs:any</em>?
    &lt;/wst:Representation&gt;?
    <em>xs:any</em>*
  &lt;/wst:PutResponse&gt;</pre></div></div><dl><dt class="label"> <b>[Body]</b>/wst:PutResponse/wst:Representation </dt><dd><p>
        This OPTIONAL element acts as a container for the full
        representation of the resource.  This element is intended for
        use as an optimization to save the client the overhead of
        having to perform a subsequent Get operation. A service
        MAY include this element to return the current
        representation of the resource. This element MAY have no
        children in cases where there is no resource representation.
       </p></dd></dl><p>
     Other components of the outline above are not further constrained by this
     specification.
    </p><p>
     The following shows a sample SOAP envelope containing a Put request:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope
    xmlns:s="http://www.w3.org/2003/05/soap-envelope"
    xmlns:wsa="http://www.w3.org/2005/08/addressing"
    xmlns:xxx="http://fabrikam123.example.com/resource-model" &gt;
  &lt;s:Header&gt;
    &lt;wsa:ReplyTo&gt;
      &lt;wsa:Address&gt;
        http://www.fabrikam123.example.org/sender
      &lt;/wsa:Address&gt;
    &lt;/wsa:ReplyTo&gt;
    &lt;wsa:To&gt;http://www.example.org/pushport&lt;/wsa:To&gt;
    &lt;xxx:CustomerID wsa:IsReferenceParameter="true"&gt;
      732199
    &lt;/xxx:CustomerID&gt;
    &lt;xxx:Region wsa:IsReferenceParameter="true"&gt;
      EMEA
    &lt;/xxx:Region&gt;
    &lt;wsa:Action&gt;
      http://www.w3.org/2011/03/ws-tra/Put
    &lt;/wsa:Action&gt;
    &lt;wsa:MessageID&gt;
      urn:uuid:00000000-0000-0000-C000-000000000047
    &lt;/wsa:MessageID&gt;
  &lt;/s:Header&gt;
  &lt;s:Body&gt;
    &lt;wst:Put&gt;
      &lt;wst:Representation&gt;
        &lt;xxx:Customer&gt;
          &lt;xxx:first&gt;Roy&lt;/xxx:first&gt;&lt;xxx:last&gt;Hill&lt;/xxx:last&gt;
          &lt;xxx:address&gt;321 Main Street&lt;/xxx:address&gt;
          &lt;xxx:city&gt;Manhattan Beach&lt;/xxx:city&gt;
          &lt;xxx:state&gt;CA&lt;/xxx:state&gt;
          &lt;xxx:zip&gt;90266&lt;/xxx:zip&gt;
        &lt;/xxx:Customer&gt;
      &lt;/wst:Representation&gt;
    &lt;/wst:Put&gt;
  &lt;/s:Body&gt;
&lt;/s:Envelope&gt; </pre></div></div><p>
     The following shows the corresponding response message indicating
     success:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope
    xmlns:s="http://www.w3.org/2003/05/soap-envelope"
    xmlns:wsa="http://www.w3.org/2005/08/addressing"
    xmlns:xxx="http://fabrikam123.example.com/resource-model" &gt;
  &lt;s:Header&gt;
    &lt;wsa:To&gt;http://www.fabrikam123.example.org/sender&lt;/wsa:To&gt;
    &lt;wsa:Action&gt;
      http://www.w3.org/2011/03/ws-tra/PutResponse
    &lt;/wsa:Action&gt;
    &lt;wsa:MessageID&gt;
      urn:uuid:0000010e-0000-0000-C000-000000000047
    &lt;/wsa:MessageID&gt;
    &lt;wsa:RelatesTo&gt;
      urn:uuid:00000000-0000-0000-C000-000000000047
    &lt;/wsa:RelatesTo&gt;
  &lt;/s:Header&gt;
  &lt;s:Body&gt;
    &lt;wst:PutResponse/&gt;
  &lt;/s:Body&gt;
&lt;/s:Envelope&gt; </pre></div></div></div><div class="div2">
<h3><a name="Delete" id="Delete"></a>4.3 Delete</h3><p>
     This specification defines one Web service operation (Delete) for
     deleting a resource in its entirety.
     This operation MAY be supported by compliant WS-Transfer resources.
    </p><p>
     The Delete request message MUST be of the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
  http://www.w3.org/2011/03/ws-tra/Delete

<b>[Body]</b>
  &lt;wst:Delete Dialect="<em>xs:anyURI</em>"? ...&gt;
    <em>xs:any</em>*
  &lt;/wst:Delete&gt;</pre></div></div><p>
     The following describes additional, normative constraints on the
     outline listed above:
    </p><dl><dt class="label"> <b>[Body]</b>/wst:Delete </dt><dd><p>
        This is a REQUIRED element that has no defined child element
        content.
       </p></dd><dt class="label"> <b>[Body]</b>/wst:Delete@Dialect </dt><dd><p>
        When this OPTIONAL attribute is present it contains a IRI that
        refers to additional information for the service on how to
        process this element.  If the attribute is present but the
        dialect IRI is not known then the service MUST generate an
        wst:UnknownDialect fault. There is no default value for the
        attribute. If the attribute is absent, then the base
        behavior is used.
       </p></dd></dl><p>
     If the request message reaches a conformant implementation of
     WS-Transfer and the message refers to an unknown resource, then the
     implementation MUST generate a wst:UnknownResource fault.
    </p><p>
     A Delete request MUST be targeted at the resource to be deleted as
     described in <a href="#Notations_and_Terminology"><b>3 Terminology and Notation</b></a> of this
     specification.
    </p><p>
     Other components of the outline above are not further constrained by
     this specification.
    </p><p>
     A successful Delete operation deletes the targeted resource.
    </p><p>
     If the resource accepts a Delete request, it MUST reply with a
     response of the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
  http://www.w3.org/2011/03/ws-tra/DeleteResponse

<b>[Body]</b>
  &lt;wst:DeleteResponse ...&gt;
    <em>xs:any</em>*
  &lt;/wst:DeleteResponse&gt;</pre></div></div><dl><dt class="label"> <b>[Body]</b>/wst:DeleteResponse </dt><dd><p>
        This REQUIRED element has no defined child element content.
       </p></dd></dl><p>
     Other components of the outline above are not further constrained
     by this specification.
    </p><p>
     The following shows a sample SOAP envelope containing a Delete
     request:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope
    xmlns:s="http://www.w3.org/2003/05/soap-envelope"
    xmlns:wsa="http://www.w3.org/2005/08/addressing"
    xmlns:xxx="http://fabrikam123.example.com/resource-model" &gt;
  &lt;s:Header&gt;
    &lt;wsa:ReplyTo&gt;
      &lt;wsa:Address&gt;
        http://www.fabrikam123.example.org/sender
      &lt;/wsa:Address&gt;
    &lt;/wsa:ReplyTo&gt;
    &lt;wsa:To&gt;http://www.example.org/pushport&lt;/wsa:To&gt;
    &lt;xxx:CustomerID wsa:IsReferenceParameter="true"&gt;
      732199
    &lt;/xxx:CustomerID&gt;
    &lt;xxx:Region wsa:IsReferenceParameter="true"&gt;
      EMEA
    &lt;/xxx:Region&gt;
    &lt;wsa:Action&gt;
      http://www.w3.org/2011/03/ws-tra/Delete
    &lt;/wsa:Action&gt;
    &lt;wsa:MessageID&gt;
      urn:uuid:00000000-0000-0000-C000-000000000049
    &lt;/wsa:MessageID&gt;
  &lt;/s:Header&gt;
  &lt;s:Body&gt;
    &lt;wst:Delete/&gt;
  &lt;/s:Body&gt;
&lt;/s:Envelope&gt; </pre></div></div><p>
     The following shows the corresponding response message indicating
     success:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope
    xmlns:s="http://www.w3.org/2003/05/soap-envelope"
    xmlns:wsa="http://www.w3.org/2005/08/addressing"
    xmlns:xxx="http://fabrikam123.example.com/resource-model" &gt;
  &lt;s:Header&gt;
    &lt;wsa:To&gt;http://www.fabrikam123.example.org/sender&lt;/wsa:To&gt;
    &lt;wsa:Action&gt;
      http://www.w3.org/2011/03/ws-tra/DeleteResponse
    &lt;/wsa:Action&gt;
    &lt;wsa:MessageID&gt;
      urn:uuid:0000010e-0000-0000-C000-000000000049
    &lt;/wsa:MessageID&gt;
    &lt;wsa:RelatesTo&gt;
      urn:uuid:00000000-0000-0000-C000-000000000049
    &lt;/wsa:RelatesTo&gt;
  &lt;/s:Header&gt;
  &lt;s:Body&gt;
    &lt;wst:DeleteResponse/&gt;
  &lt;/s:Body&gt;
&lt;/s:Envelope&gt; </pre></div></div></div></div><div class="div1">
<h2><a name="Resource_Factory_Operations" id="Resource_Factory_Operations"></a>5 Resource Factory Operations</h2><div class="div2">
<h3><a name="Factory_Create" id="Factory_Create"></a>5.1 Create</h3><p>
     This specification defines one Web service operation (Create) for
     creating a resource and providing its initial representation.
     This operation MAY be supported by compliant WS-Transfer resource
     factories.
     In some cases, the initial representation MAY constitute the
     representation of a logical constructor for the resource and can
     thus differ structurally from the representation returned by Get or
     the one used by Put. This is because
     the parameterization requirement for creating a resource is
     often distinct from the steady-state representation of the resource.
     Implementations SHOULD provide metadata which describes the use of
     the representation and how it relates to the resource which is
     created, but such mechanisms are beyond the scope of this
     specification. The resource factory that receives a
     Create request will allocate a new resource that is initialized
     from the presented representation. The new resource will be assigned
     a service-determined endpoint reference that is returned in the
     response message.
    </p><p>
     The Create request message MUST be of the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
  http://www.w3.org/2011/03/ws-tra/Create

<b>[Body]</b>
  &lt;wst:Create Dialect="<em>xs:anyURI</em>"? ...&gt;
    &lt;wst:Representation ...&gt;
      <em>xs:any</em>?
    &lt;/wst:Representation&gt;?
    <em>xs:any</em>*
  &lt;/wst:Create&gt;</pre></div></div><p>
     The following describes additional, normative constraints on the
     outline listed above:
    </p><dl><dt class="label"> <b>[Body]</b>/wst:Create@Dialect </dt><dd><p>
        When this OPTIONAL attribute is present it contains a IRI that
        refers to additional information for the service on how to
        process this element.  If the attribute is present but the
        dialect IRI is not known then the service MUST generate an
        wst:UnknownDialect fault. There is no default value for the
        attribute. If the attribute is absent, then the base
        behavior is used.
       </p></dd><dt class="label"> <b>[Body]</b>/wst:Create/wst:Representation </dt><dd><p>
        This OPTIONAL element acts as a container for the full
        representation of the resource.  If this element is not
        present the resource MUST be created using default values
        (equivalent to a null constructor). This element MAY have
        no children. This case MUST be interpreted as a request to create
        a new resource with
        an empty representation (equivalent to an empty constructor).
       </p></dd></dl><p>
     A Create request MUST be targeted at a resource factory capable of
     creating the desired new resource. This factory is distinct from the
     resource being created (which by definition does not exist prior to
     the successful processing of the Create request message).
    </p><p>
     The representation could be considered to be invalid if it does
     not conform to the schema(s) for the target resource, is empty and
     the implementation does not support empty representations, or
     otherwise violates some cardinality or type constraint. If an
     implementation that validates the presented representation detects
     that the presented representation is invalid for the target
     resource, then the implementation MUST generate a
     wst:InvalidRepresentation fault.
    </p><p>
     Other components of the outline above are not further constrained by
     this specification.
    </p><p>
     If the resource factory accepts a Create request, it MUST reply with
     a response of the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
  http://www.w3.org/2011/03/ws-tra/CreateResponse

<b>[Body]</b>
  &lt;wst:CreateResponse ...&gt;
    &lt;wst:ResourceCreated&gt;<em>endpoint-reference</em>&lt;/wst:ResourceCreated&gt;
    &lt;wst:Representation ...&gt;
      <em>xs:any</em>?
    &lt;/wst:Representation&gt;?
    <em>xs:any</em>*
  &lt;/wst:CreateResponse&gt;</pre></div></div><dl><dt class="label"> <b>[Body]</b>/wst:CreateResponse/wst:ResourceCreated </dt><dd><p>
        This REQUIRED element MUST be an endpoint reference for the
        newly created resource. This endpoint reference MUST
        identify the resource for future Get, Put, and Delete
        operations.
       </p></dd><dt class="label"> <b>[Body]</b>/wst:CreateResponse/wst:Representation </dt><dd><p>
        This OPTIONAL element acts as a container for the full
        representation of the resource.  This element is intended for
        use as an optimization to save the client the overhead of
        having to perform a subsequent Get operation. A service
        MAY include this element to return the current representation
        of the resource.  This element MAY have no children in cases
        where there is no resource representation.
       </p></dd></dl><p>
     Other components of the outline above are not further constrained by
     this specification.
    </p><p>
     The following shows a sample SOAP envelope containing a Create
     request:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope
    xmlns:s="http://www.w3.org/2003/05/soap-envelope"
    xmlns:wsa="http://www.w3.org/2005/08/addressing"
    xmlns:xxx="http://fabrikam123.example.com/resource-model" &gt;
  &lt;s:Header&gt;
    &lt;wsa:ReplyTo&gt;
      &lt;wsa:Address&gt;
        http://www.fabrikam123.example.org/sender
      &lt;/wsa:Address&gt;
    &lt;/wsa:ReplyTo&gt;
    &lt;wsa:To&gt;http://www.example.org/pushport/CustomerSpace&lt;/wsa:To&gt;
    &lt;wsa:Action&gt;
      http://www.w3.org/2011/03/ws-tra/Create
    &lt;/wsa:Action&gt;
    &lt;wsa:MessageID&gt;
      urn:uuid:00000000-0000-0000-C000-000000000048
    &lt;/wsa:MessageID&gt;
  &lt;/s:Header&gt;
  &lt;s:Body&gt;
    &lt;wst:Create&gt;
      &lt;wst:Representation&gt;
        &lt;xxx:Customer&gt;
          &lt;xxx:first&gt;Roy&lt;/xxx:first&gt;&lt;xxx:last&gt;Hill&lt;/xxx:last&gt;
          &lt;xxx:address&gt;123 Main Street&lt;/xxx:address&gt;
          &lt;xxx:city&gt;Manhattan Beach&lt;/xxx:city&gt;
          &lt;xxx:state&gt;CA&lt;/xxx:state&gt;
          &lt;xxx:zip&gt;90266&lt;/xxx:zip&gt;
        &lt;/xxx:Customer&gt;
      &lt;/wst:Representation&gt;
    &lt;/wst:Create&gt;
  &lt;/s:Body&gt;
&lt;/s:Envelope&gt;  </pre></div></div><p>
     The following shows the corresponding response message indicating
     success:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope
    xmlns:s="http://www.w3.org/2003/05/soap-envelope"
    xmlns:wsa="http://www.w3.org/2005/08/addressing"
    xmlns:wst="http://www.w3.org/2011/03/ws-tra"
    xmlns:xxx="http://fabrikam123.example.com/resource-model" &gt;
  &lt;s:Header&gt;
    &lt;wsa:To&gt;http://www.fabrikam123.example.org/sender&lt;/wsa:To&gt;
    &lt;wsa:Action&gt;
      http://www.w3.org/2011/03/ws-tra/CreateResponse
    &lt;/wsa:Action&gt;
    &lt;wsa:MessageID&gt;
      urn:uuid:0000010e-0000-0000-C000-000000000048
    &lt;/wsa:MessageID&gt;
    &lt;wsa:RelatesTo&gt;
      urn:uuid:00000000-0000-0000-C000-000000000048
    &lt;/wsa:RelatesTo&gt;
  &lt;/s:Header&gt;
  &lt;s:Body&gt;
    &lt;wst:CreateResponse&gt;
      &lt;wst:ResourceCreated&gt;
        &lt;wsa:Address&gt;http://www.example.org/pushport&lt;/wsa:Address&gt;
        &lt;wsa:ReferenceParameters&gt;
          &lt;xxx:CustomerID&gt;732199&lt;/xxx:CustomerID&gt;
          &lt;xxx:Region&gt;EMEA&lt;/xxx:Region&gt;
        &lt;/wsa:ReferenceParameters&gt;
      &lt;/wst:ResourceCreated&gt;
    &lt;/wst:CreateResponse&gt;
  &lt;/s:Body&gt;
&lt;/s:Envelope&gt;</pre></div></div></div></div><div class="div1">
<h2><a name="Faults" id="Faults"></a>6 Faults</h2><p>
    All fault messages defined in this specification MUST be sent
    according to the rules and usage described in
    <a href="#WSABinding">[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 MUST be used for faults
    defined in this specification:
   </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2011/03/ws-tra/fault">http://www.w3.org/2011/03/ws-tra/fault</a></pre></div></div><p>
    The definitions of faults in this section use the following properties:
   </p><p>
    <b>[Code]</b> The fault code.<br />
    <b>[Subcode]</b> The fault subcode.<br />
    <b>[Reason]</b> The English language reason element.<br />
    <b>[Detail]</b> The detail element. If absent, no detail element
    is defined for the fault.<br />
   </p><p>The properties above bind to a SOAP 1.2 fault as follows:</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s12:Envelope&gt;
  &lt;s12:Header&gt;
    &lt;wsa:Action&gt; <b>[Action]</b> &lt;/wsa:Action&gt;
    &lt;!-- Headers elided for brevity. --&gt;
  &lt;/s12:Header&gt;
  &lt;s12:Body&gt;
    &lt;s12:Fault&gt;
      &lt;s12:Code&gt;
        &lt;s12:Value&gt;<b>[Code]</b>&lt;/s12:Value&gt;
        &lt;s12:Subcode&gt;
          &lt;s12:Value&gt;<b>[Subcode]</b>&lt;/s12:Value&gt;
        &lt;/s12:Subcode&gt;
      &lt;/s12:Code&gt;
      &lt;s12:Reason&gt;
        &lt;s12:Text xml:lang="en"&gt;<b>[Reason]</b>&lt;/s12:Text&gt;
      &lt;/s12:Reason&gt;
      &lt;s12:Detail&gt;
        <b>[Detail]</b>
        ...
      &lt;/s12:Detail&gt;
    &lt;/s12:Fault&gt;
  &lt;/s12:Body&gt;
&lt;/s12:Envelope&gt;</pre></div></div><p>The properties bind to a SOAP 1.1 fault as follows:</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s11:Envelope&gt;
  &lt;s12:Header&gt;
    &lt;wsa:Action&gt; <b>[Action]</b> &lt;/wsa:Action&gt;
    &lt;!-- Headers elided for brevity. --&gt;
  &lt;/s12:Header&gt;
  &lt;s11:Body&gt;
    &lt;s11:Fault&gt;
      &lt;faultcode&gt;<b>[Subcode]</b>&lt;/faultcode&gt;
      &lt;faultstring xml:lang="en"&gt;<b>[Reason]</b>&lt;/faultstring&gt;
      &lt;detail&gt;
        <b>[Detail]</b>
        ...
      &lt;/detail&gt;
    &lt;/s11:Fault&gt;
  &lt;/s11:Body&gt;
&lt;/s11:Envelope&gt;</pre></div></div><div class="div2">
<h3><a name="InvalidRepresentation" id="InvalidRepresentation"></a>6.1 InvalidRepresentation</h3><p>
     This fault MUST be generated when an incorrect representation is
     sent in a wst:Put or wst:Create message.
    </p><table border="1"><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 class="div2">
<h3><a name="UnknownDialect" id="UnknownDialect"></a>6.2 UnknownDialect</h3><p>
     This fault MUST be generated when a service detects an unknown
     Dialect IRI in a request message.
    </p><table border="1"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:UnknownDialect</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
        The specified Dialect IRI is not known.
       </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The unknown IRI if specified</em></td></tr></tbody></table></div><div class="div2">
<h3><a name="PutDenied" id="PutDenied"></a>6.3 PutDenied</h3><p>
     This fault MUST be generated when a Put request message attempts
     to modify a portion of a resource but is not allowed to do so.
    </p><table border="1"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:UpdateDenied</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
       One or more elements or attributes cannot be updated.
      </td></tr><tr><th align="left"><b>[Detail]</b></th><td>
       <em>An OPTIONAL list of the QNames of the elements or
       attributes that are not allowed to be updated.</em></td></tr></tbody></table></div><div class="div2">
<h3><a name="UnknownResource" id="UnknownResource"></a>6.4 UnknownResource</h3><p>
     This fault MUST be generated when a request specifies a resource
     that is not known.
    </p><table border="1"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:UnknownResource</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
        The resource is not known.
       </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>none</em></td></tr></tbody></table></div></div><div class="div1">
<h2><a name="Security_Considerations" id="Security_Considerations"></a>7 Security Considerations</h2><p>
    This specification considers two sets of security requirements, those
    of the applications that use the WS-Transfer protocol and those of
    the protocol itself.
   </p><p>
    This specification makes no assumptions about the security requirements
    of the applications that use WS-Transfer. However, once those
    requirements have been satisfied within a given operational context,
    the addition of WS-Transfer to this operational context can not
    undermine the fulfillment of those requirements; the use of
    WS-Transfer SHOULD NOT create additional attack vectors within
    an otherwise secure system.
   </p><p>
    The material below is not  a "check list". There are many other
    security concerns that need to be considered when implementing or
    using this protocol. Implementers and users of this protocol are urged
    to perform a security analysis to determine their particular threat
    profile and the appropriate responses to those threats.
   </p><div class="div2">
<h3><a name="idp1511840" id="idp1511840"></a>7.1 Protecting Resources</h3><p>
     Both resources and the information that makes up their representation
     might be sensitive. In these cases, it is advisable for resource
     managers to authenticate and authorize clients attempting Get, Put,
     or Delete operations. To protect representations sent over a network,
     the wst:Get, wst:GetResponse, wst:Put, and wst:PutResponse messages
     ought to have the appropriate authenticity, integrity, and
     confidentiality measures applied.
    </p></div><div class="div2">
<h3><a name="idp1513520" id="idp1513520"></a>7.2 Protecting Resource Factories</h3><p>
     In cases where resources and/or the information that makes up their
     representation are sensitive so, too, are the services that create
     these resources. In such cases it is advisable for resource factories
     to authenticate and authorize clients attempting Create operations.
     To protect representations sent over a network, wst:CreateResponse
     messages that include representations ought to have the appropriate
     authenticity, integrity, and confidentiality measures applied.
    </p></div></div><div class="div1">
<h2><a name="metadata" id="metadata"></a>8 WS-Transfer Metadata</h2><p>
    An endpoint MAY indicate its support of WS-Transfer, or its features,
    by including the WS-Transfer TransferResource or TransferResourceFactory
    Policy assertions within its WSDL. By
    doing so the endpoint is indicating that the corresponding WS-Transfer
    operations are supported by that endpoint even though they are implicit
    and do not explicitly appear in its WSDL
    (i.e. the WS-Transfer operations do not appear in the WSDL that MAY be
    retrievable by using a WS-MetadataExchange GetWSDL to that endpoint).
   </p><p>
    The WS-Transfer WSDL containing the operations indicated by the
    TransferResource or TransferResourceFactory assertions MAY be exposed
    by including the WSDL as a child of the appropriate Policy assertion or
    by including a reference to it using the mex:Location or mex:Reference
    element (as described in
    WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a> Section 9).
   </p><p>
    This WS-Transfer WSDL can be annotated to indicate any endpoint
    specific metadata that might be needed by clients interacting with
    the WS-Transfer operations.
    For example, the WSDL might have policy assertions
    that indicate a particular security mechanism used to protect
    the WS-Transfer operations supported by this endpoint.
   </p><div class="div2">
<h3><a name="idp1518960" id="idp1518960"></a>8.1 TransferResource Assertion</h3><p>
     Services indicate support for the
     WS-Transfer's definition of a Transfer Resource
     through the use of the Web Services
     Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
     Attachment <a href="#wspolicyattach">[WS-Policy Attachment]</a> specifications.
    </p><p>
     This specification defines a policy assertion (wst:TransferResource).
     The normative outline of this assertion is:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;wst:TransferResource ...&gt;
  &lt;wst:PutOperationSupported .../&gt; ?
  &lt;wst:DeleteOperationSupported .../&gt; ?
  &lt;wst:FaultOnPutDenied .../&gt; ?
  &lt;wst:Dialect URI='<em>xs:anyURI</em> ...&gt;
    <em>xs:any</em>*
  &lt;/wst:Dialect&gt; *
  &lt;wst:Resource ...&gt; <em>xs:QName</em> &lt;/wst:Resource&gt; ?
  <em>xs:any</em>*
&lt;/wst:TransferResource&gt;</pre></div></div><p>
     The following describes additional, normative constraints on the
     outline listed above:
    </p><dl><dt class="label"> /wst:TransferResource </dt><dd><p>
         This policy assertion has Endpoint Policy Subject. When present in a
         policy alternative, it indicates that the subject is a Transfer
         resource
         and the WS-Transfer protocol MUST
         be used when communicating with this endpoint.

         Unless
         support for OPTIONAL operations is explicitly indicated by either
         the PutOperationSupported or DeleteOperationSupported parameters only
         the Get operation is supported.
        </p></dd><dt class="label"> /wst:TransferResource/wst:PutOperationSupported </dt><dd><p>
         When present, this OPTIONAL parameter indicates that the Put
         operation is supported by this endpoint.
        </p></dd><dt class="label"> /wst:TransferResource/wst:DeleteOperationSupported </dt><dd><p>
         When present, this OPTIONAL parameter indicates that the Delete
         operation is supported by this endpoint.
        </p></dd><dt class="label"> /wst:TransferResource/wst:FaultOnPutDenied </dt><dd><p>
         When present, this OPTIONAL parameter indicates that attempts to
         change portions of the representation that are read-only will
         generate a wst:PutDenied fault.  If this parameter is not present,
         attempts to modify read-only portions of the resource representation
         will be ignored without any fault being generated.
        </p></dd><dt class="label"> /wst:TransferResource/wst:Dialect </dt><dd><p>
         When present, this OPTIONAL parameter indicates support for the
         specified Dialect IRI.
        </p></dd><dt class="label"> /wst:TransferResource/wst:Dialect/xs:any </dt><dd><p>
         This extensibility point allows for additional Dialect specific
         metadata to be included within the policy assertion. Any metadata
         that appears is scoped to the use of the specified Dialect URI.
        </p></dd><dt class="label"> /wst:TransferResource/wst:Resource </dt><dd><p>
         When present, this OPTIONAL parameter provides the QName referencing
         the Global Element Declaration (GED) or type of this resource.  This
         QName can be used in order to retrieve the schema of the resource.
        </p><p>
         If an endpoint uses this parameter then it MUST only accept and
         transmit XML representations of the resource that adhere to the
         scheme referenced by this QName.
        </p></dd><dt class="label"> /wst:TransferResource/xs:any </dt><dd><p>
         This extensibility point allows for additional WS-Transfer
         specific metadata to be included within the policy assertion -
         e.g. WS-Transfer WSDL, or nested policy assertions related to the
         WS-Transfer message exchanges. Any metadata that appears is scoped
         to the operations and features of the WS-Transfer specification.
        </p></dd></dl></div><div class="div2">
<h3><a name="idp1541536" id="idp1541536"></a>8.2 TransferResourceFactory Assertion</h3><p>
     Services indicate support for
     WS-Transfer's definition of a Transfer Resource Factory
     through the use of the Web Services
     Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
     Attachment <a href="#wspolicyattach">[WS-Policy Attachment]</a> specifications.
    </p><p>
     This specification defines a policy assertion
     (wst:TransferResourceFactory).
     The normative outline of this assertion is:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;wst:TransferResourceFactory ...&gt;
  &lt;wst:Resource ...&gt; <em>xs:QName</em> &lt;/wst:Resource&gt; *
  &lt;wst:Dialect URI="<em>xs:anyURI</em>" ...&gt;
    <em>xs:any</em>*
  &lt;/wst:Dialect&gt; *
  <em>xs:any</em>*
&lt;/wst:TransferResourceFactory&gt;</pre></div></div><p>
     The following describes additional, normative constraints on the
     outline listed above:
    </p><dl><dt class="label"> /wst:TransferResourceFactory </dt><dd><p>
         This policy assertion has Endpoint Policy Subject. When present in a
         policy alternative, it indicates that the subject is a resource
         factory
         and the WS-Transfer protocol MUST
         be used when communicating with this endpoint.
        </p></dd><dt class="label"> /wst:TransferResourceFactory/wst:Resource </dt><dd><p>
         When present, this repeating OPTIONAL parameter indicates the QName
         referencing the GED of one type of resource representation
         supported by this factory.
        </p><p>
         If an endpoint uses this parameter then it MUST only accept and
         transmit XML representations of the resource that adhere to the
         scheme referenced by one of these QNames.
        </p></dd><dt class="label"> /wst:TransferResourceFactory/wst:Dialect </dt><dd><p>
         When present, this OPTIONAL parameter indicates support for the
         specified Dialect IRI.
        </p></dd><dt class="label"> /wst:TransferResourceFactory/wst:Dialect/xs:any </dt><dd><p>
         This extensibility point allows for additional Dialect specific
         metadata to be included within the policy assertion. Any metadata
         that appears is scoped to the use of the specified Dialect URI.
        </p></dd><dt class="label"> /wst:TransferResourceFactory/xs:any </dt><dd><p>
         This extensibility point allows for additional WS-Transfer
         specific metadata to be included within the policy assertion -
         e.g. WS-Transfer WSDL, or nested policy assertions related to the
         WS-Transfer message exchanges. Any metadata that appears is scoped
         to the operations and features of the WS-Transfer specification.
        </p></dd></dl></div></div><div class="div1">
<h2><a name="acks" id="acks"></a>9 Acknowledgements</h2><p>
     This specification has been developed as a result of joint
     work with many individuals and teams, including:
      Alessio Soldano (Red Hat),
      Ashok Malhotra (Oracle Corp.),
      Asir Vedamuthu (Microsoft Corp.),
      Bob Freund (Hitachi, Ltd.),
      Bob Natale (MITRE Corp.),
      David Snelling (Fujitsu, Ltd.),
      Doug Davis (IBM),
      Fred Maciel (Hitachi, Ltd.),
      Geoff Bullen (Microsoft Corp.),
      Gilbert Pilz (Oracle Corp.),
      Greg Carpenter (Microsoft Corp.),
      Jeff Mischkinsky (Oracle Corp.),
      Katy Warr (IBM),
      Li Li (Avaya Communications),
      Mark Little (Red Hat),
      Martin Chapman (Oracle Corp.),
      Paul Fremantle (WSO2),
      Paul Nolan (IBM),
      Prasad Yendluri (Software AG),
      Ram Jeyaraman (Microsoft Corp.),
      Sreedhara Narayanaswamy (CA),
      Sumeet Vij (Software AG),
      Tom Rutt (Fujitsu, Ltd.),
      Vikas Varma (Software AG),
      Wu Chou (Avaya Communications),
      Yves Lafon (W3C/ERCIM).
   </p></div><div class="div1">
<h2><a name="refs" id="refs"></a>10 References</h2><div class="div2">
<h3><a name="idp1561872" id="idp1561872"></a>10.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"></a>BP12</dt><dd>
        <a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
         WS-I Profile, Basic Profile Version 1.2
        </cite></a>
        , R. Chumbley, et al, Editors.
        Web Services Interoperability Organization (WS-I), 9 November 2010.
      Available at <a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html</a>.</dd><dt class="label"><a name="BP20" id="BP20"></a>BP20</dt><dd>
        <a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html"><cite>
         WS-I Profile, Basic Profile Version 2.0
        </cite></a>
        , R. Chumbley, et al, Editors.
        Web Services Interoperability Organization (WS-I), 9 November 2010.
      Available at <a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html</a>.</dd><dt class="label"><a name="RFC2119" id="RFC2119"></a>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="RFC3987" id="RFC3987"></a>RFC 3987</dt><dd>
       <a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>
        Internationalized Resource Identifiers (IRIs)
       </cite></a>
       , M. Duerst and M. Suignard, Authors.
       Internet Engineering Task Force, January 2005.
      Available at <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>.</dd><dt class="label"><a name="SOAP11" id="SOAP11"></a>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="SOAP12" id="SOAP12"></a>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"></a>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="WSABinding" id="WSABinding"></a>WS-Addressing 1.0 SOAP Binding</dt><dd>
       <a href="http://www.w3.org/TR/ws-addr-soap"><cite>
        W3C Recommendation, "Web Services Addressing 1.0 - SOAP Binding"
       </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-soap">http://www.w3.org/TR/ws-addr-soap</a>.</dd><dt class="label"><a name="wspolicy" id="wspolicy"></a>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="wspolicyattach" id="wspolicyattach"></a>WS-Policy Attachment</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>
       , 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="WSDL11" id="WSDL11"></a>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"></a>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"></a>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"></a>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="idp1609696" id="idp1609696"></a>10.2 Informative References</h3><dl><dt class="label"><a name="WsFrag" id="WsFrag"></a>WS-Fragment</dt><dd>
      <a href="http://www.w3.org/TR/ws-fragment"><cite>
       W3C Working Group Draft, "Web Services Fragment (WS-Fragment) 1.0"
      </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-fragment">http://www.w3.org/TR/ws-fragment</a>.</dd><dt class="label"><a name="MEX" id="MEX"></a>WS-MetadataExchange</dt><dd>
       <a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
        W3C Working Group Draft, "Web Services Metadata Exchange
          (WS-MetadataExchange) 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-metadata-exchange">http://www.w3.org/TR/ws-metadata-exchange</a>.</dd></dl></div></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="#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/2011/03/ws-tra/transfer.xsd">http://www.w3.org/2011/03/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>&lt;xs:schema
  targetNamespace='http://www.w3.org/2011/03/ws-tra'
  xmlns:tns='http://www.w3.org/2011/03/ws-tra'
  xmlns:xs='http://www.w3.org/2001/XMLSchema'
  xmlns:wsa='http://www.w3.org/2005/08/addressing'
  elementFormDefault='qualified'
  blockDefault='#all' &gt;

  &lt;xs:import
    namespace='http://www.w3.org/2005/08/addressing'
    schemaLocation='http://www.w3.org/2006/03/addressing/ws-addr.xsd' /&gt;

  &lt;xs:complexType name='Representation'&gt;
    &lt;xs:sequence&gt;
      &lt;xs:any minOccurs='0' processContents='lax'/&gt;
    &lt;/xs:sequence&gt;
    &lt;xs:anyAttribute namespace='##other' processContents='lax'/&gt;
  &lt;/xs:complexType&gt;

  &lt;xs:element name='Get'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:any minOccurs='0' maxOccurs='unbounded' namespace='##other' processContents='lax' /&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:attribute name='Dialect' type='xs:anyURI' use='optional' /&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

  &lt;xs:element name='GetResponse'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:element name='Representation' type='tns:Representation' minOccurs='0'/&gt;
        &lt;xs:any minOccurs='1' maxOccurs='unbounded' namespace='##other' processContents='lax' /&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

  &lt;xs:element name='Put'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:element name='Representation' type='tns:Representation' minOccurs='0'/&gt;
        &lt;xs:any minOccurs='1' maxOccurs='unbounded' namespace='##other' processContents='lax' /&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:attribute name='Dialect' type='xs:anyURI' use='optional' /&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

  &lt;xs:element name='PutResponse'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:element name='Representation' type='tns:Representation' minOccurs='0'/&gt;
        &lt;xs:any minOccurs='1' namespace='##other' processContents='lax' /&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

  &lt;xs:element name='Delete'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:any minOccurs='0' maxOccurs='unbounded' namespace='##other' processContents='lax' /&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:attribute name='Dialect' type='xs:anyURI' use='optional' /&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

  &lt;xs:element name='DeleteResponse'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:any minOccurs='0' namespace='##other' processContents='lax' /&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

  &lt;xs:element name='Create'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:element name='Representation' type='tns:Representation' minOccurs='0'/&gt;
        &lt;xs:any minOccurs='0' maxOccurs='unbounded' namespace='##other' processContents='lax' /&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:attribute name='Dialect' type='xs:anyURI' use='optional' /&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

  &lt;xs:element name='CreateResponse'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:element name='ResourceCreated' type='wsa:EndpointReferenceType' /&gt;
        &lt;xs:element name='Representation' type='tns:Representation' minOccurs='0'/&gt;
        &lt;xs:any minOccurs='0' namespace='##other' processContents='lax' /&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

  &lt;!-- Policy --&gt;
  &lt;xs:complexType name='URI'&gt;
    &lt;xs:simpleContent&gt;
      &lt;xs:extension base='xs:anyURI'&gt;
        &lt;xs:anyAttribute namespace='##other' processContents='lax'/&gt;
      &lt;/xs:extension&gt;
    &lt;/xs:simpleContent&gt;
  &lt;/xs:complexType&gt;

  &lt;xs:complexType name='QName'&gt;
    &lt;xs:simpleContent&gt;
      &lt;xs:extension base='xs:QName'&gt;
        &lt;xs:anyAttribute namespace='##other' processContents='lax'/&gt;
      &lt;/xs:extension&gt;
    &lt;/xs:simpleContent&gt;
  &lt;/xs:complexType&gt;

  &lt;xs:complexType name='Empty'&gt;
    &lt;xs:sequence/&gt;
    &lt;xs:anyAttribute namespace='##other' processContents='lax'/&gt;
  &lt;/xs:complexType&gt;

  &lt;xs:element name='TransferResource'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:element name='PutOperationSupported' type='tns:Empty'
                                                 minOccurs='0'/&gt;
        &lt;xs:element name='DeleteOperationSupported' type='tns:Empty'
                                                    minOccurs='0'/&gt;
        &lt;xs:element name='FaultOnPutDenied' type='tns:Empty' minOccurs='0'/&gt;
        &lt;xs:element name='Dialect' minOccurs='0' maxOccurs='unbounded'&gt;
          &lt;xs:complexType&gt;
            &lt;xs:sequence&gt;
              &lt;xs:any namespace='##other' processContents='lax' minOccurs='0'
                                          maxOccurs='0'/&gt;
            &lt;/xs:sequence&gt;
            &lt;xs:attribute name='URI' type='xs:anyURI' use='required' /&gt;
            &lt;xs:anyAttribute namespace="##other" processContents='lax'/&gt;
          &lt;/xs:complexType&gt;
        &lt;/xs:element&gt;
        &lt;xs:element name='Resource' type='tns:QName' minOccurs='0'/&gt;
        &lt;xs:any namespace='##other' processContents='lax' minOccurs='0'
                                    maxOccurs='unbounded'/&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

  &lt;xs:element name='TransferResourceFactory'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:element name='Resource' type='tns:QName' minOccurs='0'/&gt;
        &lt;xs:element name='Dialect' minOccurs='0' maxOccurs='unbounded'&gt;
          &lt;xs:complexType&gt;
            &lt;xs:sequence&gt;
              &lt;xs:any namespace='##other' processContents='lax' minOccurs='0'
                                          maxOccurs='0'/&gt;
            &lt;/xs:sequence&gt;
            &lt;xs:attribute name='URI' type='xs:anyURI' use='required' /&gt;
            &lt;xs:anyAttribute namespace="##other" processContents='lax'/&gt;
          &lt;/xs:complexType&gt;
        &lt;/xs:element&gt;
        &lt;xs:any namespace='##other' processContents='lax' minOccurs='0'
                                    maxOccurs='unbounded'/&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

&lt;/xs:schema&gt;</pre></div></div></div><div class="div1">
<h2><a name="WSDL" id="WSDL"></a>B WSDL</h2><p>
    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/2011/03/ws-tra/transfer.wsdl">http://www.w3.org/2011/03/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>&lt;wsdl:definitions
    targetNamespace='http://www.w3.org/2011/03/ws-tra'
    xmlns:tns='http://www.w3.org/2011/03/ws-tra'
    xmlns:wsa='http://www.w3.org/2005/08/addressing'
    xmlns:wsam='http://www.w3.org/2007/05/addressing/metadata'
    xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'
    xmlns:xs='http://www.w3.org/2001/XMLSchema'&gt;

  &lt;wsdl:types&gt;
    &lt;xs:schema&gt;
      &lt;xs:import
        namespace='http://www.w3.org/2011/03/ws-tra'
        schemaLocation='http://www.w3.org/2011/03/ws-tra/transfer.xsd'
        /&gt;
    &lt;/xs:schema&gt;
  &lt;/wsdl:types&gt;

  &lt;wsdl:message name='GetMessage'&gt;
    &lt;wsdl:part name='Body' element='tns:Get'/&gt;
  &lt;/wsdl:message&gt;
  &lt;wsdl:message name='GetResponseMessage'&gt;
    &lt;wsdl:part name='Body' element='tns:GetResponse'/&gt;
  &lt;/wsdl:message&gt;

  &lt;wsdl:message name='PutMessage'&gt;
    &lt;wsdl:part name='Body' element='tns:Put'/&gt;
  &lt;/wsdl:message&gt;
  &lt;wsdl:message name='PutResponseMessage'&gt;
    &lt;wsdl:part name='Body' element='tns:PutResponse'/&gt;
  &lt;/wsdl:message&gt;

  &lt;wsdl:message name='DeleteMessage'&gt;
    &lt;wsdl:part name='Body' element='tns:Delete'/&gt;
  &lt;/wsdl:message&gt;
  &lt;wsdl:message name='DeleteResponseMessage'&gt;
    &lt;wsdl:part name='Body' element='tns:DeleteResponse'/&gt;
  &lt;/wsdl:message&gt;

  &lt;wsdl:message name='CreateMessage'&gt;
    &lt;wsdl:part name='Body' element='tns:Create'/&gt;
  &lt;/wsdl:message&gt;
  &lt;wsdl:message name='CreateResponseMessage'&gt;
    &lt;wsdl:part name='Body' element='tns:CreateResponse'/&gt;
  &lt;/wsdl:message&gt;

  &lt;wsdl:portType name='Resource'&gt;
    &lt;wsdl:documentation&gt;
      This port type defines a resource that can be read,
      written, and deleted.
    &lt;/wsdl:documentation&gt;
    &lt;wsdl:operation name='Get'&gt;
      &lt;wsdl:input
        message='tns:GetMessage'
        wsam:Action='http://www.w3.org/2011/03/ws-tra/Get'/&gt;
      &lt;wsdl:output
        message='tns:GetResponseMessage'
        wsam:Action='http://www.w3.org/2011/03/ws-tra/GetResponse' /&gt;
    &lt;/wsdl:operation&gt;
    &lt;wsdl:operation name='Put'&gt;
      &lt;wsdl:input
        message='tns:PutMessage'
        wsam:Action='http://www.w3.org/2011/03/ws-tra/Put' /&gt;
      &lt;wsdl:output
        message='tns:PutResponseMessage'
        wsam:Action='http://www.w3.org/2011/03/ws-tra/PutResponse' /&gt;
    &lt;/wsdl:operation&gt;
    &lt;wsdl:operation name='Delete'&gt;
      &lt;wsdl:input
        message='tns:DeleteMessage'
        wsam:Action='http://www.w3.org/2011/03/ws-tra/Delete' /&gt;
      &lt;wsdl:output
        message='tns:DeleteResponseMessage'
        wsam:Action='http://www.w3.org/2011/03/ws-tra/DeleteResponse' /&gt;
    &lt;/wsdl:operation&gt;
  &lt;/wsdl:portType&gt;

  &lt;wsdl:portType name='ResourceFactory'&gt;
    &lt;wsdl:documentation&gt;
      This port type defines a Web service that can create new
      resources.
    &lt;/wsdl:documentation&gt;
    &lt;wsdl:operation name='Create'&gt;
      &lt;wsdl:input
        message='tns:CreateMessage'
        wsam:Action='http://www.w3.org/2011/03/ws-tra/Create' /&gt;
      &lt;wsdl:output
        message='tns:CreateResponseMessage'
        wsam:Action='http://www.w3.org/2011/03/ws-tra/CreateResponse' /&gt;
    &lt;/wsdl:operation&gt;
  &lt;/wsdl:portType&gt;

&lt;/wsdl:definitions&gt;</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=6588">6588</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><tr><td> 2009/03/23 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6666">6666</a>
      </td></tr><tr><td> 2009/03/24 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6648">6648</a>
      </td></tr><tr><td> 2009/04/20 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6730">6730</a>
      </td></tr><tr><td> 2009/04/22 </td><td> KW </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6739">6739</a>
      </td></tr><tr><td> 2009/05/12 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6433">6433</a>
      </td></tr><tr><td> 2009/05/13 </td><td> DD </td><td> Added resolution of issues
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6672">6672</a>,
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6673">6673</a>,
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6594">6594</a>
      </td></tr><tr><td> 2009/05/19 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6849">6849</a>
      </td></tr><tr><td> 2009/05/19 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6907">6907</a>
      </td></tr><tr><td> 2009/05/21 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6674">6674</a>
      </td></tr><tr><td> 2009/05/27 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6906">6906</a>
      </td></tr><tr><td> 2009/06/10 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6712">6712</a>
      </td></tr><tr><td> 2009/06/10 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6924">6924</a>
      </td></tr><tr><td> 2009/07/07 </td><td> DD </td><td> Added resolution of issues
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7014">7014</a>,
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6975">6975</a>,
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6413">6413</a>
      </td></tr><tr><td> 2009/08/05 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7159">7159</a>
      </td></tr><tr><td> 2009/08/18 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</a>
      </td></tr><tr><td> 2009/08/18 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7191">7191</a>
      </td></tr><tr><td> 2009/08/25 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7365">7365</a>
      </td></tr><tr><td> 2009/08/25 </td><td> DD </td><td> Added resolution of issue
       <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=6704">6704</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><tr><td> 2009/09/16 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7486">7486</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=6572">6572</a>
      </td></tr><tr><td> 2009/10/02 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</a>
      </td></tr><tr><td> 2009/10/05 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7731">7731</a>,
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6721">6721</a>
      </td></tr><tr><td> 2009/10/13 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7812">7812</a>
      </td></tr><tr><td> 2009/10/13 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7827">7827</a>
      </td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7068">7068</a>
      </td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7968">7968</a>
      </td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</a>
      </td></tr><tr><td> 2009/11/05 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7912">7912</a>
      </td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8177">8177</a>
      </td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8186">8186</a>
      </td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8184">8184</a>
      </td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8124">8124</a>
      </td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8179">8179</a>
      </td></tr><tr><td> 2009/11/17 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8280">8280</a>
      </td></tr><tr><td> 2009/12/01 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8201">8201</a>
      </td></tr><tr><td> 2010/01/05 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8183">8183</a>
      </td></tr><tr><td> 2010/01/12 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8300">8300</a>
      </td></tr><tr><td> 2010/01/12 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8303">8303</a>
      </td></tr><tr><td> 2010/01/12 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8176">8176</a>
      </td></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8301">8301</a>
      </td></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283">8283</a>
      </td></tr><tr><td> 2010/01/26 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7774">7774</a>
      </td></tr><tr><td> 2010/01/28 </td><td> DD </td><td> Added resolution of issues
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8302">8302</a>,
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8180">8180</a>,
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8299">8299</a>
      </td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</a>
      </td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8298">8298</a>
      </td></tr><tr><td> 2010/02/16 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9032">9032</a>
      </td></tr><tr><td> 2010/03/09 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6463">6463</a>,
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</a>,
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</a>
      </td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</a>
      </td></tr><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9588">9588</a>
      </td></tr><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</a>
      </td></tr><tr><td> 2010/05/11 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9569">9569</a>
      </td></tr><tr><td> 2010/05/11 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9699">9699</a>
      </td></tr><tr><td> 2010/08/17 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=10339">10339</a>
      </td></tr><tr><td> 2010/11/16 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11202">11202</a>
      </td></tr><tr><td> 2010/11/16 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11210">11210</a>
      </td></tr><tr><td> 2010/11/19 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8284">8284</a>
      </td></tr><tr><td> 2011/02/01 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11882">11882</a>
      </td></tr><tr><td> 2011/02/07 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11899">11899</a>
      </td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11766">11766</a>
      </td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=12063">12063</a>
      </td></tr><tr><td> 2011/11/08 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=14232">14232</a>
      </td></tr></tbody></table></div></div></body></html>