<img width="72" height="48" alt= "W3C" src="http://www.w3.org/Icons/w3c_home" /> W3C

2004-08-03 diff-marked version: Web Services Description Language (WSDL) Version 1.2 2.0 Part 3: Bindings

W3C Working Draft 11 June 2003 3 August 2004

This version:
<a href= "http://www.w3.org/TR/2003/WD-wsdl12-bindings-20030611"> http://www.w3.org/TR/2003/WD-wsdl12-bindings-20030611 http://www.w3.org/TR/2004/WD-wsdl20-bindings-20040803
Latest version:
<a href= "http://www.w3.org/TR/wsdl12-bindings"> http://www.w3.org/TR/wsdl12-bindings http://www.w3.org/TR/wsdl20-bindings
Previous versions:
<a href= "http://www.w3.org/TR/2003/WD-wsdl12-bindings-20030124"> http://www.w3.org/TR/2003/WD-wsdl12-bindings-20030124 http://www.w3.org/TR/2003/WD-wsdl12-bindings-20030611
Editors:
Hugo Haas, W3C
Philippe Le Hégaret, W3C
Jean-Jacques Moreau, Canon
David Orchard, BEA Systems
Jeffrey Schlimmer, Microsoft
Sanjiva Weerawarana, IBM Research

This document is also available in these non-normative formats: <a href= "http://www.w3.org/TR/2003/WD-wsdl12-bindings-20030611/wsdl12-bindings.ps"> postscript , <a href= "http://www.w3.org/TR/2003/WD-wsdl12-bindings-20030611/wsdl12-bindings.pdf"> PDF , <a href= "http://www.w3.org/TR/2003/WD-wsdl12-bindings-20030611/wsdl12-bindings.xml"> XML , and  <a href= "http://www.w3.org/TR/2003/WD-wsdl12-bindings-20030611/wsdl12-bindings.txt"> plain text .


Abstract

WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. WSDL Version 1.2 2.0 Bindings describes how to use WSDL in conjunction with SOAP 1.2 [ SOAP 1.2 Part 1: Messaging Framework ], ] and HTTP/1.1 deleted text: GET/POST [ <a href= "#RFC2616"> IETF RFC 2616 ], and MIME [ <cite> <a href= "#RFC2045"> IETF RFC 2045 </a> </cite> ]. ] (as well as other versions of HTTP). This specification depends on WSDL Version 1.2 2.0 [ <a href="#WSDL-PART1"> WSDL 1.2 2.0 Core Language ].

Status of this Document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. The A list of current W3C publications and the latest status revision of this document series is maintained at technical report can be found in the W3C. W3C technical reports index at http://www.w3.org/TR/.

This is a <a href= "http://www.w3.org/Consortium/Process-20010719/tr.html#RecsWD"> W3C Last Call Working Draft </a> of .If the WSDL Version 1.2 Bindings feedback is positive, the Working Group plans to submit this specification for review by consideration as a W3C members Candidate Recommendation. Comments on this document are invited and other interested parties. are to be sent to the public public-ws-desc-comments@w3.org mailing list ( public archive ). Comments can be sent until 4 October 2004 .

Three formal objections from Working Group participants have been received against portions of the WSDL 2.0 specification. Feedback is specifically encouraged on these topics:

A diff-marked version against the previous version of this document is available. For a detailed list of changes since the last publication of this document, please refer to appendix B. Part 3 Change Log .Issues about this document are documented in the last call issues list maintained by the Working Group.

This document has been produced as part of the W3C Web Services Activity . The authors of this document are the Web Services Description Working Group members.

Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to deleted text: use W3C Working Drafts as reference material or to cite them this document as other than deleted text: "work in progress". This is work in progress and does not imply endorsement by, or the consensus of, either W3C or members of the Web Services Description Working Group. </p> <p> For a detailed list of changes since the last publication of this document, refer to appendix <a href="#changelog"> <b> B. Part 2 Change Log </b> </a>. progress.

Comments on this document are invited and are to be sent to <a href= "mailto:public-ws-desc-comments@w3.org"> public-ws-desc-comments@w3.org </a> ( <a href= "http://lists.w3.org/Archives/Public/public-ws-desc-comments/"> public archive </a> ). It is inappropriate to send discussion emails to this address. Discussion of this This document takes place on has been produced under the public <a href="mailto:www-ws-desc@w3.org"> www-ws-desc@w3.org </a> mailing list ( <a href= "http://lists.w3.org/Archives/Public/www-ws-desc/"> public archive 24 January 2002 Current Patent Practice ). </p> <p> as amended by the W3C Patent Policy Transition Procedure . Patent disclosures relevant to this specification may be found on the Working Group's patent disclosure page . </p> <p> A list An individual who has actual knowledge of <a href="http://www.w3.org/TR/"> current a patent which the individual believes contains Essential Claim(s) with respect to this specification should disclose the information in accordance with section 6 of the W3C Recommendations and other technical documents </a> can be found at http://www.w3.org/TR. Patent Policy .


Short Table of Contents

1. Introduction
2. <a href="#_soap-b"> WSDL SOAP Binding
3. <a href="#_http"> WSDL HTTP Binding
4. deleted text: <a href="#_mime"> MIME Binding </a> <br /> 5. References
A. Acknowledgements (Non-Normative)
B. Part 2 3 Change Log (Non-Normative)


Table of Contents

1. Introduction
    1.1 Notational Conventions
2. <a href="#_soap-b"> WSDL SOAP Binding
    2.1 <a href="#_soap_binding"> binding Element with binding [parent] </a> <br />         2.1.1 <a href= "#_soap_binding_transport"> protocol Attribute with binding [owner] </a> <br />         2.1.2 <a href= "#_soap_binding_style"> styleDefault Attribute with binding [owner] </a> <br />         2.1.3 <a href= "#_soap_binding_name"> namespaceDefault Attribute with binding [owner] </a> <br />         2.1.4 <a href= "#_soap_binding_encoding"> encodingStyleDefault Attribute with binding [owner] XML Syntax Summary (Non-Normative)
    2.2 <a href="#_soap_module"> module Element with binding [parent] </a> <br />         2.2.1 <a href= "#_soap_module_uri"> uri Attribute with module [owner] </a> <br />         2.2.2 <a href= "#_soap_module_required"> required Attribute with binding [owner] Identifying a SOAP Binding
    2.3 <a href= "#_soap_property"> propertyConstraint Element with module [parent] Default Binding Rules
        2.3.1 <a href= "#_soap_property_uri"> uri Attribute with propertyConstraint [owner]     2.4 Specifying the SOAP Underlying Protocol
        2.3.2 <a href= "#_soap_property_type"> type Attribute with propertyConstraint [owner]         2.4.1 Description
    2.4 <a href="#_soap_operation"> operation Element with operation [parent]         2.4.2 Relationship to WSDL Component Model
        2.4.1 <a href= "#_soap_operation_style"> style Attribute with operation [owner]         2.4.3 XML Representation
        2.4.2 <a href= "#_soap_operation_action"> soapAction Attribute with operation [owner]         2.4.4 Mapping Between Component Properties and XML Representation
    2.5 <a href="#_soap_body"> body Element with input or output [parent] Specifying the Default SOAP MEP
        2.5.1 <a href= "#_soap_body_name"> namespace Attribute with body [owner] Description
        2.5.2 <a href= "#_soap_body_encoding"> encodingStyle Attribute with body [owner] Relationship to WSDL Component Model
        2.5.3 XML Representation
    2.6 <a href="#_soap_header"> header Element with input or output [parent] Declaring SOAP Modules
        2.6.1 <a href= "#_soap_header_element"> element Attribute with header [owner] Description
        2.6.2 <a href= "#_soap_header_type"> type Attribute with header [owner] Relationship to WSDL Component Model
        2.6.3 <a href= "#_soap_header_localname"> localname Attribute with header [owner] SOAP Module Component
        2.6.4 <a href= "#_soap_header_namespace"> namespace Attribute with header [owner] XML Representation
        2.6.5 <a href= "#_soap_header_encoding"> encodingStyle Attribute with header [owner] </a> <br />         2.6.6 <a href= "#_soap_header_role"> role Attribute with header [owner] Mapping Between Component Properties and XML Representation
    2.7 <a href= "#_soap_headerfault"> headerfault Element with input or output [parent] Binding Faults
        2.7.1 <a href= "#_soap_headerfault_message"> message Attribute with headerfault [owner] Description
        2.7.2 <a href= "#_soap_headerfault_part"> part Attribute with headerfault [owner] Relationship to WSDL Component Model
        2.7.3 <a href= "#_soap_headerfault_namespace"> namespace Attribute with headerfault [owner] XML Representation
        2.7.4 <a href= "#_soap_headerfault_encoding"> encodingStyle Attribute with headerfault [owner] Mapping Between Component Properties and XML Representation
    2.8 <a href="#_soap_fault"> fault Element with fault [parent] Binding Operations
        2.8.1 <a href= "#_soap_fault_message"> message Attribute with fault [owner] Description
        2.8.2 <a href= "#_soap_fault_namespace"> namespace Attribute with fault [owner] Relationship to WSDL Component Model
        2.8.3 <a href= "#_soap_fault_encoding"> encodingStyle Attribute with fault [owner] </a> <br />     2.9 <a href="#_soap_address"> address Element with endpoint [parent] XML Representation
        2.9.1 <a href= "#_soap_location"> location Attribute with address [owner]         2.8.4 Mapping Between Component Properties and XML Representation
3. <a href="#_http"> WSDL HTTP Binding
    3.1 <a href="#_http_binding"> binding Element with binding [parent] Identifying an HTTP Binding
        3.1.1 <a href= "#_http_binding_verbDefault"> verbDefault Attribute with binding [owner]     3.2 HTTP Syntax Summary (Non-Normative)
    3.2 <a href="#_http_operation"> operation Element with operation [parent]     3.3 Default Binding Rules
        3.2.1 <a href= "#_http_operation_verb"> verb Attribute with operation [owner]     3.4 Specifying the HTTP Version
        3.2.2 <a href= "#_http_operation_location"> location Attribute with operation [owner]         3.4.1 Description
    3.3 <a href="#_http_get_binding"> Method is GET         3.4.2 Relationship to WSDL Component Model
        3.3.1 <a href= "#_http_operation_location_cited_get"> Case of Input Parts Cited in location Attribute         3.4.3 XML Representation
        3.3.2 <a href= "#_http_operation_location_notcited_get"> Case of Input Parts NOT Cited in location attribute         3.4.4 Mapping Between Component Properties and XML Representation
            3.3.2.1 <a href="#_http_operation_request_get_body_request"> Serializing Parts into     3.5 Specifying the Default HTTP Body request Method
        3.3.3 <a href= "#_http_operation_response_get"> Case         3.5.1 Description
        3.5.2 Relationship to WSDL Component Model
        3.5.3 XML Representation
    3.6 Binding Operations
        3.6.1 Description
        3.6.2 Relationship to WSDL Component Model
        3.6.3 XML Representation of Output Parts HTTP Operation Component
            3.3.3.1 <a href="#_http_operation_response_get_body_response"> Serializing parts into         3.6.4 Mapping Between HTTP Body response Operation's XML Representation to Component Properties
    3.4 <a href="#_http_post_binding"> Method is POST     3.7 Specifying HTTP Error Codes for Faults
        3.4.1 <a href= "#_http_operation_xml_encoding">         3.7.1 Description
        3.7.2 Relationship to WSDL Component Model
        3.7.3 XML Encoding Mechanism Representation
            3.4.1.1 <a href="#_http_operation_location_cited_post_xml">         3.7.4 Mapping Between Component Properties and XML Representation
    3.8 Serialization format of instance data
        3.8.1 Serialization as application/x-www-form-urlencoded
            3.8.1.1 Case of Input Parts Cited elements cited in location Attribute whttp:location attribute
            3.4.1.2 <a href="#_http_operation_location_notcited_post_xml">             3.8.1.2 Case of Input Parts elements NOT Cited cited in location whttp:location attribute
            3.4.1.3 <a href="#_http_operation_response_post_xml"> Case of Output Parts                 3.8.1.2.1 Serialization in the request URI
        3.4.2                 3.8.1.2.2 Serialization in the message body
        3.8.2 Serialization as application/xml
        3.8.3 Serialization as multipart/form-data
    3.9 Operation Styles
        3.9.1 URI Style
        3.9.2 Multipart Encoding Mechanism style
            3.4.2.1 <a href="#_http_operation_location_cited_post_multipart"> Case of Input Parts Cited in location Attribute     3.10 Specifying the transfer coding
            3.4.2.2 <a href="#_http_operation_location_notcited_post_multipart"> Case of Input Parts NOT Cited in location Attribute         3.10.1 Description
            3.4.2.3 <a href="#_http_operation_response_post_multipart"> Case of Output Parts         3.10.2 Relationship to WSDL Component Model
        3.4.3 <a href= "#_http_operation_form_encoding"> application/x-www-form-urlencoded Encoding Mechanism         3.10.3 XML Representation
            3.4.3.1 <a href="#_http_operation_location_cited_post_form"> Case of Input Parts Cited in location Attribute         3.10.4 Mapping Between Component Properties and XML Representation
            3.4.3.2 <a href="#_http_operation_location_notcited_post_form"> Case     3.11 Specifying the Use of Input Parts NOT Cited in location Attribute HTTP Cookies
            3.4.3.3 <a href="#_http_operation_response_post_form"> Case of Output Parts         3.11.1 Description
    3.5 <a href="#_http_address"> address Element with endpoint [parent]         3.11.2 Relationship to WSDL Component Model
        3.5.1 <a href= "#_http_location"> location Attribute with address [owner]         3.11.3 XML Representation
4. <a href="#_mime"> MIME Binding         3.11.4 Mapping Between Component Properties and XML Representation
    4.1 <a href="#_how_mime_extends"> How the MIME Binding extends WSDL     3.12 Specifying HTTP Access Authentication
    4.2 <a href= "#_mime_content"> mime:content         3.12.1 Description
    4.3 <a href= "#_mime_multipartRelated"> mime:multipartRelated         3.12.2 Relationship to WSDL Component Model
    4.4 <a href= "#_mime_soap_body"> soap:body         3.12.3 XML Representation
    4.5 <a href= "#_mime_mimeXml"> mime:mimeXml         3.12.4 Mapping Between Component Properties and XML Representation
5. 4. References
    5.1     4.1 Normative References
    5.2     4.2 Informative References

<a id="appendix" name="appendix"> Appendices

A. Acknowledgements (Non-Normative)
B. Part 2 3 Change Log (Non-Normative)
deleted text:     B.1 <a href="#wsdl-spec-changelog"> WSDL Specification Changes </a> <br />     B.2 <a href="#xml-schema-changes"> XML Schema Changes </a>


1. Introduction

The Web Services Description Language WSDL Version 1.2 2.0 (WSDL) [ WSDL 1.2 2.0 Core Language ] defines an XML grammar [ <cite> <a href="#XML"> XML 1.0 </a> </cite> ] language for describing network services as collections of communication endpoints capable of exchanging messages. WSDL service definitions provide documentation for distributed systems and serve as a recipe for automating the details involved in applications communication. WSDL 1.2 2.0 Bindings (this document) defines binding extensions for the following protocols and message formats:

WSDL 1.2 2.0 Primer [ WSDL 1.2 2.0 Primer ] is a non-normative document intended to provide an easily understandable tutorial on the features of the WSDL Version 1.2 2.0 specifications.

The Core Language [ WSDL 1.2 2.0 Core Language ] of the WSDL 1.2 2.0 specification describes the core elements of the WSDL language.

1.1 Notational Conventions

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 RFC2119 [ IETF RFC 2119 ].

This specification uses a number of namespace prefixes throughout; they are listed in Table 1-1 . Note that the choice of any namespace prefix is arbitrary and not semantically significant (see [ XML Information Set ]).


Table 1-1. Prefixes and Namespaces used in this specification
Prefix Namespace Notes
wsdl "http://www.w3.org/2003/06/wsdl" "http://www.w3.org/2004/08/wsdl" A normative XML Schema [ XML Schema Structures ], [ XML Schema Datatypes ] document for the "http://www.w3.org/2003/06/wsdl" "http://www.w3.org/2004/08/wsdl" namespace can be found at <a href= "http://www.w3.org/2003/06/wsdl"> http://www.w3.org/2003/06/wsdl http://www.w3.org/2004/08/wsdl .
soap wsoap "http://www.w3.org/2003/06/wsdl/soap12" "http://www.w3.org/2004/08/wsdl/soap12" A normative XML Schema [ XML Schema Structures ], [ XML Schema Datatypes ] document for the "http://www.w3.org/2003/06/wsdl/soap12" "http://www.w3.org/2004/08/wsdl/soap12" namespace can be found at <a href= "http://www.w3.org/2003/06/wsdl/soap12"> http://www.w3.org/2003/06/wsdl/soap12 http://www.w3.org/2004/08/wsdl/soap12 .
http whttp "http://www.w3.org/2003/06/wsdl/http" "http://www.w3.org/2004/08/wsdl/http" A normative XML Schema [ XML Schema Structures ], [ XML Schema Datatypes ] document for the "http://www.w3.org/2003/06/wsdl/http" "http://www.w3.org/2004/08/wsdl/http" namespace can be found at <a href= "http://www.w3.org/2003/06/wsdl/http"> http://www.w3.org/2003/06/wsdl/http http://www.w3.org/2004/08/wsdl/http .
mime wsdls "http://www.w3.org/2003/06/wsdl/mime" "http://www.w3.org/2004/08/wsdl-simple-types" A normative XML Schema [ <cite> <a href= "#XMLSchemaP1"> XML Schema Structures </a> </cite> ], This prefix and namespace name are used to refer to the simple types defined by [ <a href= "#XMLSchemaP2"> XML Schema Datatypes WSDL 2.0 Core Language ] deleted text: document for use in the "http://www.w3.org/2003/06/wsdl/mime" namespace can be found at <a href= "http://www.w3.org/2003/06/wsdl/mime"> http://www.w3.org/2003/06/wsdl/mime </a>. </td> </tr> <tr> <td rowspan="1" colspan="1"> xsd </td> <td rowspan="1" colspan="1"> "http://www.w3.org/2001/XMLSchema" </td> <td rowspan="1" colspan="1"> Defined component model, see Definition of the Simple Types Used in the W3C XML Schema specification [ <cite> <a href="#XMLSchemaP1"> XML Schema Structures </a> </cite> ], [ <cite> <a href="#XMLSchemaP2"> XML Schema Datatypes </a> </cite> ]. Component Model .
xsi xs "http://www.w3.org/2001/XMLSchema-instance" "http://www.w3.org/2001/XMLSchema" Defined in the W3C XML Schema specification [ XML Schema Structures ], [ XML Schema Datatypes ].

Namespace names of the general form "http://example.org/..." and "http://example.com/..." represent application or context-dependent URIs [ IETF RFC 2396 ].

