Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language

2.1.1 The Definitions Component

At the abstract level, the Definitions component is just a container for two categories of components; WSDL components and type system components.

WSDL components are interfaces, bindings and services.

Type system components are element declarations drawn from some type system. They define the [local name], [namespace name], [children] and [attributes] properties of an element information item.

The properties of the Definitions component are as follows:

• {interfaces} A set of named interface definitions

• {bindings} A set of named binding definitions

• {services} A set of named service definitions

• {element declarations} A set of named element declarations, each one isomorphic to a global element declaration as defined by XML Schema

The set of interfaces/binding/services/etc. available in the Definitions component include those that are defined within the component itself and those that are imported and/or included. Note that at the component model level, there is no distinction between directly defined components vs. imported/included components.

The components directly defined within a single Definitions component are said to belong to the same target namespace. The target namespace therefore groups a set of related component definitions and represents an unambiguous name for the intended semantics of the components. The target namespace URI SHOULD point to a human or machine processable document that directly or indirectly defines the intended semantics of those components.

Note that it is RECOMMENDED that the value of the targetNamespace attribute information item SHOULD be a dereferencible URI and that it resolve to a WSDL document which provides service description information for that namespace.

If a service description is split into multiple documents (which may be combined as needed via 4.1 Including Descriptions), then the targetNamespace attribute information item SHOULD resolve to a master document which includes all the WSDL documents needed for that service description. This approach enables the WSDL component designators' fragment identifiers to be properly resolvable.

Imported components have different target namespace values from the Definitions component that is importing them. Thus importing is the mechanism to use components from one namespace in another set of definitions.

Each WSDL or type system component MUST be uniquely identified by its qualified name. That is, if two distinct components of the same kind (Interface, Binding etc.) are in the same target namespace, then their QNames MUST be unique. However, different kinds of components (e.g., an Interface component and a Binding component) MAY have the same QName. Thus, QNames of components must be unique within the space of those components in a given target namespace.

In addition to WSDL components and type system components, additional extension components MAY be added via extensibility 6. Language Extensibility. Further, additional properties to WSDL and type system components MAY also be added via extensibility.

2.1.2 XML Representation of Definitions Component

<definitions
      targetNamespace="xs:anyURI" >
  <documentation />?
  [ <import /> | <include /> ]*
  <types />?
  [ <interface /> | <binding /> | <service /> ]*
</definitions>

2.1.3 Mapping Definitions' XML Representation to Component Properties

The mapping between the properties of the Definitions component (see 2.1.1 The Definitions Component) and the XML Representation of the definitions element information item (see 2.1.2 XML Representation of Definitions Component) is described in Table 2.

2.2.1 The Interface Component

An Interface component describes sequences of messages that a service sends and/or receives. It does this by grouping related messages into operations. An operation is a sequence of input and output messages, an interface is a set of operations.

An interface can optionally extend one or more other interfaces. In such cases the interface contains the operations of the interfaces it extends, along with any operations it defines. The interfaces a given interface extends MUST NOT themselves extend that interface either directly or indirectly.

Interfaces are named constructs and can be referred to by QName (see 2.17 QName resolution). For instance, Binding components refer to interfaces in this way.

The properties of the Interface component are as follows:

• {name} An NCName as defined by [XML Namespaces].

• {target namespace} A namespace name, as defined in [XML Namespaces].

• {extended interfaces} A set of named interface definitions which this interface extends.

• {faults} A set of named interface fault definitions.

• {operations} A set of named interface operation definitions.

• {features} A set of named feature definitions.

• {properties} A set of named property definitions.

For each Interface component in the {interfaces} property of a definitions container, the combination of {name} and {target namespace} properties MUST be unique.

2.2.2 XML Representation of Interface Component

<definitions>
  <interface
        name="xs:NCName" 
        extends="list of xs:QName"?
        styleDefault="xs:anyURI"? >
    <documentation />?
    [ <fault /> | <operation /> | <feature /> | <property /> ]*
  </interface>
</definitions>

2.2.3 Mapping Interface's XML Representation to Component Properties

The mapping between the properties of the Interface component (see 2.2.1 The Interface Component) and the XML Representation of the interface element information item (see 2.2.2 XML Representation of Interface Component) is as described in Table 3.

Note that, per 2.2.1 The Interface Component, the Interface components in the {extended interfaces} property of a given Interface component MUST NOT contain that Interface component in any of their {extended interfaces} properties, that is to say, recursive extension of interfaces is disallowed.

2.3.1 The Interface Fault Component

An Interface Fault component describes a fault that MAY be occur during execution of an operation of the interface. The Interface Fault component declares a fault by naming it and indicating the content or payload of the fault message. When and how the fault message flows is indicated by the Interface Operation component 2.4 Interface Operation.

The reason the Interface Fault component is a property of the Interface component is because that provides a convenient mechanism to declare a set of fault message types and then indicate which operations use those types, thus allowing one to easily indicate that the same fault message type can occur in multiple operations.

The properties of the Interface Fault component are as follows:

• {name} An NCName as defined by [XML Namespaces].

• {element} A reference to an XML element declaration in the {element declarations} property of 2.1.1 The Definitions Component. This element represents the content or "payload" of the fault.

If a non-XML type system is in use (as considered in 3.2 Using Other Schema Languages) then additional properties would need to be added to the Fault Component (along with extensibility attributes to its XML representation) to allow associating such message types with the message reference.

For each Interface Fault component in the {faults} property of an Interface component, the combination of {name} and {target namespace} properties must be unique.

