2004-03-26 diff-marked version: 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 component; components; WSDL components and type system components.

WSDL components are interfaces, bindings and services.

Type system components are element declarations deleted text: and type definitions drawn from some type system. The former They define the [local name], [namespace name], [children] and [attributes] properties of an element information item </em> ; the latter define only the [children] and [attributes] properties. .

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

• deleted text: {type definitions} A set of named type definitions, each one isomorphic to a simple or complex type as defined by XML Schema </p> </li> <li> <p> {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. At 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 provides a hint of 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/element 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 kids 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 and element system components, additional extension components MAY be added via extensibility 6. Language Extensibility . Further, additional properties to WSDL and type/element 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>

WSDL definitions are represented in XML by one or more WSDL Information Sets (Infosets), that is one or more definitions element information item s. A WSDL Infoset contains representations for a collection of WSDL components which share a common target namespace. A WSDL Infoset which contains one or more import element information item s 4.2 Importing Descriptions corresponds to a collection with components drawn from multiple target namespaces.

The deleted text: target namespace represents an unambiguous name for the intended semantics of the WSDL Infoset. The targetNamespace URI SHOULD point to a human or machine processable document that directly or indirectly defines the semantics of the WSDL Infoset. MUST be an absolute URI (see [ IETF RFC 2396 ]).

The definitions element information item has the following Infoset properties:

• A [local name] of definitions .

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

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

  • A REQUIRED targetNamespace attribute information item as described below in 2.1.2.1 targetNamespace attribute information item .

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

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

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

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

     • Zero or more include element information item s (see 4.1 Including Descriptions )

     • Zero or more import element information item s (see 4.2 Importing Descriptions )

     • Zero or more namespace-qualified element information item s. The [namespace name] of such element information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".

  3. An OPTIONAL types element information item (see 3. Types ).

  4. Zero or more element information item s from among the following, in any order:

     • interface element information item s (see 2.2.2 XML Representation of Interface Component ).

     • binding element information item s (see 2.8.2 2.9.2 XML Representation of Binding Component ).

     • service element information item s (see 2.12.2 2.13.2 XML Representation of Service Component ).

     • Zero or more namespace-qualified element information item s. The [namespace name] of such element information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".

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-1 .

2.2.1 The Interface Component

An Interface component describes sets sequences of messages that a service sends and/or receives. It does this by grouping related messages into operations. An operation is a set 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.16 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.

• {style default} The default style of message schemas of the operations. If a per-operation value is not specified for this property, then this value becomes the default value {faults} A set of the property. See <a href= "#InterfaceOperation_style_attribute"> <b> 2.3.2.3 style attribute information item with operation [owner] </b> </a> 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 container, the combination of {name} and {target namespace} properties must 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 />?


    [ <operation /> | <feature /> | <property /> ]*



    [ <fault /> | <operation /> | <feature /> | <property /> ]*


  </interface>
</definitions>

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

• A [local name] of interface

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

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

  • A REQUIRED name attribute information item as described below in 2.2.2.1 name attribute information item with interface [owner] .

  • An OPTIONAL extends attribute information item as described below in 2.2.2.2 extends attribute information item .

  • An OPTIONAL styleDefault attribute information item as described below in 2.2.2.3 styleDefault attribute information item .

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

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

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

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

     • Zero or more fault element information item s 2.3.2 XML Representation of Interface Fault Component .

     • Zero or more operation element information item s 2.3.2 2.4.2 XML Representation of Interface Operation Component .

     • Zero or more feature element information item s 2.6.2 2.7.2 XML Representation of Feature Component .

     • Zero or more property element information item s 2.7.2 2.8.2 XML Representation of Property Component .

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

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 2-2 .

Per 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>

The XML representation for an Interface 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"

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

  • A REQUIRED name attribute information item as described below in 2.3.2.1 name attribute information item with fault [owner] .

  • An OPTIONAL element attribute information item as described below in 2.3.2.2 element attribute information item with fault [owner] .

  • Zero or more namespace qualified attribute information item s. The [namespace name] of such attribute information item s 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 item s amongst its [children]. The [namespace name] of such element information item s MUST NOT be "http://www.w3.org/2004/03/wsdl".

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 2-3 .

2.3.1 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 requester. 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 using that uses the pattern via 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 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.4 2.5 Message Reference .)

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

• {style} A URI identifying the rules that were used to construct the {message} {element} properties of {message references}. (See 2.3.1.1 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, deleted text: this specification does not preclude one from having two deleted text: distinct Interface deleted text: Operation components which have sharing the same deleted text: {name} and {target namespace} properties, as long as they are in property but with different {name} properties MAY contain Interface Operation components (with which share the same {name} property. Thus, the {name} and {target namespace} property). </p> <p> For each properties of the Interface Operation component in the {operations} property of components are not sufficient to uniquely identify an Interface component Operation component. In order to uniquely identify an Interface Operation component, one must first identify the combination of {name} Interface component (by QName) and {target namespace} properties must be unique. 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.14 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.

Due 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. Therefore

2.3.2 2.4.2 XML Representation of Interface Operation Component

<definitions>
  <interface>
    <operation
          name="xs:NCName" 
          pattern="xs:anyURI"


          style="<em>xs:anyURI</em>"? >



          style="xs:anyURI"? 
          safe="xs:boolean"? >


      <documentation />?
      [ <feature /> | <property /> | 
        [ <input /> | <output /> | <infault /> | <outfault /> ]+
      ]*
    </operation>
  </interface>
</definitions>

The XML representation for an Interface 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/2003/11/wsdl" "http://www.w3.org/2004/03/wsdl"

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

  • A REQUIRED name attribute information item as described below in 2.3.2.1 2.4.2.1 name attribute information item with operation [owner] .

  • A REQUIRED pattern attribute information item as described below in 2.3.2.2 2.4.2.2 pattern attribute information item with operation [owner] .

  • An OPTIONAL style attribute information item as described below in 2.3.2.3 2.4.2.3 style attribute information item with operation [owner] .

  • An OPTIONAL safe attribute information item as described below in 2.4.2.4 safe attribute information item with operation [owner] .

  • Zero or more namespace qualified attribute information item s. The [namespace name] of such attribute information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "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 element information item s from among the following, in any order:

     • Zero or more input element information item s (see 2.4.2 2.5.2 XML Representation of Message Reference Component ).

     • Zero or more output element information item s (see 2.4.2 2.5.2 XML Representation of Message Reference Component ).

     • Zero or more infault element information item s (see 2.5.2 2.6.2 XML Representation of Fault Reference Component ).

     • Zero or more outfault element information item s (see 2.5.2 2.6.2 XML Representation of Fault Reference Component ).

     • A feature element information item (see 2.6.2 2.7.2 XML Representation of Feature Component ).

     • A property element information item (see 2.7.2 2.8.2 XML Representation of Property Component ).

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

• At least one of the [children] MUST be an input , output , infault , or outfault element information item .

2.3.3 2.4.3 Mapping Interface Operation's XML Representation to Component Properties

The mapping between the properties of the Interface Operation component (see 2.3.1 2.4.1 The Interface Operation Component ) and the XML Representation of the interface operation element information item (see 2.3.2 2.4.2 XML Representation of Interface Operation Component ) is as described in Table 2-3 2-4 .

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 Operatio