deleted text: This specification uses the Extended Backus-Naur Form (EBNF) as described in XML 1.0 [ <cite> <a href="#XML"> XML 1.0 </a> </cite> ]. </p> <p> All parts of this specification are normative, with the EXCEPTION of pseudo-schemas, examples, and sections explicitly marked as "Non-Normative". Pseudo-schemas are provided for each component, before the description of this component. They provide visual help for the XML 1.0-based [ XML 1.0 ] serialization, but do not limit the ability of the bindings to be expressed with other versions of XML such as XML 1.1 [ XML 1.1 ] or futures versions of XML Schema [ XML Schema Structures ], [ XML Schema Datatypes ].

Note that the WSDL binding specifications in this document are defined in terms of a component model defined by this specification. As such, it is explicitly NOT a conformance requirement to be able to process documents encoded in a particular version of XML.

<a name="_soap-b" id="_soap-b"> 2. WSDL SOAP Binding

<table border="1" summary="Editorial note: JCS"> <tr> <td width="50%" valign="top" align="left"> <b> Editorial note: JCS </b> </td> <td width="50%" valign="top" align="right"> 20030115 </td> </tr> <tr> <td valign="top" align="left" colspan="2">

The WG is actively redesigning the SOAP/HTTP SOAP binding to align with changes described in this section is an extension for [ WSDL 2.0 Core Language ] to enable Web Services applications to use SOAP 1.2. </td> </tr> </table> <table border="1" summary="Editorial note: JCS"> <tr> <td width="50%" valign="top" align="left"> 1.2 [ <b> Editorial note: JCS </b> SOAP 1.2 Part 1: Messaging Framework </td> <td width="50%" valign="top" align="right"> 20030115 </td> </tr> <tr> <td valign="top" align="left" colspan="2"> ]. This section is not fully converted binding extends WSDL 2.0 by adding properties to a the Binding component model compatible as defined in [ WSDL 2.0 Core Language ]. In addition, an XML Infoset representation for these additional properties is provided, along with Part 1. </td> </tr> </table> a mapping from that representation to the various component properties.

As allowed in [ WSDL includes 2.0 Core Language ], a Binding component MAY exist without indicating a specific Interface component that it applies to. In this case there MUST NOT be any Binding Operation or Binding Fault components present in the Binding component.

The SOAP binding is designed with the objective of minimizing what needs to be explicitly declared for SOAP 1.2 endpoints, common cases. This is achieved by defining a set of default rules which supports the specification apply for all Interface Operation components of an Interface component, unless specifically overidden on a per Interface Operation basis. Thus, if a given Interface Operation component is not referred to specifically, then all the following protocol specific information: default rules apply for that component. That is, per the requirements of [ WSDL 2.0 Core Language ] all operations of an Interface component are bound by this binding.

deleted text: <ul> <li>

An indication Notice that a there are no default binding is rules defined for Interface Fault components by this binding. Thus, if a given Interface component has any Fault components, then such Interface components MUST be bound to via Binding components which indicate a specific interface and contain as many Binding Fault components as there are Fault components in the SOAP 1.2 protocol. Interface Fault component.

deleted text: </li> <li>

A way subset of deleted text: specifying an address for a SOAP endpoint. </p> </li> <li> <p> The URI for the deleted text: SOAPAction HTTP header field for properties specified in the HTTP binding of SOAP. </p> <table border="1" summary="Editorial note: JCS"> <tr> <td width="50%" valign="top" align="left"> defined in section Editorial note: JCS 3. WSDL HTTP Binding </td> <td width="50%" valign="top" align="right"> 20030115 </td> </tr> <tr> <td valign="top" align="left" colspan="2"> The may be expressed in a SOAP deleted text: 1.2 HTTP binding does not define a SOAPAction when the SOAP binding uses HTTP header field. This as the underlying protocol, i.e. when the value of the {soap underlying protocol} property of the Binding component is a known issue. </td> </tr> </table> "http://www.w3.org/2003/05/soap/bindings/HTTP/". The properties that are allowed are the ones that describe the underlying protocol.

When the SOAP bindings that do not require a <code> SOAPAction </code> omit Message Exchange Pattern is the <code> soapAction </code> attribute SOAP Response MEP, the Binding Operation may use the {http location} property defined in <a href= "#_soap_operation"> 2.4 operation Element with operation [parent] 3.6 Binding Operations .When such a location is specified, the Endpoint component also follows the rules for constructing the address from the {address} . property and the {http location} property values.

deleted text: </li> </ul>

<a name="_soap_binding" id="_soap_binding"> 2.1 <code> binding </code> Element with <code> binding </code> [parent] XML Syntax Summary (Non-Normative)

<definitions >


 <binding >
  <<b>soap:binding</b> protocol="uri" 
                styleDefault="document|rpc"?
                namespaceDefault="uri"? 
                encodingStyleDefault="uri"? />
 </binding>



  <binding name="xs:NCName" interface="xs:QName"?
           type="http://www.w3.org/2004/08/wsdl/soap12"
           whttp:version="xs:string"??
           whttp:defaultTransferCoding="xs:string"??
           wsoap:protocol="xs:anyURI"
           wsoap:mepDefault="xs:anyURI"? >
    <documentation />?

    <wsoap:module uri="xs:anyURI" required="xs:boolean"? >
      <documentation />?
    </wsoap:module>*
    
    <fault ref="xs:QName"
           wsoap:code="xs:QName"
           wsoap:subcodes="list of xs:QName"? >
      <documentation />?
    </fault>*

    <operation ref="xs:QName" 
               whttp:defaultTransferCoding="xs:string"?? >
               wsoap:mep="xs:anyURI"?
               wsoap:action="xs:anyURI"? >
      <documentation />?

      <wsoap:module ... />*

      <input messageLabel="xs:NCName"?
             whttp:transferCoding="xs:string?? >
        <documentation />?
        <wsoap:module ... />*
        <feature ... />*
        <property ... />*
      </input>*

      <output messageLabel="xs:NCName"?
             whttp:transferCoding="xs:string?? >
        <documentation />?
        <wsoap:module ... />*
        <feature ... />*
        <property ... />*
      </output>*

      <feature ... />*
      <property ... />*
    </operation>*

    <feature ... />*
    <property ... />*

  </binding>

  <service>
    <endpoint name="xs:NCName" binding="xs:QName" address="xs:anyURI"?
              whttp:authenticationType="xs:string"?? 
              whttp:authenticationRealm="xs:string"?? >
      <documentation />?
      <feature ... />*
      <property ... />*
    </endpoint>
    <feature ... />*
    <property ... />*
  </service>


</definitions>

Note:

The mandatory double question marks (" binding ?? <em> element information item </em> ") after the attributes in the whttp namespace indicates that messages are those optional attributes only make sense if the when the SOAP Envelopes binding uses HTTP as the underlying protocol, i.e. when the value of the wsoap:protocol attribute is "http://www.w3.org/2003/05/soap/bindings/HTTP/".

2.2 Identifying a SOAP Binding

A Binding component (defined in [ <a href="#SOAP12-PART1"> SOAP 1.2 Part 1: Messaging Framework WSDL 2.0 Core Language ]. </p> <p> The <code> ]) is identified as a SOAP binding </code> <em> element information item </em> has by assigning the following Infoset properties: value "http://www.w3.org/2004/08/wsdl/soap12" to the {type} property of the Binding component.