Interface Fault components are local to Interface components; they cannot be referred to by QName, despite having both {name} and {target namespace} properties. That is, two Interface components sharing the same {target namespace} property but with different {name} properties MAY contain Interface Fault components which share the same {name} property. Thus, the {name} and {target namespace} properties of the Interface Fault components are not sufficient to form the unique identity of an Interface Fault component. To uniquely identify an Interface Fault component one must first identify the Interface component (by QName) and then identify the Interface Fault within that Interface component (by a further QName).

In cases where, due to an interface extending one or more other interfaces, two or more Interface Faults components have the same value for their {name} and {target namespace} properties, then the component models of those Interface Fault components MUST be equivalent (see 2.15 Equivalence of Components). If the Interface Fault components are equivalent then they are considered to collapse into a single component. It is an error if two Interface Fault components have the same value for their {name} and {target namespace} properties but are not equivalent.

Note that, due to the above rules, if two interfaces that have the same value for their {target namespace} property also have one or more faults that have the same value for their {name} property then those two interfaces cannot both form part of the derivation chain of a derived interface unless those faults are the same fault.

2.3.2 XML Representation of Interface Fault Component

<definitions>
  <interface>
    <fault
          name="xs:NCName" 
          element="xs:QName"? >
      <documentation />?
    </fault>
  </interface>
</definitions>

2.3.3 Mapping Interface Fault's XML Representation to Component Properties

The mapping between the properties of the Interface Fault component (see 2.3.1 The Interface Fault Component) and the XML Representation of the fault element information item (see 2.3.2 XML Representation of Interface Fault Component) is as described in Table 4.

2.4.1 The Interface Operation Component

An Interface Operation component describes an operation that a given interface supports. An operation is an interaction with the service consisting of a set (ordinary and fault) messages exchanged between the service and the other roles involved in the interaction, in particular the service requestor. The sequencing and cardinality of the messages involved in a particular interaction is governed by the message exchange pattern used by the operation (see {message exchange pattern} property).

A message exchange pattern defines placeholders for messages, the participants in the pattern (i.e., the sources and sinks of the messages), and the cardinality and sequencing of messages exchanged by the participants. The message placeholders are associated with specific message types by the operation that uses the pattern by means of message and fault references (see {message references} and {fault references} properties). The service whose operation is using the pattern becomes one of the participants of the pattern. This specification does not define a machine understandable language for defining message exchange patterns, nor does it define any specific patterns. The companion specification, [WSDL 2.0 Message Exchange Patterns] defines a set of such patterns and defines identifying URIs any of which MAY be used as the value of the {message exchange pattern} property.

The properties of the Interface Operation component are as follows:

• {name} An NCName as defined by [XML Namespaces].

• {target namespace} A namespace name, as defined in [XML Namespaces].

• {message exchange pattern} A URI identifying the message exchange pattern used by the operation. This URI MUST be an absolute URI (see [IETF RFC 2396]).

• {message references} A set of Message Reference components for the ordinary messages the operation accepts or sends. (See 2.5 Message Reference.)

• {fault references} A set of Fault Reference components for the fault messages the operation accepts or sends. (See 2.6 Fault Reference.)

• {style} A URI identifying the rules that were used to construct the {element} properties of {message references}. (See 2.4.1.1 Operation Style.) This URI MUST be an absolute URI (see [IETF RFC 2396]).

• {safety} A boolean indicating whether the operation is asserted to be safe (as defined in Section 3.5 of [Web Architecture]) for users of the described service to invoke. If this property is false or is not set, then no assertion has been made about the safety of the operation, thus the operation MAY or MAY NOT be safe. However, an operation SHOULD be marked safe if it meets the criteria for a safe interaction defined in Section 3.5 of [Web Architecture]. The default value of this property is false.

• {features} A set of named feature definitions used by the operation

• {properties} A set of named property definitions used by the operation

For each Interface Operation component in the {operations} property of an Interface component, the combination of {name} and {target namespace} properties MUST be unique.

Interface Operation components are local to Interface components; they cannot be referred to by QName, despite having both {name} and {target namespace} properties. That is, two Interface components sharing the same {target namespace} property but with different {name} properties MAY contain Interface Operation components which share the same {name} property. Thus, the {name} and {target namespace} properties of the Interface Operation components are not sufficient to uniquely identify an Interface Operation component. In order to uniquely identify an Interface Operation component, one must first identify the Interface component (by QName) and then identify the Interface Operation within that Interface component (by a further QName).

In cases where, due to an interface extending one or more other interfaces, two or more Interface Operation components have the same value for their {name} and {target namespace} properties, then the component models of those Interface Operation components MUST be equivalent (see 2.15 Equivalence of Components). If the Interface Operation components are equivalent then they are considered to collapse into a single component. It is an error if two Interface Operation components have the same value for their {name} and {target namespace} properties but are not equivalent.

Note that, due to the above rules, if two interfaces that have the same value for their {target namespace} property also have one or more operations that have the same value for their {name} property then those two interfaces cannot both form part of the derivation chain of a derived interface unless those operations are the same operation.

2.4.2 XML Representation of Interface Operation Component

<definitions>
  <interface>
    <operation
          name="xs:NCName" 
          pattern="xs:anyURI"
          style="xs:anyURI"? 
          safe="xs:boolean"? >
      <documentation />?
      [ <feature /> | <property /> | 
        [ <input /> | <output /> | <infault /> | <outfault /> ]+
      ]*
    </operation>
  </interface>
</definitions>

2.4.3 Mapping Interface Operation's XML Representation to Component Properties