2.3 Default Binding Rules

  • deleted text: A [local name] of <code> binding </code> </p> </li> <li> <p> A [namespace name] Payload Construction. When formulating the SOAP envelope to be transmitted the contents of "http://www.w3.org/2003/06/wsdl/soap12" </p> </li> <li> <p> A [parent] the payload (i.e., the contents of the binding soap:Body deleted text: in the namespace named "http://www.w3.org/2003/06/wsdl" </p> </li> <li> <p> One or more attribute element information item s amongst its [attributes] of the SOAP envelope) MUST be what is defined by the corresponding Message Reference component. This is subject to optimization by a feature that is in use which may affect serialization, such as follows: MTOM [ SOAP Message Transmission Optimization Mechanism ]. The following default binding rules MUST be adhered to:

    • A required <code> protocol </code> If the value of the {message content model} property of the Message Reference component is attribute information item #any as described below. then the payload MAY be any one XML element.

    • An optional <code> styleDefault </code> If the value is attribute information item #none as described below. then the payload MUST be empty.

    • An optional <code> namespaceDefault </code> If the value is attribute #element then the payload will be the element information item as described below. identified by the {element} property of the Message Reference component.

    • An optional <code> encodingStyleDefault </code> <em> attribute information item </em> as described below. If the Message Reference component is declared using a non-XML type system (as considered in the Types section of [ WSDL 2.0 Core Language ]) then additional binding rules MUST be defined to indicate how to map those components into the SOAP envelope.

    </li> </ul>

    Note:

    The <code> This SOAP binding </code> <em> only allows one single element information item </em> has no [children]. in SOAP body.

    <div class="div3"> <h4> <a name="_soap_binding_transport" id= "_soap_binding_transport"> </a> 2.1.1 <code> protocol </code> Attribute with <code> binding </code> [owner] </h4>
  • The <code> protocol </code> attribute information item SOAPAction. indicates which underlying protocol to use If a value for SOAP Envelopes within the {soap action} property of a <code> binding </code> <em> element information item </em>. The <code> protocol </code> <em> attribute information item </em> Binding Operation component has NOT been specified then the following Infoset properties: </p> <ul> <li> <p> A [local name] of <code> protocol </code> SOAP Action Feature (see [ SOAP 1.2 Part 2: Adjuncts ]) has NO value assigned by the Binding component.

  • A [namespace name] which SOAP MEP Selection. If the Interface Operation component's {message exchange pattern} property has the value "http://www.w3.org/2004/08/wsdl/in-out" then the default value of the {soap mep} property for the corresponding Binding Operation component is "http://www.w3.org/2003/05/soap/mep/request-response/" identifying the SOAP Request-Response Message Exchange Pattern as defined in [ SOAP 1.2 Part 2: Adjuncts ]. If the Inteface Operation component has any other value for the {message exchange pattern} property, then no default value is defined for the {soap mep} property of the corresponding Binding Operation component.

  • An [owner] of <code> HTTP Method Selection. This default binding </code> in rule is applicable when the namespace named "http://www.w3.org/2003/06/wsdl/soap12" </p> </li> </ul> <p> The type value of the <code> protocol </code> <em> attribute information item </em> {soap underlying protocol} property of the Binding component is "http://www.w3.org/2003/05/soap/bindings/HTTP/". If the {soap mep} property of the Binding Operation component has the value "http://www.w3.org/2003/05/soap/mep/request-response/" then the default value of the {http method} property is xsd:anyURI POST . The If the {soap mep} property of the Binding Operation component has the value "http://www.w3.org/2003/05/soap/mep/soap-response/" then the default value of the <code> protocol </code> {http method} property is attribute information item GET .

  • HTTP URI Generation. This default binding rule is a URI that identifies a specific protocol to carry SOAP Envelopes. The URI applicable when the value "http://www.w3.org/2003/05/soap/bindings/HTTP/" corresponds of the {soap underlying protocol} property of the Binding component is "http://www.w3.org/2003/05/soap/bindings/HTTP/". If the {soap mep} property of the Binding Operation component has the value "http://www.w3.org/2003/05/soap/mep/soap-response/" then the URI to execute the HTTP binding in GET against MUST be generated using the SOAP specification. </p> </div> <div class="div3"> <h4> HTTP binding's rules for generating a URI for HTTP GET (see <a name="_soap_binding_style" id= "_soap_binding_style"> 3. WSDL HTTP Binding 2.1.2 <code> styleDefault </code> Attribute with <code> binding </code> [owner] </h4> <p> ). The input serialization format of styleDefault x-www-form-urlencoded <em> attribute information item </em> indicates is the default only supported serialization style format for all operations contained within HTTP GET in the [ancestor] SOAP Response Message Exchange Pattern.

    Editorial note: Input serialization for HTTP GET in SOAP HTTP binding  
    Use of a different input serialization format requires introduction of either a new MEP or a new binding. The <code> styleDefault </code> <em> attribute information item </em> has Working Group considered the following Infoset properties: </p> <ul> <li> <p> A [local name] limitations of the styleDefault x-www-form-urlencoded </p> </li> <li> <p> A [namespace name] serialization format (see points #2 and #3 of Binding message content to URI analysis ). It decided that the limitations of the serialization format, which has no value </p> could potentially be solved by a serialization format extension, were not sufficiently broad enough to warrant allowing extensibility in input serialization for the soap-response MEP. The Working Group solicits the public's feedback on this decision.
  • <li>

2.4 Specifying the SOAP Underlying Protocol

2.4.1 Description

An [owner] of <code> Every SOAP binding </code> MUST indicate what underlying protocol is in use, as defined in the namespace named "http://www.w3.org/2003/06/wsdl/soap12" SOAP Protocol Binding Framework section of [ SOAP 1.2 Part 1: Messaging Framework ].

deleted text: </li> </ul>

The type of SOAP binding defined by this specification supports the <code> styleDefault </code> <em> attribute information item </em> is <em> xsd:string </em>. The value of SOAP HTTP binding defined by the <code> styleDefault </code> <em> attribute information item </em> [ SOAP 1.2 Part 2: Adjuncts ] specification. This is either "document" or "rpc"; if indicated by assigning the <code> styleDefault </code> <em> attribute information item </em> is omitted, URI "http://www.w3.org/2003/05/soap/bindings/HTTP/" (as defined by [ SOAP 1.2 Part 2: Adjuncts ]) to the value is "document". See below {soap underlying protocol} property defined below. Other values MAY be used for more information on this property in conjunction with the SOAP binding defined by this specification provided that the semantics of the <code> style </code> <em> attribute information item </em>. such protocols are consistent with this binding.

<a name="_soap_binding_name" id="_soap_binding_name"> 2.1.3 <code> namespaceDefault </code> Attribute with <code> binding </code> [owner] 2.4.2 Relationship to WSDL Component Model

The <code> namespaceDefault </code> <em> attribute information item </em> indicates SOAP protocol specification adds the default namespace following property to use the WSDL component model (as defined in [ WSDL 2.0 Core Language ]):

  • {soap underlying protocol}, an absolute URI as defined by [ IETF RFC 2396 ], to the Binding component.

2.4.3 XML Representation


<definitions >
  <binding  name="xs:NCName" interface="xs:QName"? type="xs:anyURI"
            wsoap:protocol="xs:anyURI" >
    ...
  </binding>
</definitions>

The XML representation for any operation contained within specifying the [ancestor] binding with <code> style </code> SOAP protocol is a REQUIRED attribute information item with deleted text: value "rpc". The <code> namespaceDefault </code> <em> attribute information item </em> has the following Infoset properties:

  • A [local name] of namespaceDefault protocol

  • A [namespace name] deleted text: which has no value </p> </li> <li> <p> An [owner] of <code> binding </code> in the namespace named "http://www.w3.org/2003/06/wsdl/soap12" "http://www.w3.org/2004/08/wsdl/soap12"

2.4.4 Mapping Between Component Properties and XML Representation

See Table 2-1 .


Table 2-1. Mapping between Binding Component Extension Properties and XML Representation
Property Mapping
{soap underlying protocol} The type actual value of the namespaceDefault wsoap:protocol attribute information item deleted text: </em> is <em> xsd:anyURI . The value of

2.5 Specifying the <code> namespaceDefault </code> <em> attribute information item </em> is Default SOAP MEP

2.5.1 Description

Every Binding Operation component of a SOAP binding MUST indicate the XML namespace SOAP Message Exchange Pattern (MEP) (see [ SOAP 1.2 Part 2: Adjuncts ]) to use for the 'wrapper' element be used for that operation. This binding specification allows the user to indicate a default SOAP Envelope body block(s). See below MEP to be used for more information on the semantics all Binding Operation components of the <code> namespace </code> <em> attribute information item </em>. this Binding component.

<a name="_soap_binding_encoding" id= "_soap_binding_encoding"> 2.1.4 <code> encodingStyleDefault </code> Attribute with <code> binding </code> [owner] 2.5.2 Relationship to WSDL Component Model

The deleted text: <code> encodingStyleDefault </code> <em> attribute information item </em> indicates the default encodingStyle to use for any operation contained within SOAP MEP specification is a syntactic convenience and does not affect the [ancestor] binding. underlying component model.

2.5.3 XML Representation


<definitions >
  <binding  name="xs:NCName" interface="xs:QName"? type="xs:anyURI"
            wsoap:protocol="xs:anyURI"
            wsoap:mepDefault="xs:anyURI ?" >
    ...
  </binding>
</definitions>

The <code> encodingStyleDefault </code> XML representation for specifying the default SOAP MEP is an OPTIONAL attribute information item has with the following Infoset properties:

  • A [local name] of encodingStyleDefault mepDefault

  • A [namespace name] deleted text: which has no value </p> </li> <li> <p> An [owner] of <code> binding </code> in the namespace named "http://www.w3.org/2003/06/wsdl/soap12" "http://www.w3.org/2004/08/wsdl/soap12"

2.6 Declaring SOAP Modules

2.6.1 Description

The type of the <code> encodingStyleDefault </code> <em> attribute information item </em> In SOAP, it is <em> xsd:anyURI </em>. permissible for specification interaction to engage one or more additional features (typically implemented as one or more SOAP header blocks), as defined by SOAP Modules (see [ SOAP 1.2 Part 1: Messaging Framework ]). This binding specification allows users to indicate which SOAP Modules are in use across the entire binding, on a per operation basis or on a per message basis.

2.6.2 Relationship to WSDL Component Model

The <code> encodingStyle </code> and <code> encodingStyleDefault </code> <em> attribute information item </em> s indicate how SOAP Module component adds the type description for following property to the SOAP Envelope WSDL component was derived. This information MAY be exploited by tools that generate data structures from model (as defined in [ WSDL 2.0 Core Language ]):

  • {soap modules} to the type description. Binding, Binding Operation and Binding Message Reference components.

The [normalized value] "http://www.w3.org/2003/05/soap-envelope/encoding/none" indicates that the type description was not derived as SOAP modules applicable for a function particular operation of a well-known encoding. The [normalized value] MUST NOT be "". any service consists of all modules specified in the input or output Binding Message reference components, and those specified within the Binding Operation components and those specified within the Binding component. If no <code> encodingStyleDefault </code> any module is declared in scope, multiple components, then the [normalized value] is "http://www.w3.org/2003/05/soap-envelope/encoding/none" </p> <p> For all [normalized value]s requiredness of the <code> encodingStyle </code> and <code> encodingStyleDefault </code> <em> attribute information item </em> s, the SOAP Envelope component(s) MUST be exactly as described that module is defined by the type description; closest declaration, where closeness is defined by whether it is specified directly at the writer of Binding Message Reference component level, the SOAP Envelope component(s) MUST it exactly as described by Binding Operation component level or the type description. Binding component level, respectively.

</div> <div class="div2"> <h3>

<a name="_soap_module" id="_soap_module"> 2.2 <code> module </code> Element with <code> binding </code> [parent] </h3> <div class="exampleInner"> <pre> <definitions > <binding > <<b>soap:module</b> uri="uri" required="boolean"? > </<b>soap:module</b>> </binding> </definitions> </pre> </div> 2.6.3 SOAP Module Component

The optional <code> SOAP Module component identifies a SOAP module </code> <em> element information item </em> indicates that is in use. The properties of the SOAP module(s) supported Module component are as follows:

  • {uri} An absolute URI as defined by a <code> binding </code> <em> element information item </em>. A [ IETF RFC 2396 ]. The value of this property identifies the specific SOAP module[ module that is in use, as defined in the SOAP Protocol Binding Framework section of [ <a href="#SOAP12-PART1"> SOAP 1.2 Part 1: Messaging Framework ] realizes zero or more SOAP features implemented as one or more ].

  • {required} A boolean indicating if the SOAP header blocks. module is required.

2.6.4 XML Representation


<definitions >
  <binding >
    <wsoap:module uri="uri"
                  required="boolean"? >
      <documentation ... />?
    </wsoap:module>
    <operation>
      <wsoap:module ... />*
      <input>
        <wsoap:module ... />*
      </input>
      <output>
        <wsoap:module ... />*
      </output>
    </operation>
  </binding>
</definitions>

The <code> module </code> XML representation for a SOAP Module component is an element information item has with the following Infoset properties:

  • A [local name] of module

  • A [namespace name] of "http://www.w3.org/2003/06/wsdl/soap12" </p> </li> <li> <p> A [parent] of <code> binding </code> in the namespace named "http://www.w3.org/2003/06/wsdl" "http://www.w3.org/2004/08/wsdl/soap12"

  • One or more attribute information item s amongst its [attributes] as follows:

    • A required REQUIRED uri attribute information item deleted text: as described below </p> </li> <li> <p> An optional <code> required </code> <em> attribute information item </em> as described below </p> </li> </ul> </li> </ul> <div class="div3"> <h4> <a name="_soap_module_uri" id="_soap_module_uri"> </a> 2.2.1 <code> uri </code> Attribute with deleted text: <code> module </code> [owner] </h4> <p> The <code> uri </code> <em> attribute information item </em> specifies the URI of the SOAP module for the [owner] <code> module </code> . The <code> uri </code> <em> attribute information item </em> has the following Infoset properties:

      • A [local name] of uri

      • A [namespace name] which has no value

    • An [owner] of <code> module </code> in the namespace named "http://www.w3.org/2003/06/wsdl/soap12" </p> </li> </ul> <p> The type of the <code> uri </code> <em> attribute information item </em> is <code> xsd:anyURI </code>. The value of the <code> uri </code> <em> attribute information item </em> is a URI that identifies a specific SOAP module. </p> </div> <div class="div3"> <h4> <a name="_soap_module_required" id= "_soap_module_required"> </a> 2.2.2 <code> required </code> Attribute with <code> binding </code> [owner] </h4> <p> The <code> required </code> <em> attribute information item </em> specifies whether the [owner] <code> module </code> is required by the [parent] binding. The OPTIONAL required attribute information item has with the following Infoset properties:

      • A [local name] of required

      • A [namespace name] which has no value

    • An [owner] of <code> module </code> in the Zero or more namespace named "http://www.w3.org/2003/06/wsdl/soap12" </p> </li> </ul> <p> The type of the <code> required </code> <em> attribute information item </em> is <code> xsd:boolean </code>. </p> <p> Omitting this qualified attribute information item is defined as being semantically equivalent to including it with a value of "false". </p> </div> </div> <div class="div2"> <h3> <a name="_soap_property" id="_soap_property"> </a> 2.3 <code> propertyConstraint </code> Element with <code> module </code> [parent] </h3> <div class="exampleInner"> <pre> <definitions> <binding> <soap:module> <<b>soap:propertyConstraint</b> uri="uri" type="qname"? /> </soap:module> </binding> </definitions> </pre> </div> <p> The optional <code> propertyConstraint </code> <em> element information item </em> indicates SOAP module(s) supported by a <code> module </code> <em> element information item </em>. </p> <p> s. The <code> propertyConstraint </code> [namespace name] of such element attribute information item has the following Infoset properties: </p> <ul> <li> <p> A [local name] of <code> propertyConstraint </code> </p> </li> <li> <p> A [namespace name] of "http://www.w3.org/2003/06/wsdl/soap12" s MUST NOT be "http://www.w3.org/2004/08/wsdl" and MUST NOT be "http://www.w3.org/2004/08/wsdl/soap12".

    • <li> <p> A [parent] of <code> module </code> in the namespace named "http://www.w3.org/2003/06/wsdl" </p>
  • One Zero or more attribute element information item deleted text: s amongst its [attributes] [children], in order, as follows:

    <ul> <li> <p> A required <code> uri </code> <em> attribute information item </em> as described below </p> </li>
    1. An optional OPTIONAL type documentation attribute element information item as described below defined in [ WSDL 2.0 Core Language ].

    2. </ul> </li> </ul>
    3. The value of the <code> propertyConstraint </code> Zero or more namespace-qualified element information item is the value that is required for the SOAP property of the [parent] <code> module </code> . </p> <p> s amongst its [children]. The <code> propertyConstraint </code> [namespace name] of such element information item has no [children]. s MUST NOT be "http://www.w3.org/2004/08/wsdl" and MUST NOT be "http://www.w3.org/2004/08/wsdl/soap12".

<a name="_soap_property_uri" id="_soap_property_uri"> 2.3.1 <code> uri </code> Attribute with <code> propertyConstraint </code> [owner] 2.6.5 Mapping Between Component Properties and XML Representation

The <code> uri </code> <em> attribute information item </em> specifies the URI of the SOAP property for the [ancestor] <code> module </code> . The <code> uri </code> <em> attribute information item </em> has the following Infoset properties: See Table 2-2 .

<ul> <li> <p> A [local name] of <code> uri </code> </p> </li> <li> <p> A [namespace name] which has no value </p> </li> <li> <p> An [owner] of <code> propertyConstraint </code> in the namespace named "http://www.w3.org/2003/06/wsdl/soap12" </p> </li> </ul> <p>
Table 2-2. Mapping between SOAP Module Component Properties and XML Representation
Property Mapping
{uri} The type actual value of the uri attribute information item </em> is <code> xsd:anyURI </code>. .
{required} The actual value of the uri required attribute information item </em> is .

2.7 Binding Faults

2.7.1 Description

For every Interface Fault component contained in an Interface component, a URI that identifies mapping to a deleted text: specific SOAP property for Fault must be described. This binding specification allows the [ancestor] <code> module </code> . user to indicate the SOAP fault code and subcodes that are transmitted for a given Interface Fault component.

<a name="_soap_property_type" id= "_soap_property_type"> 2.3.2 <code> type </code> Attribute with <code> propertyConstraint </code> [owner] 2.7.2 Relationship to WSDL Component Model

The <code> type </code> <em> attribute information item </em> specifies the type of the value of the [owner] <code> propertyConstraint </code> . The <code> type </code> <em> attribute information item </em> has SOAP Fault binding adds the following Infoset properties: properties to the WSDL component model (as defined in [ WSDL 2.0 Core Language ]):

  • A [local name] of <code> type </code> {soap fault code}, a QName as defined by [ </p> </li> <li> <p> A [namespace name] which has no XML 1.0 ], to the Binding Fault component. The value deleted text: </p> </li> <li> <p> An [owner] of <code> propertyConstraint </code> in this property identifies a possible SOAP fault (see [ SOAP 1.2 Part 1: Messaging Framework ]) for the namespace named "http://www.w3.org/2003/06/wsdl/soap12" operation in scope.

  • </ul>
  • The type {soap fault subcodes}, a list of QNames, to the <code> type </code> <em> attribute information item </em> is <code> xsd:QName </code>. Binding Fault component. The value of the <code> type </code> <em> attribute information item </em> is XML Qualified Name that this property identifies the type of the value one or more subcodes for the [owner] <code> propertyConstraint </code> . this SOAP fault.

</div> <div class="div2"> <h3>

<a name="_soap_operation" id="_soap_operation"> 2.4 <code> operation </code> Element with <code> operation </code> [parent] </h3> 2.7.3 XML Representation



<definitions>
 <binding>
  <operation>
   <<b>soap:operation</b> style="document|rpc"? 
                   soapAction="uri"? /> ?
  </operation>
 </binding>



<definitions >
  <binding >
    <fault ref="xs:QName"
           wsoap:code="xs:QName"
           wsoap:subcodes="list of xs:QName"? />
    </fault>*
  </binding>


</definitions>

The optional <code> operation </code> <em> element information item </em> provides binding information XML representation for the [parent] operation. The <code> operation </code> binding a SOAP Fault are two element attribute information item has s with the following Infoset properties:

  • wsoap:code REQUIRED attribute information item

    • A [local name] of operation code

    • A [namespace name] of "http://www.w3.org/2003/06/wsdl/soap12" </p> </li> <li> <p> A [parent] of <code> operation </code> in the namespace named "http://www.w3.org/2003/06/wsdl" "http://www.w3.org/2004/08/wsdl/soap12"

    • <li> <p> Zero or more <em> attribute information item </em> s amongst its [attributes] as follows: </p> <ul> <li> <p> An optional <code> style </code> <em> attribute information item </em> as described below </p>
  • An optional <code> soapAction </code> wsoap:subcodes OPTIONAL attribute information item deleted text: as described below </p> </li> </ul> </li> </ul> <p> The <code> operation </code> <em> element information item </em> has no [children]. </p> <p> If the <code> operation </code> <em> element information item </em> has no [attributes], it MAY be omitted. </p> <div class="div3"> <h4> deleted text: <a name="_soap_operation_style" id= "_soap_operation_style"> </a> 2.4.1 <code> style </code> Attribute with <code> operation </code> [owner] </h4> <p> The <code> style </code> <em> attribute information item </em> indicates the serialization style of the <code> operation </code> owner. The <code> style </code> <em> attribute information item </em> has the following Infoset properties:

    • A [local name] of style subcodes

    • A [namespace name] deleted text: which has no value </p> </li> <li> <p> An [owner] of <code> operation </code> in the namespace named "http://www.w3.org/2003/06/wsdl/soap12" "http://www.w3.org/2004/08/wsdl/soap12"

2.7.4 Mapping Between Component Properties and XML Representation

See Table 2-3 .


Table 2-3. Mapping between SOAP Fault Component Properties and XML Representation
Property Mapping
{soap fault code} The type actual value of the style code attribute information item deleted text: </em> is <em> xsd:string . </p> <p>
{soap fault subcodes} The actual value of the style subcodes attribute information item </em> indicates whether the [owner] operation is serialized according to a document-oriented style (message contains document(s)) or remote-procedure-call (RPC) oriented style (message contains parameter(s) and/or return value(s)). This information may be used to select .

2.8 Binding Operations

2.8.1 Description

For every Interface Operation component contained in an appropriate programming model. The value of this <em> attribute information item </em> also affects the way Interface component, in which the <code> Fault </code> of addition to the SOAP message is constructed, as explained default binding rules described in section <a href="#_soap_body"> 2.5 body Element with input or output [parent] 2.3 Default Binding Rules </a> . If the <code> style </code> <em> attribute ,there may be additional binding information deleted text: item </em> is not specified, it defaults to be specified. This binding specification allows the value specified in user to indicate the [ancestor] <code> binding </code> <em> element information item </em> in SOAP Message Exchange Pattern (MEP) and a value for the namespace named "http://www.w3.org/2003/06/wsdl/soap12". SOAP Action Feature (see [ SOAP 1.2 Part 2: Adjuncts ]) on a per-operation basis.

<a name="_soap_operation_action" id= "_soap_operation_action"> 2.4.2 <code> soapAction </code> Attribute with <code> operation </code> [owner] 2.8.2 Relationship to WSDL Component Model

<table border="1" summary="Editorial note: JCS"> <tr> <td width="50%" valign="top" align="left"> <b> Editorial note: JCS </b> </td> <td width="50%" valign="top" align="right"> 20030115 </td> </tr> <tr> <td valign="top" align="left" colspan="2">

The SOAP 1.2 HTTP Operation binding does not define a SOAPAction HTTP header. This is a known issue. </td> </tr> </table> <p> The <code> soapAction </code> <em> attribute information item </em> specifies the value of the HTTP SOAPAction header for the <code> operation </code> owner. The <code> soapAction </code> <em> attribute information item </em> has specification adds the following Infoset properties: property to the WSDL component model (as defined in [ WSDL 2.0 Core Language ]):

  • A [local name] of <code> soapAction </code> {soap mep}, an absolute URI as defined by [ </p> </li> <li> <p> A [namespace name] which has no value </p> </li> <li> <p> An [owner] of <code> operation </code> in the namespace named "http://www.w3.org/2003/06/wsdl/soap12" </p> </li> </ul> <p> The type of IETF RFC 2396 ], to the <code> soapAction </code> <em> attribute information item </em> is <em> xsd:anyURI </em>. </p> <p> Binding Operation component. The value of this property identifies the <code> soapAction </code> <em> attribute information item </em> is the URI to be included in the HTTP SOAPAction header SOAP Message Exchange Pattern (MEP) (as defined by [ SOAP 1.2 Part 1: Messaging Framework ]) for the [owner] this specific operation. This URI If no specific value should be used directly as is assigned, then the value for assigned by the HTTP SOAPAction header; no attempt should be made default rules apply (see 2.3 Default Binding Rules ). It is an error for this property to make not have a deleted text: relative URI value absolute when making (which MAY happen if the request. For default rules are not applicable).

  • {soap action}, an absolute URI as defined by [ IETF RFC 2396 ], to the HTTP protocol binding Binding Operation component. The value of deleted text: SOAP, this property identifies the value is required (it has no default value). For other of the SOAP protocol bindings, it MUST NOT be specified. Action Feature (as defined by [ SOAP 1.2 Part 1: Messaging Framework ]) for this specific operation.

</div> <div class="div2"> <h3>

<a name="_soap_body" id="_soap_body"> 2.5 <code> body </code> Element with <code> input </code> or <code> output </code> [parent] </h3> 2.8.3 XML Representation



<definitions>
 <binding>
  <operation>
   [ <input> | <output> ]
    <<b>soap:body</b> namespace="uri"?
               encodingStyle="uri"? /> ?
   [ </input> | </output> ]
  </operation>
 </binding>



<definitions >
  <binding >
    <operation ref="xs:QName" 
               wsoap:mep="xs:anyURI"?
               wsoap:action="xs:anyURI"? >
    </operation>
  </binding>


</definitions>

The optional <code> body </code> <em> element information item </em> specifies properties of the SOAP Envelope body block(s) XML representation for the [parent] operation. The <code> body </code> binding an Operation are two element attribute information item has s with the following Infoset properties:

  • wsoap:mep OPTIONAL attribute information item

    • A [local name] of body mep

    • A [namespace name] of "http://www.w3.org/2003/06/wsdl/soap12" "http://www.w3.org/2004/08/wsdl/soap12"

    • <li> <p> A [parent] of <code> input </code> or <code> output </code> in the namespace named "http://www.w3.org/2003/06/wsdl" </p>
  • Zero or more wsoap:action OPTIONAL attribute information item s amongst its [attributes] as follows:

    • An optional A [local name] of namespace action <em> attribute information item </em> as described below

    • An optional <code> encodingStyle </code> <em> attribute information item </em> as described below A [namespace name] of "http://www.w3.org/2004/08/wsdl/soap12"

2.8.4 Mapping Between Component Properties and XML Representation

See Table 2-4 .


Table 2-4. Mapping between SOAP Operation Component Properties and XML Representation
Property Mapping
{soap mep} The actual value of the body wsoap:mep element attribute information item </em> has no [children]. </p> <p> ,if present. If not, the actual value of the body wsoap:mepDefault element attribute information item has no [attributes], it MAY be omitted. </p> <p> The <code> body </code> of the parent wsdl:binding element information item </em> provides information on how to assemble the different message parts inside ,if present. If not the <code> Fault </code> element of value as defined by the default SOAP Envelope. binding rules (see 2.3 Default Binding Rules ), if applicable.
{soap action} The actual value of the body action element attribute information item </em> is used .,if any.

3. WSDL HTTP Binding

The HTTP binding described in both RPC-oriented and document-oriented messages, but the style of the enclosing operation has important effects on how the <code> Fault </code> this section is structured: </p> <ul> <li> <p> If an extension for [ WSDL 2.0 Core Language ] to enable Web Services applications to use HTTP 1.1 [ IETF RFC 2616 ] (as well as other versions of HTTP) and HTTPS [ IETF RFC 2818 ]. This binding extends WSDL 2.0 by adding properties to the operation style is rpc each part component model defined in [ WSDL 2.0 Core Language ]. In addition an XML Infoset representation for these additional properties is provided, along with a parameter or mapping from that representation to the various component properties.

As allowed in [ WSDL 2.0 Core Language ], a return value and appears inside Binding component MAY exist without indicating a wrapper element within specific Interface component that it applies to. In this case there MUST NOT be any Binding Operation or Binding Fault components present in the body. Binding component.

The wrapper element is named identically to the operation name and its namespace HTTP binding is designed with the value objective of the namespace attribute. Each message part (parameter) appears under the wrapper, represented minimizing what needs to be explicitly declared for common cases. This is achieved by defining a set of default rules which apply for all Interface Operation components of an accessor named identically Interface component, unless specifically overidden on a per Interface Operation basis. Thus, if a given Interface Operation component is not referred to specifically, then all the corresponding parameter of the call. Parts are arranged in the same order as default rules apply for that component. That is, per the parameters requirements of the call. [ WSDL 2.0 Core Language ] all operations of an Interface component are bound by this binding.

deleted text: </li> <li>

If the operation style is document Notice that there are no additional wrappers, default binding rules defined for Fault components by this binding. Thus, if a given Interface component has any Fault components, then such Interface components MUST be bound via Binding components which indicate a specific interface and contain as many Binding Fault components as there are Fault components in the message parts appear directly under the SOAP <code> Interface Fault </code> element. component.

deleted text: </li> </ul>

[ Definition : The same mechanisms are used to define the content internal tree representation of the <code> Fault </code> an input, output or fault message is called an instance data , and parameter accessor elements. </p> <p> Each part references a concrete is constrained by the schema definition using either the <code> element </code> or <code> type </code> <em> attribute information item </em>. In associated the first case, message: the XML element referenced by the part will appear directly under the <code> Body </code> SOAP Envelope element (for document style bindings) or under an accessor element named after the message part (in rpc style). In the second, the type referenced by the part becomes in the schema type {element} property of the enclosing element ( <code> Body </code> Message Reference component for document style or part accessor element input and output messages, and in the {element} property of an Interface Fault component for rpc style). faults.]

<div class="div3"> <h4>

<a name="_soap_body_name" id="_soap_body_name"> 2.5.1 <code> namespace </code> Attribute with <code> body </code> [owner] </h4> 3.1 Identifying an HTTP Binding

The <code> namespace </code> <em> attribute information item </em> defines A Binding component (defined in [ WSDL 2.0 Core Language ]) is identified as an HTTP binding by assigning the XML namespace value "http://www.w3.org/2004/08/wsdl/http" to deleted text: use for the SOAP body block(s) for the [ancestor] <code> operation </code> . The <code> namespace </code> <em> attribute information item </em> has {type} property of the following Infoset properties: Binding component.

3.2 HTTP Syntax Summary (Non-Normative)


<definitions >
  <binding name="xs:NCName" interface="xs:QName"? type="xs:anyURI"
           whttp:methodDefault="xs:string"?
           whttp:cookies="xs:boolean"?
           whttp:version="xs:string"?
           whttp:defaultTransferCoding="xs:string"? >
   <documentation />?

    <fault ref="xs:QName"
           whttp:code="xs:int"? >
      <documentation />?
    </fault>*

    <operation ref="xs:QName" 
               whttp:location="xs:anyURI"?
               whttp:method="xs:string"? 
               whttp:inputSerialization="xs:string"? 
               whttp:outputSerialization="xs:string"? 
               whttp:faultSerialization="xs:string"? 
               whttp:defaultTransferCoding="xs:string"? >
          <documentation />?

      <input messageLabel="xs:NCName"? 
             whttp:transferCoding="xs:string? >
        <documentation />?>*
        <feature ... />*
        <property ... />*
      </input>*

      <output messageLabel="xs:NCName"?
              whttp:transferCoding="xs:string? >
        <documentation />?
        <feature ... />*
        <property ... />*
      </output>*
    </operation>*

  </binding>

  <service>
    <endpoint name="xs:NCName" binding="xs:QName" address="xs:anyURI"?
              whttp:authenticationType="xs:string"? 
              whttp:authenticationRealm="xs:string"? >
      <documentation />?
    </endpoint>
  </service>
</definitions>

3.3 Default Binding Rules

  • deleted text: A [local name] of <code> namespace </code> deleted text: </p> </li> <li> <p> A [namespace name] which has no value </p> </li> <li> <p> An [owner] of <code> body </code> in the namespace named "http://www.w3.org/2003/06/wsdl/soap12" </p> </li> </ul> <p> The type of the <code> namespace </code> <em> attribute information item </em> is <em> xsd:anyURI </em>. The value of the <code> namespace </code> attribute information item HTTP Method Declaration. is When formulating the XML namespace HTTP message to use for the 'wrapper' element for the SOAP Envelope body block(s). </p> <p> If the value of be transmitted, the <code> style </code> <em> attribute information item </em> HTTP request method MUST be what is "document", then defined by the namespace whttp:method deleted text: <em> attribute information item </em> with [owner] <code> body </code> is not applicable. </p> </div> <div class="div3"> <h4> <a name="_soap_body_encoding" id= "_soap_body_encoding"> </a> 2.5.2 on encodingStyle operation Attribute , or with the body </code> [owner] </h4> <p> The <code> encodingStyle whttp:defaultMethod deleted text: <em> attribute information item </em> indicates the encoding style </p> <p> that was used to generate type description for the SOAP body block(s) for the [ancestor] on operation binding .

  • The <code> encodingStyle </code> attribute information item Payload construction. has When formulating the following Infoset properties: </p> <ul> <li> <p> A [local name] HTTP message to be transmitted, the contents of <code> encodingStyle </code> </p> </li> <li> <p> A [namespace name] which has no value </p> </li> <li> <p> An [owner] the payload (i.e. the contents of deleted text: <code> body </code> in the namespace named "http://www.w3.org/2003/06/wsdl/soap12" HTTP message body) MUST be what is defined by the corresponding Message Reference or Interface Fault components:

    </li> </ul>
    • The type Message Reference component: if the value of the <code> encodingStyle </code> <em> attribute information item </em> {message content model} property is xsd:anyURI </em>. </p> <p> The [normalized value] "http://www.w3.org/2003/05/soap-envelope/encoding/none" indicates that #any then the type description has not been derived as a function of a well-known encoding. The [normalized value] MUST NOT payload MAY be "". any one XML element. If no <code> encodingStyle </code> the value is in scope, #none then the [normalized value] is payload MUST be empty. Finally if the <code> encodingStyleDefault </code> <em> attribute information item </em>. </p> </div> </div> <div class="div2"> <h3> <a name="_soap_header" id="_soap_header"> </a> 2.6 <code> header </code> Element with <code> input </code> or <code> output </code> [parent] </h3> <div class="exampleInner"> <pre> <definitions> <binding> <operation> [ <input> | <output> ] <<b>soap:header</b> element="qname"? type="qname"? localname="nmtoken"? namespace="uri"? encodingStyle="uri"? role="uri"? />* [ </input> | </output> ] </operation> </binding> </definitions> </pre> </div> <p> The optional <code> header </code> value is element information item #element specifies SOAP header block(s) for then the payload will be the deleted text: [ancestor] operation. The <code> header </code> element information item has identified by the following Infoset properties: </p> <ul> <li> <p> A [local name] of <code> header </code> </p> </li> <li> <p> A [namespace name] of "http://www.w3.org/2003/06/wsdl/soap12" {element} property.

    • A [parent] of <code> input </code> or <code> output </code> in Interface Fault component: the payload will be the deleted text: namespace named "http://www.w3.org/2003/06/wsdl" </p> </li> <li> <p> One or more deleted text: attribute information item </em> s amongst its [attributes] as follows: </p> <ul> <li> <p> An optional <code> element deleted text: </code> <em> attribute information item as described below </p> </li> <li> <p> An optional <code> type </code> <em> attribute information item </em> as described below </p> </li> <li> <p> An optional <code> localname </code> <em> attribute information item </em> as described below </p> </li> <li> <p> An optional <code> namespace </code> <em> attribute information item </em> as described below </p> </li> <li> <p> An optional <code> encodingStyle </code> <em> attribute information item </em> as described below </p> </li> <li> <p> An optional <code> role </code> <em> attribute information item </em> as described below identified by the {element} property.

    deleted text: </li> </ul>

    The <code> header </code> <em> element information item </em> has no [children]. </p> <p> The <code> header </code> <em> element information item </em> allow headers to be defined that are transmitted as SOAP header blocks. It If the Message Reference component or the Interface Fault component is not necessary to exhaustively list all header blocks that appear declared using a non-XML type system (as considered in the SOAP Envelope using <code> header </code> <em> element information item </em> s. For example, extensions (see <a href= "http://www.w3.org/TR/2003/WD-wsdl12-20030611#language-extensibility"> Language Extensibility and Binding </a>, Types section of [ <a href= "#WSDL-PART1"> WSDL 1.2 2.0 Core Language ], section 4) to WSDL may imply specific headers should ]) then additional binding rules MUST be added defined to the actual payload, and it is not required indicate how to list map those headers here. components into the HTTP envelope.

  • Exactly one of the <code> element </code> and <code> type </code> attribute information item Serialization format. s The HTTP request serialization format MUST be specified. what is defined by the {http input serialization} property. The <code> localname </code> and <code> namespace </code> <em> attribute information item </em> s HTTP response serialization format MUST be specified if and only if what is defined by the <code> type </code> <em> attribute information item </em> {http output serialization} property. The HTTP serialization format of a fault MUST be what is specified. defined by the {http fault serialization} property.

    <div class="div3"> <h4>

    Section <a name="_soap_header_element" id= "_soap_header_element"> 3.8 Serialization format of instance data 2.6.1 <code> element </code> Attribute defines serialization formats supported by this binding along with <code> header </code> [owner] </h4> their constraints.

  • The <code> element </code> attribute information item Default input and output serialization format. refers to an XML Schema element declaration component that Table 3-1 defines the SOAP header block default values for the [owner] <code> header </code> . The <code> element </code> <em> attribute information item </em> has the following Infoset properties: </p> <ul> <li> <p> A [local name] of <code> element </code> </p> </li> <li> <p> A [namespace name] which has no value </p> </li> <li> <p> An [owner] of <code> header </code> in the namespace named "http://www.w3.org/2003/06/wsdl/soap12" </p> </li> </ul> <p> The type GET, POST, PUT and DELETE values of the <code> element </code> <em> attribute information item </em> is <em> xsd:QName </em>. {http method} property.

    </div> <div class="div3"> <h4> <a name="_soap_header_type" id="_soap_header_type"> 2.6.2
    Table 3-1. Default values for GET, POST, PUT and DELETE
    HTTP Method Default Input Serialization Default Output Serialization
    {http method} {http input serialization} {http output serialization}
    GET type application/x-www-form-urlencoded Attribute with header application/xml [owner] </h4> <p> The
    POST type application/xml <em> attribute information item </em> refers to an XML Schema type description that defines the SOAP header block for the [owner] header application/xml . The
    PUT type application/xml <em> attribute information item </em> has the following Infoset properties: </p> <ul> <li> <p> A [local name] of type application/xml </p> </li> <li> <p> A [namespace name] which has no value </p> </li> <li> <p> An [owner] of
    DELETE header application/x-www-form-urlencoded in the namespace named "http://www.w3.org/2003/06/wsdl/soap12" </p> </li> </ul> <p> The type of the type application/xml <em> attribute information item </em> is <em> xsd:QName </em>.

    Note:

    The namespace application/x-www-form-urlencoded <em> attribute information item </em> is used in serialization format places constraints on the same way as with stype of the <code> body </code> <em> element information item </em> interface operation bound (see section <a href="#_soap_body"> 2.5 body Element with input or output [parent] 3.8.1 Serialization as application/x-www-form-urlencoded ), only <code> style </code> ="document" is assumed since headers do not contain parameters. ).

    The schema referenced MAY include definitions default vales for the <code> actor </code> {http input serialization} and {http output serialization} properties for any other {http method} is mustUnderstand </code> <em> attribute information item </em> in the namespace named "http://www.w3.org/2003/05/soap-envelope". application/xml .

    deleted text: </div> <div class="div3"> <h4> <a name="_soap_header_localname" id= "_soap_header_localname"> </a> 2.6.3 <code> localname </code> Attribute with <code> header </code> [owner] </h4>

    The <code> localname </code> <em> attribute information item </em> defines Mechanisms that are outside the localname scope of this specification MAY modify the SOAP header block for serialization format of the [owner] <code> header </code> when it has a <code> type </code> <em> attribute information item </em>. The <code> localname </code> <em> attribute information item </em> has instance data corresponding to the following Infoset properties: </p> <ul> <li> <p> A [local name] output message. An example of such modification is the combination of the serialization as localname application/x-www-form-urlencoded and the SOAP-Response Message Exchange Pattern ([ SOAP 1.2 Part 2: Adjuncts ], Section 6.3).

  • A [namespace name] which has no value </p> </li> <li> <p> An [owner] Accept headers. Standard HTTP accept headers (see section 14 of [ IETF RFC 2616 ]) MAY be used in an HTTP request. When constructing an HTTP header Accept in header, the namespace named "http://www.w3.org/2003/06/wsdl/soap12" </p> </li> </ul> <p> The type of requester agent MAY take into account the localname expectedMediaType deleted text: <em> attribute information item </em> (see [ MTXML ]) appearing on an output message description to find out about the type of binary element content which is <em> xsd:NCName </em>. expected to be sent by the provider agent.