The mapping between the properties of the Interface Operation component (see 2.4.1 The Interface Operation Component) and the XML Representation of the operation element information item (see 2.4.2 XML Representation of Interface Operation Component) is as described in Table 5.

2.4.4 RPC Style

The RPC style is selected by assigning to an Interface Operation component's {style} property the value http://www.w3.org/2004/03/wsdl/style/rpc.

The RPC style MUST NOT be used for Interface Operation components whose {message exchange pattern} property has a value other than 'http://www.w3.org/2004/03/wsdl/in-only' or 'http://www.w3.org/2004/03/wsdl/in-out'.

Use of this value indicates that XML Schema [XML Schema: Structures] was used to define the schemas of the {element} properties of all {message reference} components of the Interface Operation component. Those schemas MUST adhere to the rules below.

Note that if the Interface Operation component uses the {message exchange pattern} 'http://www.w3.org/2004/03/wsdl/in-only' then there is no output element and hence the rules which refer to the output element do not apply.

• The content model of input and output {element} elements are defined using a complex type that contains a sequence from XML Schema.

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

• The sequence MUST contain only local element children. Note that these child elements MAY contain the following attributes: nillable, minOccurs and maxOccurs.

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

• The LocalPart of the output element's QName is obtained by concatenating the name of the operation and the string value "Response", i.e. concat(operation/@name,"Response").

• Input and output elements MUST both be in the same namespace.

• The complex type that defines the body of an input or an output element MUST NOT contain any attributes.

• If elements with the same qualified name appear as children of both the input and output elements, then they MUST both be declared using the same type.

• The input or output sequence MUST NOT contain multiple children elements declared with the same name.

<xs:attribute name="signature" type="wrpc:signatureType"/>

<xs:simpleType name="signatureType">
  <xs:list itemType="wrpc:signatureItemType"/>
</xs:simpleType>

<xs:simpleType name="signatureItemType">
  <xs:union memberTypes="wrpc:directionToken xsd:QName"/>
</xs:simpleType>

<xs:simpleType name="directionToken">
  <xs:restriction base="xs:token">
    <xs:enumeration value="#in"/>
    <xs:enumeration value="#out"/>
    <xs:enumeration value="#inout"/>
    <xs:enumeration value="#return"/>
  </xs:restriction>
</xs:simpleType>
	  
	   

2.5.1 The Message Reference Component

A Message Reference component associates to a message exchanged in an operation an XML element declaration that specifies its message content.

Message Reference components are identified by the role the message plays in the {message exchange pattern} that the operation is using. That is, a message exchange pattern defines a set /meof placeholder messages that participate in the pattern and assigns them unique names within the pattern. The purpose of a Message Reference component is to associate an actual message type (XML element declaration or some other declaration (see 3.2 Using Other Schema Languages) for message content) with the message that will perform a specific role in the message exchange pattern.

The properties of the Message Reference component are as follows:

• {message label} An NCName as defined by [XML Namespaces]. This property identifies the role this message plays in the {message exchange pattern} of the Interface Operation component this is contained within. The value of this property MUST match the name of a placeholder message defined by the message exchange pattern.

• {direction} One of in or out indicating whether the message is coming to the service or going from the service, respectively. The direction MUST be the same as the direction of the message identified by the {message label} property in the {message exchange pattern} of the Interface Operation component this is contained within.

• {message content model} A token with one of the values #any, #none, or #element. A value of #any indicates that the message content is any single element. A value of #none indicates there is no message content. A value of #element indicates that the message consists of a single element described by the global element declaration reference by the {element} property.

• {element} A reference to an XML element declaration in the {element declarations} property of 2.1.1 The Definitions Component. This element represents the content or "payload" of the message. When the {message content model} property has the value #any or #none the {element} property has no value.

If a non-XML type system is in use (as considered in 3.2 Using Other Schema Languages) then additional properties would need to be added to the Message Reference Component (along with extensibility attributes to its XML representation) to allow associating such message types with the message reference.

For each Message Reference component in the {message references} property of an Interface Operation component, its {message label} property MUST be unique.

2.5.2 XML Representation of Message Reference Component

<definitions>
  <interface>
    <operation>
      <input
            messageLabel="xs:NCName"?
            element="union of xs:QName, xs:Token"? >
        <documentation />?
      </input>
      <output
            messageLabel="xs:NCName"?
            element="union of xs:QName, xs:Token"? >
        <documentation />?
      </output>
    </operation>
  </interface>
</definitions>

2.5.3 Mapping Message Reference's XML Representation to Component Properties

The mapping between the properties of the Message Reference component (see 2.5.1 The Message Reference Component) and the XML Representation of the message reference element information item (see 2.5.2 XML Representation of Message Reference Component) is as described in Table 7.

2.6.1 The Fault Reference Component

A Fault Reference component associates a Fault component that defines the fault message type for a fault that occurs related to a message participating in an operation.

Fault Reference components are identified by the role the related message plays in the {message exchange pattern} that the operation is using. That is, a message exchange pattern defines a set of placeholder messages that participate in the pattern and assigns them unique labels within the pattern. The purpose of a Fault Reference component is to associate an actual Fault component for the fault that will occur with a specific message in the message exchange pattern.

The companion specification [WSDL 2.0 Message Exchange Patterns] defines two fault patterns that a given message exchange pattern may use. For the pattern fault-replaces-message, the message that the fault relates to identifies the message in place of which the declared fault message will occur. Thus, the fault message will travel in the same direction as the message it replaces in the pattern. For the pattern message-triggers-fault, the message that the fault relates to identifies the message after which the indicated fault may occur, in the opposite direction of the referred to message. That is, the fault message will travel in the opposite direction of the message it comes after in the pattern.

More than one Fault Reference component may refer to the same message label. This allows one to indicate that there is more than one type of fault that is related to that message.

The properties of the Fault Reference component are as follows:

• {message label} An NCName as defined by [XML Namespaces]. This property identifies the message this fault relates to among those defined in the {message exchange pattern} property of the Interface Operation component it is contained within. The value of this property MUST match the name of a placeholder message defined by the message exchange pattern.

• {direction} One of in or out indicating whether the fault is coming to the service or going from the service, respectively. The direction MUST be consistent with the direction implied by the fault rule used in the message exchange pattern of the operation. For example, if the fault rule fault-replaces-message is used, then a fault which refers to an outgoing message would have a {direction} property value of out. On the other hand, if the fault rule message-triggers-fault is used, then a fault which refers to an outgoing message would have a {direction} property value of in as the fault travels in the opposite direction of the message.

• {fault reference} A reference to a Fault component in the {faults} property of the parent Interface Operation component's parent Interface component. Identifying the Fault component therefore indirectly defines the actual content or payload of the fault message.

2.6.2 XML Representation of Fault Reference Component

<definitions>
  <interface>
    <operation>
      <infault
            ref="xs:QName"
            messageLabel="xs:NCName"? >
        <documentation />?
      </infault>*
      <outfault
            ref="xs:QName"
            messageLabel="xs:NCName"? >
        <documentation />?
      </outfault>*
    </operation>
  </interface>
</definitions>

2.6.3 Mapping Fault Reference's XML Representation to Component Properties

The mapping between the properties of the Fault Reference component (see 2.6.1 The Fault Reference Component) and the XML Representation of the message reference element information item (see 2.6.2 XML Representation of Fault Reference Component) is as described in Table 8.

2.7.1 The Feature Component

A feature component describes an abstract piece of functionality typically associated with the exchange of messages between communicating parties. Although WSDL poses no constraints on the potential scope of such features, examples might include "reliability", "security", "correlation", and "routing". The presence of a feature component in a WSDL description indicates that the service supports the feature and may require a requester agent that interacts with the service to use that feature. Each Feature is identified by its URI.

The properties of the Feature component are as follows:

• {name} An absolute URI as defined by [IETF RFC 2396]. This URI SHOULD be dereferenceable to a document that directly or indirectly defines the meaning and use of the Feature that it identifies.

• {required} A boolean value. If the {require} property is true, then the requester agent MUST use the Feature that is identified by the {name} URI. Otherwise, the requester agent MAY use the Feature that is identified by the {name} URI. In either case, if the requester agent does use the Feature that is identified by the {name} URI, then the requester agent MUST obey all semantics implied by the definition of that Feature.

<definitions targetNamespace="http://example.com/bank"
     xmlns:ns1="http://example.com/bank">
  <interface name="ns1:Bank">
    <!-- All uses of this interface must be secure -->
    <feature uri="http://example.com/secure-channel"
             required="true"/>
    <operation name="withdrawFunds">
      <!-- This operation must have ACID properties -->
      <feature uri="http://example.com/transaction"
               required="true"/>
      ...
    </operation>
    <operation name="depositFunds">
      <!-- This operation requires notarization -->
      <feature uri="http://example.com/notarization"
               required="true"/>
      ...
    </operation>
  </interface>
  <binding name="ns1:BankSOAPBinding">
  </binding>
  <service name="ns1:BankService"
           interface="tns:Bank">
   <!-- This particular service requires ISO9001
        compliance to be verifiable -->
   <feature uri="http://example.com/ISO9001"
            required="true"/>
   <!-- This service also requires notarization -->
   <feature uri="http://example.com/notarization"
            required="true"/>
   <endpoint>
     ...
   </endpoint>
  </service>
</definitions>

2.7.2 XML Representation of Feature Component

<feature
      uri="xs:anyURI" 
      required="xs:boolean"? >
  <documentation />?
</feature>

2.7.3 Mapping Feature's XML Representation to Component Properties

The mapping between the properties of the Feature component (see 2.7.1 The Feature Component) and the XML Representation of the feature element information item (see 2.7.2 XML Representation of Feature Component) is as described in Table 9.

2.8.1 The Property Component

A Property component describes the set of possible values for a particular property. The permissible values are specified by references to a Schema description. A property is typically used to control a feature's behavior. Properties, and hence property values, can be shared amongst features.

The properties of the Property component are as follows:

• {name} An absolute URI as defined by [IETF RFC 2396]. This URI SHOULD be dereferenceable to a document that directly or indirectly defines the meaning and use of the Property that it identifies.

• {required} A boolean value. If the {required} property is true, then the requester agent MUST use the Property that is identified by the {name} URI. Otherwise, the requester agent MAY use the Property that is identified by the {name} URI. In either case, if the requester agent does use the Property that is identified by the {name} URI, then the requester agent MUST obey all semantics implied by the definition of that Property.

• {value constraint} A type definition constraining the value of the property.

• {value} The value of the property.

2.8.2 XML Representation of Property Component

<property
      uri="xs:anyURI" 
      required="xs:boolean"? >
  <documentation />?
  [ <value /> | <constraint /> ]
</property>

The XML representation for a Property component is an element information item with the following Infoset properties:

• A [local name] of property

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

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

  • A REQUIRED uri attribute information item as described below in 2.8.2.1 uriattribute information item with property [owner].

  • An OPTIONAL required attribute information item as described below in 2.8.2.2 requiredattribute information item with feature [owner].

  • Zero or more namespace qualified attribute information items. The [namespace name] of such attribute information items MUST NOT be "http://www.w3.org/2004/03/wsdl".