3.4 Specifying the HTTP Version

<a name="_soap_header_namespace" id= "_soap_header_namespace"> 2.6.4 <code> namespace </code> Attribute with <code> header </code> [owner] 3.4.1 Description

The <code> namespace </code> <em> attribute information item </em> defines the XML namespace Every Binding component MUST indicate what version of the SOAP header block HTTP is in use for the [owner] <code> header </code> when it has a <code> type </code> <em> attribute information item </em>. The <code> namespace </code> <em> attribute information item </em> has the following Infoset properties: </p> <ul> <li> <p> A [local name] of <code> namespace </code> </p> </li> <li> <p> A [namespace name] which has no value </p> </li> <li> <p> An [owner] operations of deleted text: <code> header </code> in the namespace named "http://www.w3.org/2003/06/wsdl/soap12" interface that this binding applies to.

deleted text: </li> </ul>

The type of the <code> namespace </code> <em> attribute information item </em> By default, HTTP/1.1 [ IETF RFC 2616 ] is <em> xsd:anyURI </em>. used.

<a name="_soap_header_encoding" id= "_soap_header_encoding"> 2.6.5 <code> encodingStyle </code> Attribute with <code> header </code> [owner] 3.4.2 Relationship to WSDL Component Model

The <code> encodingStyle </code> <em> attribute information item </em> indicates HTTP binding specification adds the encoding style </p> <p> that was used following property to deleted text: generate type description for the SOAP header block(s) for the [ancestor] <code> operation </code> . </p> <p> The <code> encodingStyle </code> <em> attribute information item </em> has the following Infoset properties: </p> <ul> <li> <p> A [local name] of <code> encodingStyle </code> WSDL component model (as defined in [ WSDL 2.0 Core Language ]):

</li>
  • A [namespace name] which has no {http version}, a string value </p> </li> <li> <p> An [owner] of <code> header </code> in to the namespace named "http://www.w3.org/2003/06/wsdl/soap12" Binding component.

deleted text: <p> The type of the <code> encodingStyle </code> <em> attribute information item </em> is <em> xsd:anyURI </em>. </p> <p> The [normalized value] "http://www.w3.org/2003/05/soap-envelope/encoding/none" indicates that the type description has not been derived as a function of a well-known encoding. The [normalized value] MUST NOT be "". If no <code> encodingStyle </code> is in scope, then the [normalized value] is the <code> encodingStyleDefault </code> <em> attribute information item </em>. </p>

<a name="_soap_header_role" id="_soap_header_role"> 2.6.6 <code> role </code> Attribute with <code> header </code> [owner] 3.4.3 XML Representation


<definitions >
  <binding name="xs:NCName" interface="xs:QName"? type="xs:anyURI"
           whttp:version="xs:string"? >
  </binding>
</definitions>

The optional <code> role </code> <em> attribute information item </em> identifies XML representation for specifying the SOAP role to which a SOAP header block HTTP version is targeted. The <code> role </code> an optional attribute information item has: with the following Infoset properties:

  • A [local name] of role version

  • A [namespace name] which has no value of "http://www.w3.org/2004/08/wsdl/http"

  • A [specified] property with a value type of "true" wsdls:string

  • An [owner] A default value of <code> header </code> in the namespace named "http://www.w3.org/2003/06/wsdl/soap12" "1.1"

3.4.4 Mapping Between Component Properties and XML Representation

See Table 3-2 .


Table 3-2. Mapping between Binding Component Extension Properties and XML Representation
Property Mapping
{http version} The type actual value of the role whttp:version attribute information item </em> .

3.5 Specifying the Default HTTP Method

3.5.1 Description

Every Binding Operation component MUST indicate what HTTP method is <code> xsd:anyURI </code>. The value in use for the operations of the <code> role </code> <em> attribute information item </em> is a URI that names a role interface that this binding applies to. This binding specification allows the user to indicate a SOAP node can assume. It SHOULD NOT default HTTP method to be a relative URI. used for all Binding Operation components of this Binding component.

3.5.2 Relationship to WSDL Component Model

A <code> role </code> <em> attribute information item </em> that is either absent or has an empty value The default HTTP method specification is deleted text: equivalent to indicating a value of "http://www.w3.org/2003/05/soap-envelope/role/ultimateReceiver", i.e., targeting syntactic convenience and does not affect the SOAP header block to an ultimate SOAP receiver. underlying component model.

</div> <div class="div2"> <h3>

<a name="_soap_headerfault" id="_soap_headerfault"> 2.7 <code> headerfault </code> Element with <code> input </code> or <code> output </code> [parent] </h3> 3.5.3 XML Representation



<definitions>
 <binding>
  <operation>
    [ <input> | <output> ]
    <<b>soap:headerfault</b> message="qname"
                      part="nmtoken"
                      namespace="uri"?
                      encodingStyle="uri"? />*
    [ </input> | </output> ]
  </operation>
 </binding>



<definitions >
  <binding name="xs:NCName" interface="xs:QName"? type="xs:anyURI"
           whttp:defaultMethod="xs:string"? >
  </binding>


</definitions>
deleted text: <table border="1" summary="Editorial note: JJM"> <tr> <td width="50%" valign="top" align="left"> <b> Editorial note: JJM </b> </td> <td width="50%" valign="top" align="right"> 2003/05/23 </td> </tr> <tr> <td valign="top" align="left" colspan="2"> This section has not yet been finalized. </td> </tr> </table>

The optional <code> headerfault </code> <em> element information item </em> specifies SOAP fault header block(s) XML representation for deleted text: the [ancestor] operation. The SOAP specification states that errors pertaining to header blocks have to be returned in header blocks, and this mechanism allows specifying the format of such fault header blocks. </p> <p> The <code> headerfault </code> default HTTP method is an optional element attribute information item has with the following Infoset properties:

  • A [local name] of headerfault defaultMethod

  • A [namespace name] of "http://www.w3.org/2003/06/wsdl/soap12" "http://www.w3.org/2004/08/wsdl/http"

  • A [parent] type of deleted text: <code> input </code> or <code> output </code> in the namespace named "http://www.w3.org/2003/06/wsdl" </p> </li> <li> <p> One or more attribute information item </em> s amongst its [attributes] as follows: </p> <ul> <li> <p> A mandatory <code> message </code> <em> attribute information item </em> as described below. </p> </li> <li> <p> A mandatory <code> part </code> <em> attribute information item </em> as described below. </p> </li> <li> <p> An optional <code> namespace </code> <em> attribute information item wsdls:string as described below.

  • An optional <code> encodingStyle </code> <em> attribute information item </em> as described below. No default value

</li> </ul>

3.6 Binding Operations

3.6.1 Description

The <code> headerfault </code> <em> element information item </em> This binding specification provides a binding to HTTP of Interface Operation components whose {message exchange pattern} property has no [children]. the value 'http://www.w3.org/2004/08/wsdl/in-only', 'http://www.w3.org/2004/08/wsdl/robust-in-only' or 'http://www.w3.org/2004/08/wsdl/in-out'.

The <code> headerfault </code> <em> element information item </em> allows fault headers For every Binding operation component corresponding to be defined that are transmitted as SOAP fault header blocks, and that carry information pertaining such Interface Operation components, this binding specification allows the user to indicate the faulty SOAP header block defined by HTTP method to use, the corresponding <code> header </code> . </p> <p> The <code> namespace </code> <em> attribute information item </em> s MUST be specified if input, output and fault serialization, and deleted text: only if the <code> type </code> <em> attribute information item </em> is specified. location of the bound operation.