• One or more element information items amongst its [children], in order as follows:

  1. An OPTIONAL documentation element information item (see 5. Documentation).

  2. One REQUIRED element information item from among the following:

     • A value element information item as described in 2.8.2.3 valueelement information item with property [parent]

     • A constraint element information item as described in 2.8.2.4 constraintelement information item with property [parent]

  3. Zero or more namespace-qualified element information items amongst its [children]. The [namespace name] of such element information items MUST NOT be "http://www.w3.org/2004/03/wsdl".

<property>
  <value>
    xs:anyType
  </value>
</property>

<property>
  <constraint>
    xs:QName
  </constraint>
</property>

2.8.3 Mapping Property's XML Representation to Component Properties

The mapping between the properties of the Property component (see 2.8.1 The Property Component) and the XML Representation of the property element information item (see 2.8.2 XML Representation of Property Component) is as described in Table 10.

2.9.1 The Binding Component

A Binding component describes a concrete message format and transmission protocol which may be used to define an endpoint (see 2.14 Endpoint). Binding components can be used to describe such information in a re-usable manner for any interface or specifically for a given interface. Furthermore, binding information MAY be specified on a per-operation basis (see 2.11.1 The Binding Operation Component) within an interface in addition to across all operations of an interface.

If a Binding component specifies any operation-specific binding details (by including Binding Operation components) or any fault binding details (by including Binding Fault components) then it MUST specify an interface the Binding component applies to, so as to indicate which interface the operations come from.

Conversely, a Binding component which omits any operation-specific binding details and any fault binding details MAY omit specifying an interface. Binding components that do not specify an interface MAY be used to specify operation-independent binding details for Service components with different interfaces. That is, such Binding components are reusable across one or more interfaces.

No concrete binding details are given in this specification. The companion specification, WSDL (Version 2.0): Bindings[WSDL 2.0 Bindings] defines such bindings for SOAP 1.2 [SOAP 1.2 Part 1: Messaging Framework] and HTTP [IETF RFC 2616]. Other specifications MAY define additional binding details. Such specifications are expected to annotate the Binding component (and its sub-components) with additional properties and specify the mapping between those properties and the XML representation.

A Binding component which defines bindings for an Interface component MUST define bindings for all the operations of that Interface component. The bindings may occur via defaulting rules which allow one to specify default bindings for all operations (see, for example [WSDL 2.0 Bindings]) or by directly listing each Operation component of the Interface component and defining bindings for them. Thus, it is an error for a Binding component to not define bindings for all the Operation components of the Interface component for which the Binding component purportedly defines bindings for.

Bindings are named constructs and can be referred to by QName (see 2.17 QName resolution). For instance, Endpoint components refer to bindings in this way.

The properties of the Binding component are as follows:

• {name} An NCName as defined by [XML Namespaces].

• {target namespace} A namespace name, as defined in [XML Namespaces].

• {interface} An named interface definition indicating the interface for which binding information is being specified.

• {faults} A set of named binding fault definitions.

• {operations} A set of named binding operation definitions.

• {features} A set of named feature definitions.

• {properties} A set of named property definitions.

For each Binding component in the {bindings} property of a definitions container, the combination of {name} and {target namespace} properties must be unique.

2.9.2 XML Representation of Binding Component

<definitions>
  <binding
        name="xs:NCName" 
        interface="xs:QName"? >
    <documentation />?
    [ <fault /> | <operation /> | <feature /> | <property /> ]*
  </binding>
</definitions>

The XML representation for a Binding component is an element information item with the following Infoset properties:

• A [local name] of binding

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

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

  • A REQUIRED name attribute information item as described below in 2.9.2.1 nameattribute information item with binding [owner].

  • An OPTIONAL interface attribute information item as described below in 2.9.2.2 interfaceattribute information item with binding [owner].

  • Zero or more namespace qualified attribute information items. The [namespace name] of such attribute information items MUST NOT be "http://www.w3.org/2004/03/wsdl".

• Zero or more element information items amongst its [children], in order, as follows:

  1. An OPTIONAL documentation element information item (see 5. Documentation).

  2. Zero or more element information items from among the following, in any order:

     • Zero or more fault element information items (see 2.10.2 XML Representation of Binding Fault Component).

     • Zero or more operation element information items (see 2.11.2 XML Representation of Binding Operation Component).

     • Zero or more feature element information items (see 2.7.2 XML Representation of Feature Component).

     • Zero or more property element information items (see 2.8.2 XML Representation of Property Component).

     • Zero or more namespace-qualified element information items. The [namespace name] of such element information items MUST NOT be "http://www.w3.org/2004/03/wsdl". Such element information items are considered to be binding extension elements(see 2.9.2.3 Binding extension elements).

2.9.3 Mapping Binding's XML Representation to Component Properties

The mapping between the properties of the Binding component (see 2.9.1 The Binding Component) and the XML Representation of the binding element information item (see 2.9.2 XML Representation of Binding Component) is as described in Table 11.

2.10.1 The Binding Fault Component

A Binding Fault component describes a concrete binding of a particular fault within an interface to a particular concrete message format. A particular fault of an interface is uniquely identified by the target namespace of the interface and the name of the fault within that interface.

Note that the fault does not occur by itself - it occurs as part of a message exchange as defined by an Interface Operation component (and its binding counterpart the Binding Operation component). Thus, the fault binding information specified in a Binding Fault component describes how faults that occur within a message exchange of an operation will be formatted.

The properties of the Binding Fault component are as follows:

• {fault reference} A QName as defined by [XML Namespaces] which refers to an Interface Fault component in the {faults} property of the Interface component identified by the {interface} property of the parent Binding component. This is the Interface Fault component for which binding information is being specified.

For each Binding Fault component in the {faults} property of a Binding component, the {fault reference} property MUST be unique. That is, one cannot define multiple bindings for the same fault within a given Binding component.

2.10.2 XML Representation of Binding Fault Component

<definitions>
  <binding>
    <fault
          ref="xs:QName" >
      <documentation />?
    </fault>
  </binding>
</definitions>

The XML representation for a Binding Fault component is an element information item with the following Infoset properties:

• A [local name] of fault

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

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

  • A REQUIRED ref attribute information item as described below in 2.10.2.1 refattribute information item with fault [owner].

  • Zero or more namespace qualified attribute information items. The [namespace name] of such attribute information items MUST NOT be "http://www.w3.org/2004/03/wsdl".

• Zero or more element information items amongst its [children], in order, as follows:

  1. An OPTIONAL documentation element information item (see 5. Documentation).

  2. Zero or more namespace-qualified element information items amongst its [children]. The [namespace name] of such element information items MUST NOT be "http://www.w3.org/2004/03/wsdl". Such element information items are considered to be binding fault extension elements as described below (see 2.10.2.2 Binding Fault extension elements).

2.10.3 Mapping Binding Fault's XML Representation to Component Properties

The mapping between the properties of the Binding Fault component (see 2.10.1 The Binding Fault Component) and the XML Representation of the fault element information item (see 2.10.2 XML Representation of Binding Fault Component) is as described in Table 12.

2.11.1 The Binding Operation Component

A Binding Operation component describes a concrete binding of a particular operation of an interface to a particular concrete message format. A particular operation of an interface is uniquely identified by the target namespace of the interface and the name of the operation within that interface.

The properties of the Binding Operation component are as follows:

• {operation reference} A QName as defined by [XML Namespaces] which refers to an Interface Operation component in the {operations} property of the Interface component identified by the {interface} property of the parent Binding component. This is the Interface Operation component for which binding information is being specified.

• {message references} A set of Binding Message Reference components

For each Binding Operation component in the {operations} property of a Binding component, the {operation reference} property MUST be unique. That is, one cannot define multiple bindings for the same operation within a given Binding component.

Interface Operation components are local to Interface components; they cannot be referred to by QName, despite having both {name} and {target namespace} properties. That is, two Interface components sharing the same {target namespace} property but with different {name} properties MAY contain Interface Operation components which share the same {name} property. Thus, the {name} and {target namespace} properties of the Interface Operation components are not sufficient to form the unique identity of an Interface Operation component. To uniquely identify an Interface Operation component one must first identify the Interface component (by QName) and then identify the Interface Operation within that Interface component (by a further QName).

2.11.2 XML Representation of Binding Operation Component

<definitions>
  <binding>
    <operation
          ref="xs:QName" >
      <documentation />?
      [ <input /> | <output /> | <feature /> | <property /> ]*
    </operation>
  </binding>
</definitions>

The XML representation for a Binding Operation component is an element information item with the following Infoset properties:

• A [local name] of operation

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

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

  • A REQUIRED ref attribute information item as described below in 2.11.2.1 refattribute information item with operation [owner].

  • Zero or more namespace qualified attribute information items. The [namespace name] of such attribute information items MUST NOT be "http://www.w3.org/2004/03/wsdl".

• Zero or more element information items amongst its [children], in order, as follows:

  1. An OPTIONAL documentation element information item (see 5. Documentation).

  2. Zero or more element information items from among the following, in any order:

     • Zero or more input element information items (see 2.12 Binding Message Reference )

     • Zero or more output element information items (see 2.12 Binding Message Reference )

     • Zero or more feature element information items

     • Zero or more property element information items

     • Zero or more namespace-qualified element information items amongst its [children]. The [namespace name] of such element information items MUST NOT be "http://www.w3.org/2004/03/wsdl". Such element information items are considered to be binding operation extension elements as described below (see 2.11.2.2 Binding Operation extension elements).

2.11.3 Mapping Binding Operation's XML Representation to Component Properties

The mapping between the properties of the Binding Operation component (see 2.11.1 The Binding Operation Component) and the XML Representation of the operation element information item (see 2.11.2 XML Representation of Binding Operation Component) is as described in Table 13.

2.12.1 The Binding Message Reference Component

A Binding Message Reference component describes a concrete binding of a particular message participating in an operation to a particular concrete message format.

The properties of the Binding Message Reference component are as follows:

• {message label} An NCName as defined by [XML Namespaces]. The value of this property identifies the role that the message for which binding details are being specified plays in the {message exchange pattern} of the Interface Operation component being bound by the containing Binding Operation component.

• {direction} One of in or out indicating whether the message is coming to the service or going from the service, respectively. The direction MUST be the same as the direction of the message identified by the {message label} property in the {message exchange pattern} of the Interface Operation component being bound by the containing Binding Operation component.

For each Binding Message Reference component in the {message references} property of a Binding Operation component, the {message label} property MUST be unique. That is, the same message cannot be bound twice within the same operation.

2.12.2 XML Representation of Binding Message Reference Component

<definitions>
  <binding>
    <operation>
      <input
            messageLabel="xs:NCName"? >
        <documentation />?
      </input>
      <output
            messageLabel="xs:NCName"? >
        <documentation />?
      </output>
    </operation>
  </binding>
</definitions>

The XML representation for a Binding Message Reference component is an element information item with the following Infoset properties:

• A [local name] of input or output .

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

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

  • An OPTIONAL messageLabel attribute information item as described below in 2.12.2.1 messageLabelattribute information item with input or output [owner].

    If the {message exchange pattern} of the Interface Operation component being bound has only one message with a given value for {direction}, then the messageLabel attribute information item is optional for the XML representation of the Binding Message Reference component with that {direction}.

  • Zero or more namespace qualified attribute information items. The [namespace name] of such attribute information items MUST NOT be "http://www.w3.org/2004/03/wsdl".

• Zero or more element information items amongst its [children], in order, as follows:

  1. An OPTIONAL documentation element information item (see 5. Documentation).

  2. Zero or more namespace-qualified element information items amongst its [children]. The [namespace name] of such element information items MUST NOT be "http://www.w3.org/2004/03/wsdl". Such element information items are considered to be binding message reference extension elements, as described below (see 2.12.2.2 Binding Message Reference extension elements).

2.12.3 Mapping Binding Message Reference's XML Representation to Component Properties

The mapping between the properties of the Binding Message Reference component (see 2.12.1 The Binding Message Reference Component) and the XML Representation of the binding element information item (see 2.12.2 XML Representation of Binding Message Reference Component) is as described in Table 14.

2.13.1 The Service Component

A Service component describes a set of endpoints (see 2.14 Endpoint) at which the single interface of the service is provided. The endpoints thus are in effect alternate places at which the service is provided.

Services are named constructs and can be referred to by QName (see 2.17 QName resolution).

The properties of the Service component are as follows:

• {name} An NCName as defined by [XML Namespaces].

• {target namespace} A namespace name, as defined in [XML Namespaces].

• {interface} An Interface component.

• {endpoints} A set of Endpoint components.

For each Service component in the {services} property of a definitions container, the combination of {name} and {target namespace} properties MUST be unique.

2.13.2 XML Representation of Service Component

<definitions>
  <service
        name="xs:NCName" 
        interface="xs:QName" >
    <documentation />?
    <endpoint />+
  </service>
</definitions>

The XML representation for a Service component is an element information item with the following Infoset properties:

• A [local name] of service

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

• Two or more attribute information items amongst its [attributes] as follows:

  • A REQUIRED name attribute information item as described below in 2.13.2.1 nameattribute information item with service [owner].

  • A REQUIRED interface attribute information item as described below in 2.13.2.2 interfaceattribute information item with service [owner].

  • Zero or more namespace qualified attribute information items. The [namespace name] of such attribute information items MUST NOT be "http://www.w3.org/2004/03/wsdl".