<a name="_soap_headerfault_message" id= "_soap_headerfault_message"> 2.7.1 <code> message </code> Attribute with <code> headerfault </code> [owner] 3.6.2 Relationship to WSDL Component Model

The <code> message </code> <em> attribute information item </em> refers to an XML Schema element declaration HTTP Operation component that defines adds the SOAP fault header block for following property to the [owner] <code> headerfault </code> . The <code> message </code> <em> attribute information item </em> has Binding Operation component of the following Infoset properties: WSDL component model (as defined in [ WSDL 2.0 Core Language ]):

  • A [local name] of <code> message </code> {http location}, an absolute or relative URI as defined by [ </p> </li> <li> <p> A [namespace name] which has no IETF RFC 2396 ]. The value deleted text: </p> </li> <li> <p> An [owner] of <code> headerfault </code> in this property specifies a template for the namespace named "http://www.w3.org/2003/06/wsdl/soap12" </p> </li> </ul> <p> The type relative portion of the <code> message </code> <em> attribute information item </em> request URI for an operation. This URI is <em> xsd:QName </em>. </p> </div> <div class="div3"> <h4> <a name="_soap_headerfault_part" id= "_soap_headerfault_part"> </a> 2.7.2 <code> part </code> Attribute combined with <code> headerfault </code> [owner] </h4> <p> The <code> part </code> <em> attribute information item </em> refers the base URI specified in the {address} property of the endpoint element to an XML Schema type description that defines form the SOAP header block full URI for the [owner] <code> headerfault </code> . The <code> part </code> <em> attribute information item </em> has HTTP request to invoke the following Infoset properties: operation. It MUST contain an absolute or a relative URI, i.e. it MUST NOT include a fragment identifier in the URI.

    deleted text: <ul> <li>

    A [local name] of If the resulting URI uses the part https scheme, then HTTP over TLS [ IETF RFC 2818 ] is used to send the HTTP request.

  • A [namespace name] which has no {http method}, a string value </p> </li> <li> <p> An [owner] of <code> headerfault </code> in indicating, if present, the namespace named "http://www.w3.org/2003/06/wsdl/soap12" </p> </li> </ul> <p> The type of value for the <code> part </code> <em> attribute information item </em> is <em> xsd:QName </em>. </p> <p> The <code> namespace </code> <em> attribute information item </em> is used in HTTP Request Method for this specific operation. Otherwise, the same way default HTTP method as with the <code> body </code> <em> element information item </em> (see section <a href="#_soap_body"> defined in 2.5 body Element with input or output [parent] 3.5 Specifying the Default HTTP Method ), only <code> style </code> ="document" is assumed since headers do not contain parameters. applies. One or the other MUST be present

  • The schema referenced MAY include definitions {http input serialization}, a string value indicating, if present, the value for the <code> role </code> and <code> mustUnderstand </code> <em> attribute information item </em> in serialization of the namespace named "http://www.w3.org/2003/05/soap-envelope". </p> </div> <div class="div3"> <h4> HTTP Request message for this specific operation. Its value MUST be the name of a IANA media type token. If not present, the default input serialization associated with the {http method} property applies, as specified in <a name="_soap_headerfault_namespace" id= "_soap_headerfault_namespace"> 3.3 Default Binding Rules </a> 2.7.3 <code> namespace </code> Attribute with <code> headerfault </code> [owner] </h4> .

  • The <code> namespace </code> <em> attribute information item </em> defines {http output serialization}, a string value indicating, if present, the XML namespace value for the serialization of the SOAP fault header block HTTP Response message for this specific operation. Its value MUST be the [owner] <code> headerfault </code> when it has name of a <code> IANA media type </code> <em> attribute information item </em>. The <code> namespace </code> <em> attribute information item </em> has token. If not present, the following Infoset properties: </p> <ul> <li> <p> A [local name] of <code> namespace </code> default output serialization associated with the {http method} property applies, as specified in 3.3 Default Binding Rules .

  • A [namespace name] which has no {http fault serialization}, a string value </p> </li> <li> <p> An [owner] indicating the value for the serialization of <code> headerfault </code> the HTTP Response message for this specific operation in case a fault is returned. Its value MUST be the namespace named "http://www.w3.org/2003/06/wsdl/soap12" name of a IANA media type token.

deleted text: <p> The type of the <code> namespace </code> <em> attribute information item </em> is <em> xsd:anyURI </em>. </p>

<a name="_soap_headerfault_encoding" id= "_soap_headerfault_encoding"> 2.7.4 <code> encodingStyle </code> Attribute with <code> headerfault </code> [owner] 3.6.3 XML Representation of HTTP Operation Component


<definitions>
 <binding>
   <operation ref="xs:QName" 
              whttp:location="xs:anyURI"?
              whttp:method="xs:string"? 
              whttp:inputSerialization="xs:string"? 
              whttp:outputSerialization="xs:string"? 
              whttp:faultSerialization="xs:string"? >
  </operation>
 </binding>
</definitions>
          

The <code> encodingStyle </code> XML representation for binding an Operation are four attribute information item indicates the encoding style that was used to generate type description for the SOAP fault header block(s) for s with the [ancestor] <code> operation </code> . following Infoset properties:

  • The An OPTIONAL encodingStyle location attribute information item has with the following Infoset properties:

    • A [local name] of encodingStyle location

    • A [namespace name] deleted text: which has no value </p> </li> <li> <p> An [owner] of <code> headerfault </code> in the namespace named "http://www.w3.org/2003/06/wsdl/soap12" "http://www.w3.org/2004/08/wsdl/http"

    • </ul>
    • The A type of deleted text: the <code> encodingStyle </code> attribute information item wsdls:anyURI is <em> xsd:anyURI </em>.

    • The [normalized value] "http://www.w3.org/2003/05/soap-envelope/encoding/none" indicates that the type description has not been derived as a function of a well-known encoding. The [normalized value] MUST NOT be "". If no <code> encodingStyle </code> is in scope, then the [normalized value] is the <code> encodingStyleDefault </code> <em> attribute information item </em>. No default value

      </div> </div> <div class="div2"> <h3> <a name="_soap_fault" id="_soap_fault"> </a> 2.8 <code> fault </code> Element with <code> fault </code> [parent] </h3> <div class="exampleInner"> <pre> <definitions> <binding> <operation> <fault> <<b>soap:fault</b> message="nmtoken" namespace="uri"? encodingStyle="uri"? />* </fault> </operation> </binding> </definitions> </pre> </div> <table border="1" summary="Editorial note: JJM"> <tr> <td width="50%" valign="top" align="left"> <b> Editorial note: JJM </b> </td> <td width="50%" valign="top" align="right"> 2003/05/23 </td> </tr> <tr> <td valign="top" align="left" colspan="2"> This section has not yet been finalized. </td> </tr> </table>
  • The optional An OPTIONAL fault method element attribute information item specifies SOAP fault for the [ancestor] operation. It has with the following Infoset properties:

    • A [local name] of fault method

    • A [namespace name] of "http://www.w3.org/2003/06/wsdl/soap12" "http://www.w3.org/2004/08/wsdl/http"

    • A [parent] type of deleted text: <code> fault </code> in the namespace named "http://www.w3.org/2003/06/wsdl" </p> </li> <li> <p> One or more <em> attribute information item </em> s amongst its [attributes] as follows: </p> <ul> <li> <p> A mandatory <code> message </code> attribute information item wsdls:string as described below.

    • An optional <code> namespace </code> <em> attribute information item </em> as described below. No default value

  • An optional OPTIONAL encodingStyle inputSerialization attribute information item deleted text: as described below. </p> </li> </ul> </li> </ul> <p> The <code> fault </code> <em> element information item </em> has no [children]. </p> <div class="div3"> <h4> <a name="_soap_fault_message" id= "_soap_fault_message"> </a> 2.8.1 <code> message </code> Attribute with deleted text: <code> fault </code> [owner] </h4> <p> The <code> message </code> <em> attribute information item </em> refers to an XML Schema element declaration component that defines the SOAP fault header block for the [owner] <code> fault </code> . The <code> message </code> <em> attribute information item </em> has the following Infoset properties:

    • A [local name] of message inputSerialization

    • A [namespace name] deleted text: which has no value </p> </li> <li> <p> An [owner] of <code> fault </code> in the namespace named "http://www.w3.org/2003/06/wsdl/soap12" "http://www.w3.org/2004/08/wsdl/http"

    • </ul>
    • The A type of deleted text: the <code> message </code> attribute information item </em> is <em> xsd:QName </em>. </p> </div> <div class="div3"> <h4> <a name="_soap_fault_namespace" id= "_soap_fault_namespace"> </a> 2.8.2 <code> namespace </code> Attribute with <code> fault </code> [owner] </h4> <p> The <code> namespace </code> <em> attribute information item </em> defines the XML namespace of the SOAP fault for the [owner] <code> fault </code> . The <code> namespace </code> <em> attribute information item wsdls:string deleted text: has the following Infoset properties: </p> <ul> <li> <p> A [local name] of <code> namespace </code>

    • A [namespace name] which has no No default value

  • An [owner] of <code> fault </code> in the namespace named "http://www.w3.org/2003/06/wsdl/soap12" </p> </li> </ul> <p> The type of the OPTIONAL namespace outputSerialization attribute information item deleted text: is <em> xsd:anyURI </em>. </p> </div> <div class="div3"> <h4> <a name="_soap_fault_encoding" id= "_soap_fault_encoding"> </a> 2.8.3 <code> encodingStyle </code> Attribute with deleted text: <code> fault </code> [owner] </h4> <p> The <code> encodingStyle </code> <em> attribute information item </em> indicates the encoding style that was used to generate type description for the SOAP fault for the [ancestor] <code> operation </code> . </p> <p> The <code> encodingStyle </code> <em> attribute information item </em> has the following Infoset properties:

    • A [local name] of encodingStyle outputSerialization

    • A [namespace name] deleted text: which has no value </p> </li> <li> <p> An [owner] of <code> fault </code> in the namespace named "http://www.w3.org/2003/06/wsdl/soap12" "http://www.w3.org/2004/08/wsdl/http"

    • </ul>
    • The A type of deleted text: the <code> encodingStyle </code> attribute information item wsdls:string is <em> xsd:anyURI </em>.

    • The [normalized value] "http://www.w3.org/2003/05/soap-envelope/encoding/none" indicates that the type description has not been derived as a function of a well-known encoding. The [normalized value] MUST NOT be "". If no <code> encodingStyle </code> is in scope, then the [normalized value] is the <code> encodingStyleDefault </code> <em> attribute information item </em>. No default value

      </div> </div> <div class="div2"> <h3> <a name="_soap_address" id="_soap_address"> </a> 2.9 <code> address </code> Element with <code> endpoint </code> [parent] </h3> <div class="exampleInner"> <pre> <definitions> <service> <endpoint> <<b>soap:address</b> location="uri" /> </endpoint> </service> </definitions> </pre> </div>
  • The mandatory <code> address </code> <em> element information item </em> contains the endpoint address of an <code> endpoint </code> . The An OPTIONAL address faultSerialization element attribute information item has with the following Infoset properties:

    • A [local name] of address faultSerialization

    • A [namespace name] of "http://www.w3.org/2003/06/wsdl/soap12" "http://www.w3.org/2004/08/wsdl/http"

    • A [parent] type of deleted text: <code> endpoint </code> in the namespace named "http://www.w3.org/2003/06/wsdl" </p> </li> <li> <p> One attribute information item wsdls:string amongst its [attributes] as follows:

      <ul>
    • A required <code> location </code> default value of attribute information item "application/xml" as described below

    deleted text: <br /> <br />
<p> The <code> address </code> <em> element information item </em> has no [children]. </p>

<a name="_soap_location" id="_soap_location"> 2.9.1 <code> location </code> Attribute with <code> address </code> [owner] 3.6.4 Mapping Between HTTP Operation's XML Representation to Component Properties

The mandatory <code> location </code> <em> attribute information item </em> identifies the endpoint address of an <code> endpoint </code> . The <code> location </code> <em> attribute information item </em> has the following Infoset properties: See Table 3-3 .

<ul> <li> <p> A [local name] of <code> location </code> </p> </li> <li> <p> A [namespace name] which has no value </p> </li> <li> <p> An [owner] of <code> address </code> in the namespace named "http://www.w3.org/2003/06/wsdl/soap12" </p> </li> </ul> <p>
Table 3-3. Mapping between Binding Operation Component Extension Properties and XML Representation
Property Mapping
{http location} The type actual value of the location whttp:location attribute information item </em> is <code> xsd:anyURI </code>. .
{http method} The actual value of the location whttp:method attribute information item </em> is a URI that processes messages bound by the <code> endpoint </code> . .
{http input serialization} The URI scheme of the actual value of the location whttp:inputSerialization attribute information item </em> MUST correspond to the transport specified by the .
{http output serialization} The actual value of the binding whttp:outputSerialization attribute information item </em> .
{http fault serialization} The actual value of the endpoint whttp:faultSerialization element attribute information item . </p> </div>

<div class="div1"> <h2>

<a name="_http" id="_http"> 3. WSDL 3.7 Specifying HTTP Binding </h2> <table border="1" summary="Editorial note: JJM"> <tr> <td width="50%" valign="top" align="left"> Error Codes for Faults

<b> Editorial note: JJM </b> </td> <td width="50%" valign="top" align="right"> 20030514 </td> </tr> <tr> <td valign="top" align="left" colspan="2"> This section is not fully converted to a component model compatible with Part 1. </td> </tr> </table> 3.7.1 Description

The WSDL For every Interface Fault component contained in an Interface component, an HTTP binding described error code MAY be defined. It represents the error code that will be used by the service in this section is a binding case the fault needs to HTTP 1.1 [ <cite> be returned.

<a href="#RFC2616"> IETF RFC 2616 </a> </cite> ]. This 3.7.2 Relationship to WSDL Component Model

The HTTP Fault binding extends adds the following property to the WSDL component model (as defined in [ WSDL 1.2 2.0 Core Language ] by adding <em> element information item </em> s and <em> attribute information item </em> s to the Infoset of the WSDL <code> binding </code> <em> element information item </em> and <code> service </code> <em> element information item </em> (in the "http://www.w3.org/2003/06/wsdl" namespace). </p> <p> The WSDL HTTP binding supports the specification of the following protocol specific information: ]):

  • Binding to the HTTP/1.1 protocol. </p> </li> <li> <p> An HTTP method to be used for each operation. </p> </li> <li> <p> An address for {http error status code}, an HTTP endpoint. </p> </li> <li> <p> A relative address for each operation (relative to the base address integer representing a error Status-Code as defined by the port). </p> </li> <li> <p> Portions of an input message [ IETF RFC 2616 ], to deleted text: be serialized in the path of the request URI, query parameters Binding Fault component. The value of this property identifies the request URI, or the body of error code that the request. </p> </li> <li> <p> Serializing an output message service will use in case the body of fault is returned. If empty, no claim is made by the response. service.

<div class="div2"> <h3>

<a name="_http_binding" id="_http_binding"> 3.1 <code> binding </code> Element with <code> binding </code> [parent] </h3> 3.7.3 XML Representation



<definitions>
    <binding>
        <<b>http:binding</b> verbDefault="xsd:string"? />
    </binding>



<definitions >
  <binding >
    <fault ref="xs:QName"
           whttp:code="xs:int" />
    </fault>*
  </binding>


</definitions>

The mandatory <code> XML representation for binding </code> a SOAP Fault are two element attribute information item indicates that messages are HTTP messages [ <cite> <a href= "#RFC2616"> IETF RFC 2616 </a> </cite> ]. s with the following Infoset properties:

  • The <code> binding </code> whttp:code OPTIONAL element attribute information item has the following Infoset properties:

    • A [local name] of binding code

    • A [namespace name] of "http://www.w3.org/2003/06/wsdl/http" "http://www.w3.org/2004/08/wsdl/http"

    • A [parent] type of deleted text: <code> binding </code> in the namespace named "http://www.w3.org/2003/06/wsdl" </p> </li> <li> <p> Zero or one attribute information item </em> s amongst its [attributes] as follows: </p> <ul> <li> <p> An optional <code> verbDefault </code> <em> attribute information item wsdls:int as described below.

<p> The <code> binding </code> <em> element information item </em> has no [children]. </p>

<a name="_http_binding_verbDefault" id= "_http_binding_verbDefault"> 3.1.1 <code> verbDefault </code> Attribute with <code> binding </code> [owner] 3.7.4 Mapping Between Component Properties and XML Representation

The <code> verbDefault </code> <em> attribute information item </em> indicates the HTTP method used within a <code> binding </code> <em> element information item </em>, for example "GET" or "POST". </p> <p> The <code> verbDefault </code> <em> attribute information item </em> has the following Infoset properties: See Table 3-4 .

<ul> <li> <p> A [local name] of <code> verbDefault </code> </p> </li> <li> <p> A [namespace name] which has no value </p> </li> <li> <p> An [owner] of <code> binding </code> in the namespace named "http://www.w3.org/2003/06/wsdl/http" </p> </li> </ul> <p> The type of the <code> verbDefault </code> <em> attribute information item </em> is <em> xsd:string </em>.
Table 3-4. Mapping between Binding Fault Component Extension Properties and XML Representation
Property Mapping
{http error status code} The actual value of the verbDefault whttp:code attribute information item </em> is a string that identifies a specific HTTP method. </p> .

<a name="_http_operation" id="_http_operation"> 3.2 <code> operation </code> Element with <code> operation </code> [parent] 3.8 Serialization format of instance data

deleted text: <div class="exampleInner"> <pre> <definitions> <binding> <operation> <<b>http:operation</b> location="xsd:anyURI"? verb="xsd:string"? />? </operation> </binding> </definitions> </pre> </div>

The deleted text: optional <code> operation </code> <em> element information item </em> provides binding information to the [parent] operation. </p> <p> The <code> operation </code> <em> element information item </em> has the following Infoset properties: </p> <ul> <li> <p> A [local name] of <code> operation </code> </p> </li> <li> <p> A [namespace name] of "http://www.w3.org/2003/06/wsdl/http" </p> </li> <li> <p> A [parent] of <code> operation </code> in serialization formats can be used to encode the namespace named "http://www.w3.org/2003/06/wsdl" </p> </li> <li> <p> Zero instance data corresponding to two <em> attribute information item </em> s amongst its [attributes] as follows: </p> <ul> <li> <p> An optional <code> location </code> <em> attribute information item </em> the input and output message, as defined below. </p> </li> <li> <p> An optional <code> verb </code> <em> attribute information item </em> well as described below. </p> </li> </ul> </li> </ul> <p> The <code> operation </code> <em> element information item </em> has no [children]. the media types and HTTP headers associated.

If Other serialization formats may be used. Those MAY place restrictions on the <code> style of the interface operation </code> <em> element information item </em> has no [attributes], it MAY be omitted. bound.

<a name="_http_operation_verb" id= "_http_operation_verb"> 3.2.1 <code> verb </code> Attribute with <code> operation </code> [owner] 3.8.1 Serialization as "application/x-www-form-urlencoded"

The <code> verb </code> <em> attribute information item </em> indicates This serialization format is designed to allow a Web Service to produce a URI based on the HTTP method instance data of input messages. It may only be used by a particular <code> for interface operation </code> <em> element information item </em>. </p> <p> The <code> verb </code> <em> attribute information item </em> has using the following Infoset properties: </p> <ul> <li> <p> A [local name] of <code> verb </code> URI Style format as defined in 3.9.1 URI Style .

deleted text: </li> <li> <p> A [namespace name] which has no value </p> </li> <li>

An [owner] of <code> operation </code> in Elements from the namespace named "http://www.w3.org/2003/06/wsdl/http" </p> </li> </ul> <p> The type of instance data can be inserted into the <code> verb </code> <em> attribute information item </em> is <em> xsd:string </em>. </p> <p> The value path of the <code> verb </code> <em> attribute information item </em> is a string that identifies request URI, or a specific HTTP method to be used with this operation. If there is no <code> verb </code> <em> attribute information item </em>, the HTTP method to be used is specified by query parameter, as shown in the <code> verbDefault </code> <em> attribute information item </em> with [owner] <code> binding </code> . It is a fatal error if there is no <code> verb </code> <em> attribute information item </em> or <code> verbDefault </code> <em> attribute information item </em>. example below:

</div> <div class="div3"> <h4>

<a name="_http_operation_location" id= "_http_operation_location"> 3.2.2 <code> location </code> Attribute with <code> operation </code> [owner] </h4> <p> The <code> location </code> <em> attribute information item </em> indicates Example 3-1. Instance data serialized in a deleted text: relative URI for a particular <code> operation </code> <em> element information item </em>.

The <code> location </code> <em> attribute information item </em> may also indicate which portions following instance data of an input message deleted text: are serialized in the path of the request URI (as opposed to simply being serialized as query parameters of the request URI or in the body of the request).


<data>
  <town>Fréjus</town>
  <date>2004-01-16</date>
  <unit>C</unit>
</data>

The <code> location </code> <em> attribute information item </em> has with the following deleted text: Infoset properties: </p> <ul> <li> <p> A [local name] of <code> location </code> </p> </li> <li> <p> A [namespace name] which has no value </p> </li> <li> <p> An [owner] of operation in the namespace named "http://www.w3.org/2003/06/wsdl/http" element

</li> </ul>

<operation ref='t:io'
    whttp:location='temperature/{town}'
    whttp:method='GET' />

The type of and the following location endpoint <em> attribute information item </em> is <em> xsd:anyURI </em>. element


<endpoint name='e' binding='t:b'
    address='http://ws.example.com/service1' />

The <code> location </code> <em> attribute information item </em> specifies a template for the relative portion of the request URI for an operation. This URI is combined with will serialize the base URI specified message in the deleted text: <code> address </code> <em> element information item </em> to form the full URI for the HTTP request to invoke the operation. </p> <p> Message parts are serialized according to the rules of: as follow:

<ul> <li> <p> Section <a href="#_http_get_binding">

http://ws.example.com/service1/temperature/Fr%C3%A9jus?date=2004-01-16&unit=C

3.3 Method is GET Note: deleted text: </a>, if the HTTP method is "GET"

deleted text: </li> <li>

Section <a href="#_http_post_binding"> Element name and element content MUST be URI escaped when inserted into the request, as defined in " Serialization as application/x-www-form-urlencoded " ([ <b> 3.4 Method is POST </b> XForms 1.0 </a>, if the HTTP method is "POST" ], Section 11.6).

</li> </ul> <table border="1" summary="Editorial note: JJM">
3.8.1.1 Case of elements cited in whttp:location attribute
<td width="50%" valign="top" align="left"> <td width="50%" valign="top" align="right"> 2003/05/23 <td valign="top" align="left" colspan="2"> The editors are soliciting input on whether bindings for HTTP PUT or HTTP DELETE would be appropriate. </td> </tr> </table> </div> </div> <div class="div2"> <h3> <a name="_http_get_binding" id="_http_get_binding"> </a> 3.3 Method is <code> GET </code> </h3> <p>
Editorial note: JJM URIPath Feedback Requested  
The rules inclusion of elements of the instance data in deleted text: this section MUST be followed when the HTTP method is "GET". </p> <div class="div3"> <h4> <a name="_http_operation_location_cited_get" id= "_http_operation_location_cited_get"> </a> 3.3.1 Case path of Input Parts Cited the request URI, whilst supported by WSDL 1.1, is not supported by XForms 1.0. Hence this mechanism MAY be removed in <code> location </code> Attribute </h4> a future version of this specification. Feedback on this issue from users and implementers is highly encouraged.

The location attribute information item MAY cite elements instance data of the input message deleted text: parts to be serialized in the path of the request URI ("URI Syntactic Components", [ IETF RFC 2396 ], Section 3) by enclosing a part the element name within curly braces (e.g. "{partName}"): location="temperature/{town}"):

  • When constructing the request URI, each pair of curly braces (and enclosed part element name) is replaced by the corresponding part value. content of the element.

  • A double curly brace (i.e. "{{" or "}}") MAY be used to include a single, literal curly brace in the request URI.

Part values MUST be URI escaped. </p> <p> Parts An element MUST NOT be cited more than once within the location attribute information item .

An element name MAY be followed by a slash (i.e. "/") inside curly braces (e.g. location="temperature/{town/}") to indicate that no other element must be serialized in the request URI (see 3.8.1.2 Case elements NOT cited in whttp:location attribute ).

Strings enclosed within single curly braces MUST be element names from the instance data of the input message part names; message, possibly followed by a slash; any other strings enclosed within single curly braces are a fatal error.

deleted text: <p> If cited input message parts are defined using an XML Schema type, they MUST derive from xsd:simpleType, but MUST NOT derive from xsd:hexBinary, xsd:base64Binary, or any simple list type. </p>
<div class="div3"> <h4>
3.3.2 3.8.1.2 Case of Input Parts elements NOT Cited cited in location whttp:location attribute </h4>

If not all elements from the instance data are cited in the whttp:location attribute, then additional serialization rules apply.

If an element name appears in the whttp:location attribute information item followed by a slash, then the instance data must be serialized in the message body (see 3.8.1.2.2 Serialization in the message body ), otherwise the elements not cited must be serialized as parameters in the request URI (see 3.8.1.2.1 Serialization in the request URI ).

3.8.1.2.1 Serialization in the request URI

All elements of the instance data from the input message deleted text: parts NOT cited by the location attribute information item are serialized as query parameters appended to the request URI. </p> <div class="div4"> <h5> <a name="_http_operation_request_get_body_request" id= "_http_operation_request_get_body_request"> URI (e.g. Example 3-1 3.3.2.1 Serializing Parts into HTTP Body request </h5> ).

If the location attribute does not contain a '?' (question mark) character, one is appended. If it does already contain a question mark character, then an "&" separator character is appended. Each parameter pair is separated by the "&" separator character.

  • Uncited parts elements with single values (non-list) are serialized as a single name-value parameter pair. The name of the parameter is the name of the uncited part, element, and the value of the parameter is the value of the uncited part. element.

  • Uncited parts elements with list values are serialized as one name-value parameter pair per list value. The name of each parameter is the name of the uncited part, element, and the value of each parameter is the corresponding value in the list.

3.8.1.2.2 Serialization in the message body

Part names and values MUST be In addition to the serialization in the request URI escaped. of the elements cited in the whttp:location attribute, the entire instance data is serialized in the message body following the rules of the "application/xml" (see 3.8.2 Serialization as application/xml ).

Example 3-2. Instance data serialized in a URI and in a message body

If uncited The following instance data of an input message deleted text: parts are defined using an XML Schema type, they MUST derive from xsd:simpleType, MUST NOT derive from xsd:hexBinary or xsd:base64Binary, but MAY derive from a simple list type.


<data>
  <town>Fréjus</town>
  <date>2004-01-16</date>
  <unit>C</unit>
  <value>24</value>
</data>

with the following operation element:


<operation ref='t:io'
    whttp:inputSerialization='application/x-www-form-urlencoded'
    whttp:location='temperature/{town/}'
    whttp:method='POST' />

and the following endpoint element


<endpoint name='e' binding='t:b'
    address='http://ws.example.com/service1' />

will serialize the message in the URI as follow:


http://ws.example.com/service1/temperature/Fr%C3%A9jus

and in the message as follow:


Content-Type: application/xml
Content-Length: xxx

<data>
  <town>Fréjus</town>
  <date>2004-01-16</date>
  <unit>C</unit>
  <value>24</value>
</data>

<a name="_http_operation_response_get" id= "_http_operation_response_get"> 3.3.3 Case of Output Parts 3.8.2 Serialization as "application/xml"

Output The instance data of the input, output or fault message parts are is serialized as a single an XML document in the message body of the HTTP response. </p> <div class="div4"> <h5> <a name="_http_operation_response_get_body_response" id= "_http_operation_response_get_body_response"> request, following the serialization defined in [ Canonical XML 3.3.3.1 Serializing parts into HTTP Body response </h5> ].

The root of Content-Type HTTP header MUST have the document value application/xml ,or a media type compatible with application/xml .Other HTTP headers, such as Content-Encoding or Transfer-Encoding ,MAY be used.

3.8.3 Serialization as "multipart/form-data"

This format is an XML element whose local name and XML namespace are for legacy compatibility to permit the {name} and {target namespace} use of the operation, respectively. The root has one child XForms clients with [ IETF RFC 2388 ] servers. This serialization format may only be used for each part interface operations using the Multipart Style format as follows: defined in 3.9.2 Multipart style .

deleted text: <ul> <li>

If the {component reference} for an uncited part corresponds to an Each element declaration, in the child sequence is the element instance. serialized into a part as follow:

</li>
  1. If the {component reference} for an uncited part corresponds to a type definition, The Content-Disposition header MUST have the deleted text: child has a local name, XML namespace, and value corresponding to the {name} of the part, the {target namespace} of the message, form-data , and its name parameter is the value local name of the part, respectively. element.

  2. </ul>
  3. The deleted text: HTTP Content-Type header deleted text: field MUST be have the media type "application/xml" or any derived XML type ("*/*+xml"). value:

    • If there are no message parts, the HTTP Body MUST be empty, and the HTTP Content-Length application/xml header field MUST have (or a value of "0" (zero). media type compatible with application/xml ) if the element has a complex type;

      </div> </div> </div> <div class="div2"> <h3> <a name="_http_post_binding" id="_http_post_binding">
    • deleted text: </a> 3.4 Method is POST application/octet-stream </h3> <p> The rules in this section MUST be followed when if the HTTP method element is "POST". of type xs:base64Binary ,xs:hexBinary ,or a derived type;

      <table border="1" summary="Editorial note: JJM"> <tr> <td width="50%" valign="top" align="left"> <b> Editorial note: JJM </b> </td> <td width="50%" valign="top" align="right"> 2003/05/22 </td> </tr> <tr> <td valign="top" align="left" colspan="2"> How do we select the encoding mechanism to be used? </td> </tr> </table> <div class="div3"> <h4> <a name="_http_operation_xml_encoding" id= "_http_operation_xml_encoding"> </a> 3.4.1 XML Encoding Mechanism </h4> <div class="div4"> <h5> <a name="_http_operation_location_cited_post_xml" id= "_http_operation_location_cited_post_xml">
    • deleted text: </a> 3.4.1.1 Case of Input Parts Cited in location text/plain Attribute </h5> if the element has a simple type; The charset MUST be set appropriately. UTF-8 or UTF-16 MUST be at least supported.

  4. All input message parts cited by If the type is location xs:base64Binary ,xs:hexBinary ,xs:anySimpleType <em> attribute information item </em> are or a derived type, the content of the part is the content of the element. If the type is a complex type, the element is serialized according to following the rules defined in <a href="#_http_operation_location_cited_get"> the 3.3.1 Case of Input Parts Cited in location Attribute 3.8.2 Serialization as application/xml </a>. .

    </div> <div class="div4"> <h5>

<a name="_http_operation_location_notcited_post_xml" id= "_http_operation_location_notcited_post_xml"> </a> 3.4.1.2 Case Example 3-3. Example of Input Parts NOT Cited in <code> location </code> attribute </h5> multipart/form-data

All The following instance data of an input message parts NOT cited by message:


<data>
  <town>
    <name>Fréjus</name>
    <country>France</country>
  </town>
  <date>2004-01-16</date>
</data>

with the following location operation <em> attribute information item </em> are serialized according to the rules in <a href= "#_http_operation_response_get_body_response"> <b> 3.3.3.1 Serializing parts into HTTP Body response </b> element


<operation ref='t:io'
    whttp:location='temperature'
    whttp:method='POST'
    whttp:inputSerialization='multipart/form-data'/>

</a>.

will serialize the message as follow:


Content-Type: multipart/form-data; boundary=AaB03x
Content-Length: xxx
        
--AaB03x
Content-Disposition: form-data; name="town"
Content-Type: application/xml
<town>
  <name>Fréjus</name>
  <country>France</country>
</town>
--AaB03x
Content-Disposition: form-data; name="date"
Content-Type: text/plain; charset=utf-8
2004-01-16
--AaB03x--

<div class="div4"> <h5>

<a name="_http_operation_response_post_xml" id= "_http_operation_response_post_xml"> 3.4.1.3 Case of Output Parts </h5> 3.9 Operation Styles

All output message parts are serialized according This section defines operation styles in use in parallel to the rules in <a href="#_http_operation_response_get"> <b> 3.3.3 Case of Output Parts </b> </a>. HTTP 1.1 binding.

deleted text: </div> </div>

<a name="_http_operation_multipart_encoding" id= "_http_operation_multipart_encoding"> 3.4.2 Multipart Encoding Mechanism 3.9.1 URI Style

deleted text: <div class="div4"> <h5> <a name="_http_operation_location_cited_post_multipart" id= "_http_operation_location_cited_post_multipart"> </a> 3.4.2.1 Case of Input Parts Cited in <code> location </code> Attribute </h5>

All input message parts cited The URI style is selected by assigning the <code> location </code> Interface Operation component's {style} property the value attribute information item </em> are serialized according to http://www.w3.org/2004/08/wsdl/style/uri .

The URI style may only be used for Interface Operation components whose {message exchange pattern} property has the rules in <a href="#_http_operation_location_cited_get"> <b> 3.3.1 Case of Input Parts Cited in location Attribute </b> </a>. value 'http://www.w3.org/2004/08/wsdl/in-only', 'http://www.w3.org/2004/08/wsdl/robust-in-only' or 'http://www.w3.org/2004/08/wsdl/in-out'.

</div> <div class="div4"> <h5>

Use of this value indicates that XML Schema [ <a name="_http_operation_location_notcited_post_multipart" id= "_http_operation_location_notcited_post_multipart"> XML Schema Structures ] was used to define the schemas of the {element} 3.4.2.2 Case properties of all Message Reference components of deleted text: Input Parts NOT Cited in <code> location </code> Attribute </h5> <p> All input message parts NOT cited by the <code> location </code> Interface Operation component with {direction} property deleted text: attribute information item </em> are serialized as a single MIME Multipart document in .Those schemas MUST adhere to the body of the HTTP response. The document has one MIME body part for each uncited message part as follows: rules below.

  • If the {component reference} for an uncited part corresponds to an element declaration, the The content model of the MIME body part is the element instance. The media input message elements are defined using a complex type of the MIME body part MUST be "application/xml" or any derived that contains a sequence from XML type ("*/*+xml"). Schema.

  • If The sequence MUST only contain elements. It MUST NOT contain other structures such as xs:choice.

  • The sequence MUST contain only local element children. These child elements MAY contain the {component reference} for an uncited part corresponds to nillable attribute, and the simple type definition attributes xsd:hexBinary </code>, minOccurs and xsd:base64Binary maxOccurs or MUST have a type derived from one value 0 or the other, the content of the MIME body part is the element instance. 1 .

  • The media type localPart of the MIME body part input element's QName MUST be the one specified. same as the Interface operation component's name.

  • In all other cases, the content of The complex types that defines the deleted text: MIME body part is of an XML document input element or its children elements MUST NOT contain any attributes.

  • The input sequence MUST NOT contain multiple children element declared with deleted text: a local name, XML namespace, and value corresponding to the {name} of the part, same local name.

  • If the {target namespace} children elements of the message, input sequence are defined using an XML Schema type, they MUST derive from xs:simpleType , and the value MUST NOT be of the deleted text: part, respectively. The media type of the MIME body part MUST be "application/xml". or derive from xs:QName ,xs:NOTATION ,xs:hexBinary or xs:base64Binary .

deleted text: <div class="div4"> <h5> <a name="_http_operation_response_post_multipart" id= "_http_operation_response_post_multipart"> </a> 3.4.2.3 Case of Output Parts </h5> <p> All output message parts are serialized according to the rules in <a href="#_http_operation_response_get"> <b> 3.3.3 Case of Output Parts </b> </a>. </p> </div> </div>

<a name="_http_operation_form_encoding" id= "_http_operation_form_encoding"> 3.4.3 <code> application/x-www-form-urlencoded </code> Encoding Mechanism 3.9.2 Multipart style

deleted text: <div class="div4"> <h5> <a name="_http_operation_location_cited_post_form" id= "_http_operation_location_cited_post_form"> </a> 3.4.3.1 Case of Input Parts Cited in <code> location </code> Attribute </h5>

All input message parts cited The Multipart style is selected by assigning the <code> location </code> Interface Operation component's {style} property the value attribute information item </em> are serialized according to http://www.w3.org/2004/08/wsdl/style/multipart .

The Multipart style may only be used for Interface Operation components whose {message exchange pattern} property has the rules in <a href="#_http_operation_location_cited_get"> <b> 3.3.1 Case of Input Parts Cited in location Attribute </b> </a>. value 'http://www.w3.org/2004/08/wsdl/in-only', 'http://www.w3.org/2004/08/wsdl/robust-in-only' or 'http://www.w3.org/2004/08/wsdl/in-out'.

</div> <div class="div4"> <h5>