• One or more element information item amongst its [children], in order, as follows:

  1. An OPTIONAL documentation element information item (see 5. Documentation).

  2. One or more element information items from among the following, in any order:

     • One or more endpoint element information items (see 2.14.2 XML Representation of Endpoint Component

     • Zero or more namespace-qualified element information items amongst its [children]. The [namespace name] of such element information items MUST NOT be "http://www.w3.org/2004/03/wsdl".

Note that the XML Schema [XML Schema: Structures] type of the element information itemservice as defined in the WSDL schema MAY be used as the basis for defining new elements which can be used as service references in message exchanges. To enable such reuse, the WSDL schema defines the attribute information itemname as optional in the type of the element information itemservice , while it is REQUIRED for the element information itemservice as indicated above.

2.13.3 Mapping Service's XML Representation to Component Properties

The mapping between the properties of the Service component (see 2.13.1 The Service Component) and the XML Representation of the service element information item (see 2.13.2 XML Representation of Service Component) is as described in Table 15.

2.14.1 The Endpoint Component

An Endpoint component defines the particulars of a specific endpoint at which a given service is available.

Endpoint components are local to a given Service component; they cannot be referred to by QName.

The properties of the Endpoint component are as follows:

• {name} An NCName as defined by [XML Namespaces].

• {binding} A named Binding component.

For each Endpoint component in the {endpoints} property of a Service component, the {binding} property (see 2.14.1 The Endpoint Component) MUST either be a Binding component with an unspecified {interface} property (see 2.9.1 The Binding Component or a Binding component with an {interface} property equal to the {interface} property of the Service component.

For each Endpoint component in the {endpoints} property of a Service component, the {name} property MUST be unique.

2.14.2 XML Representation of Endpoint Component

<definitions>
  <service>
    <endpoint
          name="xs:NCName" 
          binding="xs:QName" >
      <documentation />?
    </endpoint>
  </service>+
</definitions>

The XML representation for a Endpoint component is an element information item with the following Infoset properties:

• A [local name] of endpoint .

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

• Two or more attribute information items amongst its [attributes] as follows:

  • A REQUIRED name attribute information item as described below in 2.14.2.1 nameattribute information item with endpoint [owner].

  • A REQUIRED binding attribute information item as described below in 2.14.2.2 bindingattribute information item with endpoint [owner].

  • Zero or more namespace qualified attribute information items. The [namespace name] of such attribute information items MUST NOT be "http://www.w3.org/2004/03/wsdl".

• Zero or more element information item amongst its [children], in order, as follows:

  1. An OPTIONAL documentation element information item (see 5. Documentation).

  2. Zero or more namespace-qualified element information items amongst its [children]. The [namespace name] of such element information items MUST NOT be "http://www.w3.org/2004/03/wsdl". Such element information items are considered to be endpoint extension elements (see 2.14.2.3 Endpoint extension elements).

2.14.3 Mapping Endpoint's XML Representation to Component Properties

The mapping between the properties of the Endpoint component (see 2.14.1 The Endpoint Component) and the XML Representation of the endpoint element information item (see 2.14.2 XML Representation of Endpoint Component) is as described in Table 16.

3.1.1 Importing XML Schema

Importing an XML Schema uses the syntax and semantics of the xs:import mechanism defined by XML Schema [XML Schema: Structures],[XML Schema: Datatypes], with some additional restrictions. The schema components defined in the imported schema are available for reference by QName (see 2.17 QName resolution). Note that only components defined in the schema itself and components included by it via xs:include are available to WSDL. Specifically, components that the schema imports via xs:import are NOT available to WSDL.

A child element information item of the types element information item is defined with the Infoset properties as follows:

• A [local name] of "import".

• A [namespace name] of ""http://www.w3.org/2001/XMLSchema"".

• One or two attribute information items as follows:

  • A REQUIRED namespace attribute information item as described below.

  • An OPTIONAL schemaLocation attribute information item as described below.

3.1.2 Embedding XML Schema

Embedding an XML schema uses the existing top-level xs:schema element information item defined by XML Schema [XML Schema: Structures]. It may be viewed as simply cutting and pasting an existing, stand-alone schema, to a location inside the types element information item.

The schema components defined in the embedded schema are available to WSDL for reference by QName (see 2.17 QName resolution). Note that only components defined in the schema itself and components included by it via xs:include are available to WSDL. Specifically components that the schema imports via xs:import are NOT available to WSDL.

Similarly, components defined in an embedded XML schema are NOT automatically made available to a WSDL description that imported (using wsdl:import ) the description that embeds the schema (see 4.2 Importing Descriptions for more details). For this reason, it is recommended that XML schema documents intended to be shared across several WSDL descriptions be placed in separate documents and imported using xs:import , rather than embedded inside a WSDL document.

Inside an embedded XML schema, the xs:import and xs:include element information items MAY be used to refer to other XML schemas embedded in the same WSDL description, provided that an appropriate value is specified for their schemaLocation attribute information items. The semantics of such element information items are governed solely by the XML Schema specification [XML Schema: Structures].

The xs:schema element information item has the following Infoset properties:

• A [local name] of schema.

• A [namespace name] of "http://www.w3.org/2001/XMLSchema".

• A REQUIRED targetNamespace attribute information item, amongst its [attributes] as described below.

• Additional OPTIONAL attribute information items as specified for the xs:schema element information item by the XML Schema specification.

• Zero or more child element information items as specified for the xs:schema element information item by the XML Schema specification.

3.1.3 References to Element Declarations

Whether embedded or imported, the element declarations present in a schema may be referenced from a Message Reference or Interface Fault component.

A named, global xs:element declaration may be referenced from the element attribute information item of an input , output or fault element information item. The QName is constructed from the targetNamespace of the schema and the value of the name attribute information item of the xs:element element information item. An element attribute information item MUST NOT refer to a global xs:simpleType or xs:complexType definition.

4.1.1 location attribute information item with include [owner]

The location attribute information item has the following Infoset properties:

• A [local name] of location .

• A [namespace name] which has no value.

A location attribute information item is of type xs:anyURI . Its actual value is the location of some information about the namespace identified by the targetNamespace attribute information item of the containing definitions element information item.

If the URI indicated by location is not dereferenceable or does not resolve to a WSDL document then the processor MUST fail immediately. That is, include elements MUST be processed immediately by WSDL processors.

The actual value of the targetNamespace attribute information item of the included WSDL document MUST match the actual value of the targetNamespace attribute information item of the definitions element information item which is the [parent] of the include element information item.

4.2.1 namespace attribute information item

The namespace attribute information item has the following Infoset properties:

• A [local name] of namespace .

• A [namespace name] which has no value.

The namespace attribute information item is of type xs:anyURI . Its actual value indicates that the containing WSDL document MAY contain qualified references to WSDL definitions in that namespace (via one or more prefixes declared with namespace declarations in the normal way). This value MUST NOT match the actual value of the enclosing WSDL document targetNamespace attribute information item. If the import statement results in the import of a WSDL document then the actual value of the namespace attribute information item MUST be identical to the actual value of the imported WSDL document's targetNamespace attribute information item.

4.2.2 location attribute information item with import [owner]

The location attribute information item has the following Infoset properties:

• A [local name] of location .

• A [namespace name] which has no value.

The location attribute information item is of type xs:anyURI . Its actual value is the location of some information about the namespace identified by the namespace attribute information item.

The location attribute information item is optional. This allows WSDL components to be constructed from information other than serialized XML 1.0. It also allows the development of WSDL processors that have a priori (i.e., built-in) knowledge of certain namespaces.

6.1.1 Mandatory extensions

Extension elements can be marked as mandatory by annotating them with a wsdl:required attribute information item (see 6.1.2 requiredattribute information item) with a value of "true". A mandatory extension is an extension that MAY change the meaning of the element to which it is attached, such that the meaning of that element is no longer governed by this specification. Instead, the meaning of an element containing a mandatory extension is governed by the meaning of that extension. Thus, the definition of the element's meaning is delegated to the specification that defines the extension.

An extension that is NOT marked as mandatory MUST NOT invalidate the meaning of any part of the WSDL document. Thus, a NON-mandatory extension merely provides additional description of capabilities of the service. Furthermore, any extension that is NOT marked as mandatory and which is NOT understood, MUST be ignored. Any NOT understood extension attributes MUST be ignored as this specification does not provide a mechanism to mark extension attributes as being required.

6.1.2 required attribute information item

WSDL provides a global attribute information item with the following Infoset properties:

• A [local name] of required .

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

• A [specified] property with a value of "true".

The type of the required attribute information item is xs:boolean.