Use of this value indicates that XML Schema [ <a name="_http_operation_location_notcited_post_form" id= "_http_operation_location_notcited_post_form"> XML Schema Structures ] was used to define the schemas of the {element} 3.4.3.2 Case properties of Input Parts NOT Cited all Message Reference components of the Interface Operation component with {direction} property in <code> location </code> Attribute </h5> .Those schemas MUST adhere to the rules below.

  • All The content model of input message parts elements are defined using a complex type that contains a sequence from XML Schema.

  • The sequence MUST only contain elements. It MUST NOT cited by contain other structures such as xs:choice.

  • The sequence MUST contain only local element children. These child elements MAY contain the location nillable <em> attribute information item </em> are serialized as attribute, and the attributes minOccurs and maxOccurs MUST have a single URLEncoded form in value 1 .

  • The localPart of input element's QName MUST be the same as the Interface operation component's name.

  • The complex types that defines the body of the HTTP request. an input element or its children elements MUST NOT contain any attributes.

    <ul>
  • Uncited The input parts sequence MUST follow NOT contain multiple children element declared with the rules in <a href= "#_http_operation_request_get_body_request"> same local name.

<b> 3.3.2.1 Serializing Parts into HTTP Body request </b> 3.10 Specifying the transfer coding

3.10.1 Description

Every Binding Message Reference component MAY indicate which transfer codings, as defined in section 3.6 of [ IETF RFC 2616 ], are available for this particular message.

deleted text: </li> </ul>

The HTTP <code> Content-Type </code> header field MUST be binding provides a mechanism for indicating a default value at the media type "x-www-form-urlencoded". Binding component and Binding Operation levels.

If deleted text: there is no deleted text: uncited message part, the HTTP Body MUST be empty, and the HTTP <code> Content-Length </code> header field MUST have a value of "0" (zero). is specified, no claim is being made.

<div class="div4"> <h5>

<a name="_http_operation_response_post_form" id= "_http_operation_response_post_form"> 3.4.3.3 Case of Output Parts </h5> 3.10.2 Relationship to WSDL Component Model

All output message parts are serialized according The HTTP binding specification adds the following property to the rules WSDL component model (as defined in <a href="#_http_operation_response_get"> [ <b> 3.3.3 Case of Output Parts </b> WSDL 2.0 Core Language </a>. ]):

  • {http transfer coding}, a string value to the Binding Message Reference component.

</div> </div> <div class="div2"> <h3>

<a name="_http_address" id="_http_address"> 3.5 <code> address </code> Element with <code> endpoint </code> [parent] </h3> 3.10.3 XML Representation



<definitions>
    <service>
        <endpoint>
            <<b>http:address</b> location="xsd:anyURI" />
        </endpoint>
    </service>



<definitions >
  <binding name="xs:NCName" interface="xs:QName"? type="xs:anyURI"
           whttp:defaultTransferCoding="xs:string"? >
    <operation location="xs:anyURI"?
               whttp:defaultTransferCoding="xs:string" ? >
      <input messageLabel="xs:NCName"? 
             whttp:transferCoding="xs:string"? />

      <output messageLabel="xs:NCName"?
              whttp:transferCoding="xs:string"? />
    </operation>
  </binding>


</definitions>

The mandatory XML representation for specifying the default transfer coding is an OPTIONAL attribute information item for the address binding element information item contains the endpoint address of an or endpoint binding . The 's child address operation element information item has s with the following Infoset properties:

  • A [local name] of address. defaultTransferCoding

  • A [namespace name] of "http://www.w3.org/2003/06/wsdl/http." "http://www.w3.org/2004/08/wsdl/http"

  • A [parent] type of deleted text: <code> endpoint </code> in the namespace named "http://www.w3.org/2003/06/wsdl." </p> </li> <li> <p> One attribute information item wsdls:string amongst its [attributes] as follows:

    <ul>
  • A required <code> location </code> <em> attribute information item </em> as described below. No default value

deleted text: <br /> <br /> </li> </ul>

The <code> address </code> <em> element information item </em> has no [children]. </p> <div class="div3"> <h4> <a name="_http_location" id="_http_location"> </a> 3.5.1 <code> location </code> Attribute with <code> address </code> [owner] </h4> <p> The mandatory <code> location </code> <em> attribute information item </em> identifies XML representation for specifying the endpoint address of transfer coding is an <code> endpoint </code> . The <code> location </code> OPTIONAL attribute information item has with the following Infoset properties:

  • A [local name] of location. transferCoding

  • A [namespace name] which has no value. of "http://www.w3.org/2004/08/wsdl/http"

  • An [owner] A type of <code> address </code> in the namespace named "http://www.w3.org/2003/06/wsdl/http". wsdls:string

  • No default value

3.10.4 Mapping Between Component Properties and XML Representation

See Table 3-5 .


Table 3-5. Mapping between Message Reference Component Extension Properties and XML Representation
Property Mapping
{http transfer coding} The type of the <code> location </code> <em> attribute information item </em> is <code> xsd:anyURI </code>. The actual value of the location whttp:transferCoding attribute information item is a URI that processes messages bound by on the <code> endpoint </code> . The URI scheme of Binding Message Reference component, if present. If not, the actual value of the location whttp:defaultTransferCoding <em> attribute information item </em> MUST correspond to on the transport specified by Binding Operation component, if present. If not, the actual value of the binding whttp:defaultTransferCoding <em> attribute information item </em> of on the <code> endpoint </code> <em> element information item </em>. </p> </div> Binding component, if present.

<div class="div1"> <h2>

<a name="_mime" id="_mime"> 4. MIME Binding </h2> <table border="1" summary="Editorial note: JJM"> <tr> <td width="50%" valign="top" align="left"> 3.11 Specifying the Use of HTTP Cookies

<b> Editorial note: JJM </b> </td> <td width="50%" valign="top" align="right"> 20030514 </td> </tr> <tr> <td valign="top" align="left" colspan="2"> This binding has not been revised and may be dropped in a future version of this specification </td> </tr> </table> <p> WSDL includes a way to bind abstract types to concrete messages in some MIME format. Bindings for the following MIME types are defined: </p> <ul> <li> 3.11.1 Description

"multipart/related", Every Binding component MAY indicate whether HTTP cookies (as defined in by [ <a href="#RFC2387"> IETF RFC 2387 2965 ]. ]) are used for some or all of operations of the interface that this binding applies to.

</li> <li>

3.11.2 Relationship to WSDL Component Model

"text/xml", The HTTP binding specification adds the following property to the WSDL component model (as defined in [ <a href="#RFC3023"> IETF RFC 3023 WSDL 2.0 Core Language ]. ]):

</li>
  • "application/x-www-form-urlencoded", defined in <a href= "http://www.w3.org/TR/1999/REC-html401-19991224/interact/forms.html#h-17.13.4"> Form content types </a> ([ <cite> {http cookies}, a boolean value to the Binding component.

deleted text: <a href="#HTML401"> HTML 4.01 3.11.3 XML Representation


<definitions >
  <binding name="xs:NCName" interface="xs:QName"? type="xs:anyURI"
           whttp:cookies="xs:boolean"? >
  </binding>
</definitions>

The XML representation for specifying the use of HTTP cookies is an OPTIONAL attribute information item with the following Infoset properties:

  • A [local name] of cookies deleted text: </cite> ], section 17.13.4).

  • Others (by specifying the MIME A [namespace name] of "http://www.w3.org/2004/08/wsdl/http"

  • A type string) of wsdls:boolean

  • </ul>
  • The set A default value of defined MIME types is both large false

3.11.4 Mapping Between Component Properties and deleted text: evolving, so it is not a goal for WSDL to exhaustively define XML grammar for each MIME type. Nothing precludes additional grammar to be added to define additional MIME types as necessary. If a MIME type string is sufficient to describe the content, Representation

See Table 3-6 .


Table 3-6. Mapping between Binding Component Extension Properties and XML Representation
Property Mapping
{http cookies} The actual value of the mime whttp:cookies element defined below can be used. </p> attribute information item .

<a name="_how_mime_extends" id="_how_mime_extends"> 4.1 How the MIME Binding extends WSDL 3.12 Specifying HTTP Access Authentication

3.12.1 Description

The MIME Binding extends WSDL with Every Endpoint component MAY indicate the following extension elements: </p> <div class="exampleInner"> <pre> <mime:content part="nmtoken"? type="string"?/> use of an HTTP access authentication mechanism (as defined by [ <mime:multipartRelated> <mime:part> * <-- mime element --> </mime:part> </mime:multipartRelated> <mime:mimeXml part="nmtoken"?/> </pre> IETF RFC 2616 </div> <p> They are used at ]) for the following locations in WSDL: endpoint described.

deleted text: <div class="exampleInner"> <pre> <definitions .... > <binding .... > <operation .... > <input .... > <em> <-- mime elements --></em> </input> <output .... > <em> <-- mime elements --></em> </output> </operation> </binding> </definitions> </pre> </div>

MIME elements appear under input and output to specify This binding specification allows the MIME format. If multiple appear, they are considered authentication scheme and realm to be alternatives. specified.

<div class="div2"> <h3>

<a name="_mime_content" id="_mime_content"> 4.2 mime:content </h3> <p> To avoid having 3.12.2 Relationship to define a new element for every MIME format, WSDL Component Model

The HTTP binding specification adds the <code> mime:content </code> element may be used if there is no additional information following property to deleted text: convey about the format other than its MIME type string. </p> <div class="exampleInner"> <pre> <mime:content part="nmtoken"? type="string"?/> </pre> WSDL component model (as defined in [ </div> WSDL 2.0 Core Language ]):

  • The <code> part </code> attribute is used {http authentication scheme}, a string value to deleted text: specify the name of the message part. If the message has a single part, then Endpoint component, corresponding to the <code> part </code> attribute is optional. HTTP authentication scheme used. The <code> type </code> attribute contains the MIME type string. A <code> type </code> value has two portions, separated by a slash (/), either of which may be a wildcard (*). Not specifying the <code> type </code> attribute indicates that all MIME types valid values are acceptable. </p> <p> If "basic" for the return format is XML "basic" authentication scheme defined in [ <a href="#XML"> XML 1.0 IETF RFC 2617 ], but the schema is not known ahead of time, "digest" for the generic mime element can be used indicating "text/xml" Digest Access Authentication scheme as defined in [ <a href="#RFC3023"> IETF RFC 3023 2617 ]: ], and "none" for no access authentication.

    <div class="exampleInner"> <pre> <mime:content type="text/xml"/> </pre> </div>
  • A wildcard (*) can be used to specify {http authentication realm}, a family string value to the Endpoint. It corresponds to the realm authentication parameter defined in [ IETF RFC 2617 ]. If the the value of mime types, for example all text types. the {http authentication scheme} property is not "none", it MUST not be empty.

    <div class="exampleInner"> <pre> <mime:content type="text/*"/> </pre>
<p> The following two examples both specify all mime types: </p>

3.12.3 XML Representation



<mime:content type="*/*"/>
<mime:content/>



<definitions>
  <service>
    <endpoint name="xs:NCName" binding="xs:QName" address="xs:anyURI"? >
              whttp:authenticationType="xs:string"? 
              whttp:authenticationRealm="xs:string"? />
    </endpoint>
  </service>
</definitions>


deleted text: </div> <div class="div2"> <h3> <a name="_mime_multipartRelated" id= "_mime_multipartRelated"> </a> 4.3 mime:multipartRelated </h3>

The "multipart/related" MIME type aggregates an arbitrary set XML representation for specifying the use of MIME formatted parts into one message using HTTP access authentication is two OPTIONAL attribute information item s with the MIME type "multipart/related". The following Infoset properties:

  • An OPTIONAL mime:multipartRelated authenticationType element describes attribute information item with the concrete format of such a message: following Infoset properties:

    <div class="exampleInner"> <pre> <mime:multipartRelated> <mime:part> * <-- mime element --> </mime:part> </mime:multipartRelated> </pre> </div>
    • The A [local name] of mime:part authenticationType element describes each part

    • A [namespace name] of a "multipart/related" message [ <cite> "http://www.w3.org/2004/08/wsdl/http"

    • A type of wsdls:string <a href="#RFC2387"> IETF RFC 2387 </a>

    • A default value of "none" </cite> ]. MIME elements appear within

  • An OPTIONAL mime:part authenticationType to specify the concrete MIME type for attribute information item with the part. If more than one MIME element appears inside a <code> mime:part </code>, they are alternatives. following Infoset properties:

    </div> <div class="div2"> <h3> <a name="_mime_soap_body" id="_mime_soap_body"> </a> 4.4 soap:body </h3>
    • When using the MIME binding with SOAP requests [ <cite> <a href= "#SOAP12-PART1"> SOAP 1.2 Part 1: Messaging Framework </a> </cite> ], it is legal to use the A [local name] of soap:body authenticationRealm element as a MIME element. It indicates the content

    • A [namespace name] of "http://www.w3.org/2004/08/wsdl/http"

    • A type is "text/xml", and there is an enclosing SOAP Envelope. of wsdls:string

    • A default value of ""

<div class="div2"> <h3>

<a name="_mime_mimeXml" id="_mime_mimeXml"> 4.5 mime:mimeXml </h3> 3.12.4 Mapping Between Component Properties and XML Representation

To specify See Table 3-7 .


Table 3-7. Mapping between Endpoint Component Extension Properties and XML payloads that are not SOAP compliant (do not have a SOAP Envelope), but do have a particular schema, the <code> mime:mimeXml </code> element may be used to specify that concrete schema. Representation
Property Mapping
{http authentication scheme} The <code> part </code> attribute refers to a message part defining the concrete schema actual value of the deleted text: root XML element. The part whttp:authenticationType attribute MAY be omitted if the message has only a single part. information item .
{http authentication realm} The part references a concrete schema using actual value of the element </code> attribute for simple parts or <code> type whttp:authenticationRealm attribute for composite parts . </p> <div class="exampleInner"> <pre> <mime:mimeXml part="nmtoken"?/> </pre> information item .

5. 4. References

5.1 4.1 Normative References

<a name="HTML401" id="HTML401"> [HTML 4.01] [Canonical XML]
<a href= "http://www.w3.org/TR/1999/REC-html401-19991224/"> HTML 4.01 Specification Canonical XML , D. Raggett, A. Le Hors, I. Jacobs, Editors. J. Boyer, Author. World Wide Web Consortium, 24 December 1999. 15 March 2001. This version of the HTML 4.01 Canonical XML Recommendation is http://www.w3.org/TR/1999/REC-html401-19991224. http://www.w3.org/TR/2001/REC-xml-c14n-20010315. The <a href= "http://www.w3.org/TR/html401/"> latest version of HTML 4.01 Canonical XML is available at http://www.w3.org/TR/html401. </dd> <dt class="label"> <a name="RFC2045" id="RFC2045"> </a> [IETF RFC 2045] </dt> <dd> <cite> <a href= "http://www.ietf.org/rfc/rfc2045.txt"> Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies </a> </cite>, N. Freed, N. Borenstein, Authors. Internet Engineering Task Force, November 1996. Available at http://www.ietf.org/rfc/rfc2045.txt. http://www.w3.org/TR/xml-c14n.
[IETF RFC 2119]
Key words for use in RFCs to Indicate Requirement Levels , S. Bradner, Author. Internet Engineering Task Force, June 1999. Available at http://www.ietf.org/rfc/rfc2119.txt.
<a name="RFC2387" id="RFC2387"> [IETF RFC 2387] 2388]
<a href="http://www.ietf.org/rfc/rfc2387.txt"> The MIME Multipart/Related Content-type Returning Values from Forms: multipart/form-data , E. Levinson, Authors. L. Masinter, Author. Internet Engineering Task Force, August 1998. Available at http://www.ietf.org/rfc/rfc2387.txt. http://www.ietf.org/rfc/rfc2388.txt.
[IETF RFC 2396]
Uniform Resource Identifiers (URI): Generic Syntax , T. Berners-Lee, R. Fielding, L. Masinter, Authors. Internet Engineering Task Force, August 1998. Available at http://www.ietf.org/rfc/rfc2396.txt.
[IETF RFC 2616]
Hypertext Transfer Protocol -- HTTP/1.1 , R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee, Authors. Internet Engineering Task Force, June 1999. Available at http://www.ietf.org/rfc/rfc2616.txt.
[IETF RFC 2617]
HTTP Authentication: Basic and Digest Access Authentication ,J. Franks, P. Hallam-Baker, J. Hostetler, S. Lawrence, P. Leach, A. Luotonen, L. Stewart, June 1999. Available at http://www.ietf.org/rfc/rfc2616.txt.
[IETF RFC 2818]
HTTP Over TLS ,E. Rescorla, Author. Internet Engineering Task Force, May 2000. Available at http://www.ietf.org/rfc/rfc2818.txt.
[IETF RFC 2965]
HTTP State Management Mechanism ,D. Kristol, L. Montulli Authors. Internet Engineering Task Force, October 2000. Available at http://www.ietf.org/rfc/rfc2965.txt.
[IETF RFC 3023]
XML Media Types , M. Murata, S. St. Laurent, D. Kohn, Authors. Internet Engineering Task Force, January 2001. Available at http://www.ietf.org/rfc/rfc3023.txt.
[XForms 1.0]
XForms 1.0 ,M. Dubinko, et al., Editors. World Wide Web Consortium, 14 October 2003. This version of the XForms 1.0 Recommendation is http://www.w3.org/TR/2003/REC-xforms-20031014/. The latest version of XForms 1.0 is available at http://www.w3.org/TR/xforms/.
[SOAP 1.2 Part 1: Messaging Framework]
<a href= "http://www.w3.org/TR/2003/PR-soap12-part1-20030507/"> SOAP Version 1.2 Part 1: Messaging Framework , M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielsen, Editors. World Wide Web Consortium, 7 May 24 June 2003. This version of the "SOAP Version 1.2 Part 1: Messaging Framework" Specification Recommendation is http://www.w3.org/TR/2003/PR-soap12-part1-20030507/. http://www.w3.org/TR/2003/REC-soap12-part1-20030624/. The latest version of "SOAP Version 1.2 Part 1: Messaging Framework" is available at http://www.w3.org/TR/soap12-part1/.
[SOAP 1.2 Part 2: Adjuncts]
<a href= "http://www.w3.org/TR/2003/PR-soap12-part2-20030507/"> SOAP Version 1.2 Part 2: Adjuncts , M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, and H. Frystyk Nielsen, Editors. World Wide Web Consortium, 7 May 2003. This version of the "SOAP Version 1.2 Part 2: Adjuncts" Specification Recommendation is http://www.w3.org/TR/2003/PR-soap12-part2-20030507/. http://www.w3.org/TR/2003/REC-soap12-part2-20030624/. The latest version of "SOAP Version 1.2 Part 2: Adjuncts" is available at http://www.w3.org/TR/soap12-part2/.
<a name="XML" id="XML"> [XML 1.0]
Extensible Markup Language (XML) 1.0 (Second Edition) , T. Bray, J. Paoli, C. M. Sperberg-McQueen, and E. Maler, Editors. World Wide Web Consortium, 10 February 1998, revised 6 October 2000. This version of the XML 1.0 Recommendation is http://www.w3.org/TR/2000/REC-xml-20001006. The latest version of XML 1.0 is available at http://www.w3.org/TR/REC-xml.
[XML Information Set]
XML Information Set , J. Cowan and R. Tobin, Editors. World Wide Web Consortium, 24 October 2001. This version of the XML Information Set Recommendation is http://www.w3.org/TR/2001/REC-xml-infoset-20011024. The latest version of XML Information Set is available at http://www.w3.org/TR/xml-infoset.
[XML Schema Structures]
XML Schema Part 1: Structures , H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn, Editors. World Wide Web Consortium, 2 May 2001. This version of the XML Schema Part 1 Recommendation is http://www.w3.org/TR/2001/REC-xmlschema-1-20010502. The latest version of XML Schema Part 1 is available at http://www.w3.org/TR/xmlschema-1.
[XML Schema Datatypes]
XML Schema Part 2: Datatypes , P. Byron and A. Malhotra, Editors. World Wide Web Consortium, 2 May 2001. This version of the XML Schema Part 2 Recommendation is http://www.w3.org/TR/2001/REC-xmlschema-2-20010502. The latest version of XML Schema Part 2 is available at http://www.w3.org/TR/xmlschema-2.
[WSDL 1.2 2.0 Core Language]
<a href= "http://www.w3.org/TR/2003/WD-wsdl12-20030611"> Web Services Description Language (WSDL) Version 1.2: 2.0 Part 1: Core Language , R. Chinnici, M. Gudgin, J-J. Moreau, S. Weerawarana, Editors. World Wide Web Consortium, 11 June 2003. 3 August 2004. This version of the "Web Services Description Language (WSDL) Version 1.2:Core 2.0 Part 1: Core Language" Specification is available is available at http://www.w3.org/TR/2003/WD-wsdl12-20030611. http://www.w3.org/TR/2004/WD-wsdl20-20040803. The <a href= "http://www.w3.org/TR/wsdl12"> latest version of "Web Services Description Language (WSDL) Version 1.2: 2.0 Part 1: Core Language" is available at http://www.w3.org/TR/wsdl12. http://www.w3.org/TR/wsdl20.
[WSDL 2.0 Predefined Extensions]
Web Services Description Language (WSDL) Version 2.0 Part 2: Predefined Extensions ,M. Gudgin, A. Lewis, and J. Schlimmer, Editors. World Wide Web Consortium, 3 August 2004. This version of the "Web Services Description Language (WSDL) Version 2.0 Part 2: Predefined Extensions" Specification is available at http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803. The latest version of "Web Services Description Language (WSDL) Version 2.0 Part 2: Predefined Extensions" is available at http://www.w3.org/TR/wsdl20-extensions.

5.2 4.2 Informative References

[SOAP Message Transmission Optimization Mechanism]
SOAP Message Transmission Optimization Mechanism ,N. Mendelsohn, M. Nottingham, and H. Ruellan, Editors. World Wide Web Consortium, Working Draft 8 June 2004.
[MTXML]
Assigning Media Types to Binary Data in XML ,A. Karmarkar, Ü. Yalçınalp, W3C Working Draft, 8 June 2004. The latest version of the "Assigning Media Types to Binary Data in XML" document is available from http://www.w3.org/TR/xml-media-types/.
[WSDL 1.2 2.0 Primer]
Web Services Description (WSDL) Version 1.2: 2.0: Primer , K. Sankar, K. Liu, D. Booth, Editors. World Wide Web Consortium, 11 June 2003. Consortium. The editors' version of the "Web Services Description Version 1.2: 2.0: Primer" document is available from http://www.w3.org/2002/ws/desc/. http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20-primer.html.
[XML 1.1]
Extensible Markup Language (XML) 1.1 , T. Bray, J. Paoli, C. M. Sperberg-McQueen, E. Maler, Francois Yergau, and John Cowan, Editors. World Wide Web Consortium, 04 February 2004, edited in place 15 April 2004. This version of the XML 1.1 Recommendation is http://www.w3.org/TR/2004/REC-xml-20040204. The latest version of XML 1.1 is available at http://www.w3.org/TR/xml11.

A. Acknowledgements (Non-Normative)

This document is the work of the W3C Web Services Service Description Working Group. Group .

Members of the Working Group are (at the time of writing, and by alphabetical order): Adi Sakala (IONA Technologies), Alan Davies (SeeBeyond), David Booth (W3C), Allen Brookes (Rogue Wave Softwave), Amelia Lewis (TIBCO/Extensibility), Arthur Ryman (IBM), Bijan Parsia (University of Maryland), Dale Moberg (Cyclone Commerce), Dan Kulp (IONA Technologies), David Booth (W3C), Dietmar Gaertner (Software AG), Don Mullen (TIBCO Software), Erik Ackerman (Lexmark), Helen Chen (Agfa-Gevaert N. V.), Roberto Chinnici (Sun Microsystems), Ugo Corda (SeeBeyond), Glen Daniels (Sonic Software), Paul Downey (British Telecommunications), Youenn Fablet (Canon), Martin Gudgin (Microsoft Corporation), Hugo Haas (W3C), Hao He (The Thomson Corporation), Tom Jordahl (Macromedia), deleted text: Igor Sedukhin (Computer Associates), Ingo Melzer (DaimlerChrysler Research and Technology), Jacek Kopecky (Systinet), Jean-Jacques Moreau (Canon), (Digital Enterprise Research Institute (DERI)), Amelia Lewis (TIBCO Software, Inc.), Kevin Canyang Liu (SAP), Jonathan Marsh (Microsoft Corporation), Peter Madziak (Agfa-Gevaert N. V.), Josephine Micallef (SAIC - Telcordia Technologies), Jeff Mischkinsky (Oracle Corporation), Dale Moberg (Cyclone Commerce), Jean-Jacques Moreau (Canon), Mark Nottingham (BEA Systems, Inc.), David Orchard (BEA Systems, Inc.), Bijan Parsia (University of Maryland), Arthur Ryman (IBM), Adi Sakala (IONA Technologies), Jeffrey Schlimmer (Microsoft Corporation), Igor Sedukhin (Computer Associates), Jerry Thrasher (Lexmark), Jim Hendler (University of Maryland), Johan Pauhlsson (L'Échangeur), Jonathan Marsh ( <em> Chair </em>, Microsoft Corporation), Kevin Canyang Liu (SAP), Laurent De Teneuille (L'Échangeur), Lily Liu (webMethods, Inc.), Martin Gudgin (Microsoft Corporation), Michael Champion (Software AG), Michael Mahan (Nokia), Michael Mealling (Verisign), Mike Ballantyne (Electronic Data Systems), Mike Davoren (W. W. Grainger), Mike McHugh (W. W. Grainger), Philippe Le Hégaret (W3C), Prasad Yendluri William Vambenepe (Hewlett-Packard Company), Asir Vedamuthu (webMethods, Inc.), deleted text: Roberto Chinnici (Sun Microsystems), Sandeep Kumar (Cisco Systems), Sandra Swearingen (U.S. Department of Defense, U.S. Air Force), Sanjiva Weerawarana (IBM), Steve Graham (Global Grid Forum), Steve Lind (AT&T), Steve Tuecke (Global Grid Forum), Tom Jordahl (Macromedia), Umit Yalcinalp Ümit Yalçınalp (Oracle Corporation), Waqar Sadiq (Electronic Data Systems), William Vambenepe (Hewlett-Packard Company), Youenn Fablet (Canon) Prasad Yendluri (webMethods, Inc.).

Previous members were: Aaron Skonnard (DevelopMentor), Lily Liu (webMethods, Inc.), Don Wright (Lexmark), deleted text: Barbara Zengler (DaimlerChrysler Research and Technology), Jochen Ruetschlin (DaimlerChrysler Research and Technology), Joyce Yang (Oracle Corporation), deleted text: Keith Ballinger (Microsoft), Krishna Sankar (Cisco Systems), Mario Jeckle (DaimlerChrysler Research and Technology), Pallavi Malu (Intel Corporation), William Stumbo (Xerox), Daniel Schutzer (Citigroup), Dave Solo (Citigroup), Stefano Pogliani (Sun Microsystems), William Stumbo (Xerox), Stephen White (SeeBeyond), Barbara Zengler (DaimlerChrysler Research and Technology), Tim Finin (University of Maryland) Maryland), Laurent De Teneuille (L'Echangeur), Johan Pauhlsson (L'Echangeur), Mark Jones (AT&T), Steve Lind (AT&T), Sandra Swearingen (U.S. Department of Defense, U.S. Air Force), Philippe Le Hégaret (W3C), Jim Hendler (University of Maryland), Dietmar Gaertner (Software AG), Michael Champion (Software AG), Don Mullen (TIBCO Software, Inc.), Steve Graham (Global Grid Forum), Steve Tuecke (Global Grid Forum), Michael Mahan (Nokia), Bryan Thompson (Hicks & Associates), Ingo Melzer (DaimlerChrysler Research and Technology), Sandeep Kumar (Cisco Systems), Alan Davies (SeeBeyond), Jacek Kopecky (Systinet), Mike Ballantyne (Electronic Data Systems), Mike Davoren (W. W. Grainger), Dan Kulp (IONA Technologies), Mike McHugh (W. W. Grainger), Michael Mealling (Verisign), Waqar Sadiq (Electronic Data Systems), Yaron Goland (BEA Systems, Inc.).

The people who have contributed to discussions on deleted text: <a href= "mailto:www-ws-desc@w3.org"> www-ws-desc@w3.org are also gratefully acknowledged.

B. Part 2 3 Change Log (Non-Normative)

deleted text: <div class="div2"> <h3> <a name="wsdl-spec-changelog" id="wsdl-spec-changelog"> </a> B.1 WSDL Specification Changes </h3>
Date Author Description
20040730 HH Removed property on wsoap:module in pseudo-schema.
20040730 HH Removed AD Feature HTTP serialization.
20040729 HH Added AD Feature support in HTTP binding.
20040727 HH Clarified interaction between SOAP binding and HTTP binding properties
20040727 HH Renamed http prefix whttp
20040727 SW Implemented Umit's proposal to mark MTOM as one optimization mechanism.
20040726 HH Restricted URI style with regards to QNames and added trailing / in URL-encoded syntax
20040723 HH Addressed issue 246: limited MEP to In-Out, In-Only and Robust In-Only
20040723 HH Addressed issue 226.
20040723 HH Addressed 249: major reorganization of the HTTP binding to be presented in a functional way like the SOAP binding rather than in a syntactical way.
20040722 SW Moved SOAP binding syntax summary to the top per request. Also fixed the value of the binding/@type property in the pseudo-schema to show that its a SOAP binding.
20040722 HH Added HTTP error code attribute on fault binding. Added relationship between instance data and properties in the component model. Addresses issue 166.
20040722 HH Renamed SOAP protocol into underlying protocol.
20040721 HH Set the {type} property of binding for HTTP binding.
20040721 HH Fixes for issue 177.
20040720 HH Cross-referenced Part 1 properties.
20040720 HH Specified default serialization format for HTTP binding, as well as made clear how the defined serialization formats apply constraints on interface operation styles
20040705 JJM Added note to indicate only one element per SOAP body.
20040702 SW Corrected how the SOAP binding is indicated .. I had forgotten about binding/@type!
20040625 SW Made pseudo-syntax consistent with part1
20040624 SW Update the rest of the SOAP binding stuff and consistified everything.
20040624 SW Cleaned up how SOAP modules were described. Added default SOAP MEP stuff.
20040623 SW Added default binding rules about HTTP URI generation.
20040623 SW Added default binding rules about SOAP MEP selection and HTTP Method selection.
20040623 SW Fixed up soapaction default rules
20040623 SW Allowed use of MTOM for payload serialization
20040623 SW Fixed up the wsoap:protocol section
20040618 SW Re-introduced AII and EII entity refs.
20040618 SW Made soap:module compose with nearest-wins rule.
20040606 DO Cleanup on http binding section - had missed some properties. completed removal of @separator
20040604 DO Major rewrite of http binding. Moved to component model, added http properties, added input/output serialization, removed @separator, added self as editor
20040526 SW Removed wsoap:address
20040526 SW Editorial/small corrections per F2F decisions
20040526 SW Made soap binding be mostly attribute based per F2F decision
20040519 SW removed spurious fault element inside binding/operation/{in,out}put from syntax summary
20040519 SW Put in wsoap:module at operation level in the syntax summary (was missing)
20040519 SW Removed old SOAP binding text
20040519 SW Removed wsoap:header
20040519 JJM Added SOAP Address section
20040519 JJM Added SOAP Operation section
20040519 JJM Replace reference to "XML" by "XML1.0"
20040519 JJM Added SOAP Fault section
20040519 JJM Added SOAP Header section
20040519 JJM Added SOAP Module section
20040516 SW Finished writing up soap:binding
20040516 SW Added myself as an editor.
20040514 SW Added default binding rules.
20040514 SW Commented out old totally out of date SOAP binding.
20040514 JJM Rework the binding and module sections. Reindent to match the structure of the HTTP binding.
20040511 JJM Updated SOAP binding pseudo-schema, according to telcon 20040506.
20040511 JJM Updated SOAP binding introduction.
20040401 JJM Fixed one remaining occurrence of "verb" (instead of "method").
20040326 JJM Sanitized ednotes. Added new ednotes indicating the SOAP binding needs work and the HTTP binding is (mostly) OK.
20040326 JJM Added Philippe's note on URIPath, as per telcon 20040325.
20040305 JJM Removed the archaic MIME binding, now superseeded by the HTTP binding anyway.
20040305 JJM Included Philippe's changes to the HTTP binding.
20031103 JJM Fix new non-normative SOAP binding pseudo-schema.
20031102 SW Updated SOAP binding.
20031102 SW Change 1.2 to 2.0 per WG decision to rename.
20030606 JJM Replaced <kw/> by <b/>. Indicated that pseudo-schemas are not normative
20030604 JJM Reformated pseudo-syntax elements to match Part 1 layout
20030529 JCS Incorporated text to resolve Issue 6e
20030523 JJM Commented out MIME binding example; this is primer stuff.
20030523 JJM Added pseudo-syntax to all sections.
20030523 JJM Started converting the fault and headerfault sections to component model.
20030523 JJM Complete the Multipart and x-www-form-urlencoded sections.
20030523 JJM Fixed typos in HTTP binding (in particular added NOT in some section headers).
20030522 JCS Added rules for serializing HTTP response
20030522 JCS Added cardinality to pseudo schema for HTTP binding
20030522 JCS Changes @transport to @protocol for SOAP binding
20030522 JJM Incorporated remaining text from Philippe into the HTTP binding.
20030522 JJM Polished the HTTP binding, split into subsections, added double curly brace escape mechanism, removed pseudo-schema.
20030521 JCS Added rules for @verbDefault/@verb and @location.
20030514 JJM Start converting the HTTP binding to the component model. The next thing to do will be to remove http:urlReplacement, etc. and incorporate instead Philippe's text.
20030313 MJG Changed to Part 3 ( from Part 2 )
20030117 JCS Incorporated resolution for Issue 5 (@encodingStyle). Referenced (rather than in-lined XML Schema).
20030117 JJM Various editorial fixes.
20030116 JCS Updated pseudo and XML Schema.
20030116 JJM Added propertyConstraint section.
20030116 JJM Added soap:module section.
20030115 JCS Incorporated resolutions for Issue 25 (drop @use and @encoding), Issue 51 (headers reference element/type), and attribute roll up into text and schema. Began reworking SOAP HTTP binding to use Infoset model. Removed informative appendices 'Notes on URIs' and example WSDL documents; expect them to appear in the primer. Updated SOAP 1.2 references to CR.
20030114 JJM Removed ednote saying Part 2 is out of synch with Part 1.
20030111 JJM Incorporated resolution for issue 17 (role AII).
20030109 JJM Incorporated resolution for issue 4 (Namespaces).
20020702 JJM Added summary to prefix table.
20020628 JJM Added out-of-synch-with-Part2 and not-soap12-yet ednote.
20020621 JJM Commented out the link to the previous version. There is no previous version for 1.2 right now.
20020621 JJM Rewrote the Notation Conventions section.
20020621 JJM Added reference to part 0 in introduction. Renumbered references.
20020621 JJM Simplified abstract and introduction.
20020621 JJM Obtain the list of WG members from a separate file.
20020621 JJM Updated stylesheet and DTDs to latest XMLP stylesheet and DTDs.
20020621 JJM Deleted placeholder for appendix C "Location of Extensibility Elements", since this is part 1 stuff and extensibility has been reworked anyway.
20020621 JJM Corrected link to issues lists
20020621 JJM Updated title from "WSDL" to "Web Services Description Language". Now refer to part 1 as "Web Services... Part 1: Framework
20020621 JJM Added Jeffrey as an editor :-). Removed Gudge (now on Part 2) :-(
20020411 JJM Fixed typos noticed by Kevin Liu
20020301 JJM Converted the "Schemas" sections
20020301 JJM Converted the "Wire WSDL examples" sections
20020301 JJM Converted the "Notes on URIs" sections
20020301 JJM Converted the "Notational Conventions" sections
20020301 JJM Converted the "References" sections
20020301 JJM Converted the "MIME Binding" section to XML
20020221 JJM Converted the "HTTP Binding" section to XML
20020221 JJM Added placeholders for the "Wire examples" and "Schema" sections
20020221 JJM Converted the "SOAP Binding" section to XML
20020221 JJM Added the Change Log
20020221 JJM Added the Status section
20020221 JJM Simplified the introduction; referred to Part1 for a longer introduction
20020221 JJM Renamed to "Part 2: Bindings"
20020221 JJM Created from http://www.w3.org/TR/2001/NOTE-wsdl-20010315
deleted text: </div> <div class="div2"> <h3> <a name="xml-schema-changes" id="xml-schema-changes"> </a> B.2 XML Schema Changes </h3> <p> The encoding schema has been updated to be compliant with the XML Schema Recommendations ([ <cite> <a href="#XMLSchemaP1"> XML Schema Structures </a> </cite> ] and [ <cite> <a href="#XMLSchemaP2"> XML Schema Datatypes </a> </cite> ]). The table below shows the categories of change. </p> <a name="xml-schema-changes-table" id= "xml-schema-changes-table"> </a> <br /> <table border="1"> <tbody> <tr> <th rowspan="1" colspan="1"> Class </th> <th rowspan="1" colspan="1"> Meaning </th> </tr> <tr> <td rowspan="1" colspan="1"> @@@ </td> <td rowspan="1" colspan="1"> @@@ </td> </tr> </tbody> </table>
deleted text: <p> The table below lists the changes to the encoding schema. </p> <a name="xml-encoding-schema-changes-table" id= "xml-encoding-schema-changes-table"> deleted text: </a> <br /> <table border="1"> <tbody> <tr> <th rowspan="1" colspan="1"> Class </th> <th rowspan="1" colspan="1"> Description </th> </tr> <tr> <td rowspan="1" colspan="1"> @@@ </td> <td rowspan="1" colspan="1"> @@@ </td> </tr> </tbody> </table> </div>