Web Services Description Language (WSDL) Version 1.2 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; WSDL components and type system components. WSDL components are messages, interfaces, bindings and services.

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

The properties of the Definitions Component are as follows:

• {messages} A set of named message definitions

• {interfaces} A set of named interface definitions

• {bindings} A set of named binding definitions

• {services} A set of named service definitions

• {type definitions} A set of named type definitions, each one isomorphic to a simple or complex type as defined by XML Schema

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

2.1.2 XML Representation of Definitions Component

WSDL definitions are represented in XML by one or more WSDL Information Sets (Infosets), that is one or more definitions element information items. 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 items 4.2 Importing Descriptions corresponds to a collection with components drawn from multiple target namespaces.

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

The definitions element information item has the following Infoset properties:

• A [local name] of definitions .

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

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

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

  • Zero or more namespace qualified attribute information items. The [namespace name] of such attribute information items MUST NOT be "http://www.w3.org/2003/06/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:

     1. Zero or more include element information items (see 4.1 Including Descriptions)

     2. Zero or more import element information items (see 4.2 Importing Descriptions)

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

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

     1. message element information items (see 2.2.2 XML Representation of Message Component).

     2. interface element information items (see 2.4.2 XML Representation of Interface Component).

     3. binding element information items (see 2.10.2 XML Representation of Binding Component).

     4. service element information items (see 2.13.2 XML Representation of Service Component).

• Zero or more namespace qualified element information items amongst its [children]. Such element information items MUST be a member of one of the element substitution groups allowed at the top-level of a WSDL document as described in 6. Language Extensibility.

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 Message Component

A message component describes the abstract format of a particular message that a Web service sends or receives. The format of a message is typically described in terms of XML element information items and attribute information items. A message binding (see 2.10 Binding) describes how the abstract content is mapped into a concrete format. However, in some cases, the abstract definition may match the concrete representation very closely or exactly for one or more bindings. Such bindings will supply little or no mapping information. However, another binding of the same message definition may require extensive mapping information. For this reason, it is not until the binding is inspected that one can determine "how abstract" a message really is.

Messages are named constructs and can be referred to by QName (see 2.17 QName resolution). For instance, interface components refer to messages in this way (see 2.8 Message Reference).

The properties of the Message Component are as follows:

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

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

• {parts} A list of named part definitions.

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

2.2.2 XML Representation of Message Component

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

• A [local name] of message

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

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

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

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

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

  • An optional documentation element information item (see 5. Documentation).

  • Zero or more part element information items (see 2.3.2 XML Representation of Part Component)

• Zero or more namespace qualified element information items amongst its [children]. Such element information items MUST be a member of one of the element substitution groups related to messages described in 6. Language Extensibility.

2.2.3 Mapping Message's XML Representation to Component Properties

The mapping between the properties of the Message Component (see 2.2.1 The Message Component) and the XML Representation of the message element information item (see 2.2.2 XML Representation of Message Component) is as described in Table 2-1.

2.3.1 The Part Component

A part component describes a portion of a particular message that a web service sends or receives. The format of a part is described by reference to type definition or element declaration components. Such components may be drawn from any appropriate type system. However WSDL makes special recognition of the XML Schema language [XML Schema: Structures],[XML Schema: Datatypes] as the RECOMMENDED type specification language (see 3. Types).

Part components are local to a given message component, they cannot be referred to by QName.

The properties of the Part Component are as follows:

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

• {content reference} A reference to either an element declaration or a type definition component

For each part component in the {parts} property of a given message component the {name} property MUST be unique.

2.3.2 XML Representation of Part Component

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

• A [local name] of part

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

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

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

  • One of the following:

    • An element attribute information item as described below in 2.3.2.2 element attribute information item.

    • A type attribute information item as described below in 2.3.2.3 type attribute information item.

    • A namespace qualified attribute information item in a namespace other than "http://www.w3.org/2003/06/wsdl" indicating the validation rules for this part in an alternative schema language.

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

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

  • An optional documentation element information item (see 5. Documentation) amongst its [children].

  • Zero or more namespace qualified element information items. Such element information items MUST be a member of one of the element substitution groups related to message parts described in 6. Language Extensibility.

A part carries information about its type system by the reference contained in the type, element, or alternative qualified attribute information item. The schema language used is determined by examining the referred-to namespace and associating it with an imported or embedded schema. WSDL uses the type and element attribute information items to refer to constructs in XML Schema [XML Schema: Structures],[XML Schema: Datatypes]. Alternative schema languages may re-use these attribute information items if appropriate. If the concepts embodied by the type and element attribute information item are not appropriate for an alternative schema language, that language should specify an alternative attribute information item with prescribed semantics. Such attribute information items are not defined by this specification.

2.3.3 Mapping Part's XML Representation to Component Properties

The mapping between the properties of the Part Component (see 2.3.1 The Part Component) and the XML Representation of the part element information item (see 2.3.2 XML Representation of Part Component) is as described in Table 2-1.

2.4.1 The Interface Component

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

• {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.4.2 XML Representation of Interface Component

The XML representation for an interface definition 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/06/wsdl"

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

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

  • An optional extends attribute information item as described below in 2.4.2.2 extends attribute information item.

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

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

  • An optional documentation element information item (see 5. Documentation).

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

    • Zero or more operation element information items 2.7.2 XML Representation of Interface Operation Component.

    • Zero or more feature element information items 2.5.2 XML Representation of Feature Component.

    • Zero or more property element information items 2.6.2 XML Representation of Property Component.

• Zero or more namespace qualified element information items amongst its [children]. Such element information items MUST be a member of one of the element substitution groups related to interfaces described in 6. Language Extensibility.

2.4.3 Mapping Interface's XML Representation to Component Properties

The mapping between the properties of the Interface Component (see 2.4.1 The Interface Component) and the XML Representation of the interface element information item (see 2.4.2 XML Representation of Interface Component) is as described in Table 2-1.

2.5.1 The Feature Component

A feature component describes a particular feature that a Web service accepts or requires in particular interactions. Features can be engaged in inbound, outbound messages, or both. Features in the feature component are identified by their URI. Unless otherwise specified, recognizing a feature's URI is assumed to be semantically equivalent to understanding the feature's specification.

The properties of the Feature Component are as follows:

• {name} A URI as defined by [IETF RFC 2396].

• {required} A boolean value.

2.5.2 XML Representation of Feature Component

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

• A [local name] of feature

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

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

  • A uri attribute information item as described below in 2.5.2.1 uri attribute information item with feature [owner].

  • An optional required attribute information item as described below in 2.5.2.2 required attribute 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/2003/06/wsdl".

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

  • An optional documentation element information item (see 5. Documentation).

  • Zero or more namespace qualified element information items amongst its [children]. Such element information items MUST be a member of one of the element substitution groups related to features described in 6. Language Extensibility.

2.5.3 Mapping Feature's XML Representation to Component Properties

The mapping between the properties of the Feature Component (see 2.5.1 The Feature Component) and the XML Representation of the feature element information item (see 2.5.2 XML Representation of Feature Component) is as described in Table 2-1.

2.6.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} A URI as defined by [IETF RFC 2396].

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

2.6.2 XML Representation of Property Component

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

• A [local name] of property

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

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

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

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

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

  • An optional documentation element information item (see 5. Documentation).

  • One element information item from among the following:

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

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

  • Zero or more namespace qualified element information items amongst its [children]. Such element information items MUST be a member of one of the element substitution groups related to properties described in 6. Language Extensibility.

<property>
  <value>
    xs:anySimpleType
  </value>
</property>

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

2.6.3 Mapping Property's XML Representation to Component Properties

The mapping between the properties of the Property Component (see 2.6.1 The Property Component) and the XML Representation of the property element information item (see 2.6.2 XML Representation of Property Component) is as described in Table 2-1.

2.7.1 The Interface Operation Component

An interface operation component describes an operation that a given interface supports. An operation is a set of message references and an associated message pattern. Message references are references either to messages accepted by this operation (input messages), or messages sent by this operation (output messages).Such messages may be ordinary messages or fault messages.

Interface operation components are local to interface components, they cannot be referred to by QName, despite having both {name} and {target namespace} properties

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 pattern} A URI identifying the message pattern used by the operation

• {message references} A set of message reference components for the ordinary messages the operation accepts or sends

• {fault references} A set of fault reference components for the fault messages the operation accepts or sends

• {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.

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.

2.7.2 XML Representation of Interface Operation Component

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/06/wsdl"

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

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

  • A pattern attribute information item as described below in 2.7.2.2 pattern attribute 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/2003/06/wsdl".

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

  • An optional documentation element information item (see 5. Documentation).

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

    • Zero or more input element information items (see 2.8.2 XML Representation of Message Reference Component).

    • Zero or more output element information items (see 2.8.2 XML Representation of Message Reference Component).

    • Zero or more infault element information items (see 2.9.2 XML Representation of Fault Reference Component).

    • Zero or more outfault element information items (see 2.9.2 XML Representation of Fault Reference Component).

• Zero or more element information items amongst its [children] from among the following, in any order:

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

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

• Zero or more namespace qualified element information items amongst its [children]. Such element information items MUST be a member of one of the element substitution groups related to interface operations described in 6. Language Extensibility.

2.7.3 Mapping Interface Operation's XML Representation to Component Properties

The mapping between the properties of the Interface Operation Component (see 2.7.1 The Interface Operation Component) and the XML Representation of the interface element information item (see 2.7.2 XML Representation of Interface Operation Component) is as described in Table 2-1.

2.8.1 The Message Reference Component

A message reference component refers to a named message that forms part of an operation.

Message reference components are local to a given interface operation component, they cannot be referred to by QName

The properties of the Message Reference Component are as follows:

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

• {direction} One of in or out.

• {message} A reference, by QName (see 2.17 QName resolution), to a named message component.

For each message reference component in the {message references} and {fault references} properties of an interface operation component the {name} property must be unique.

2.8.2 XML Representation of Message Reference Component

The XML representation for a 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/2003/06/wsdl"

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

  • A name attribute information item as described below in 2.8.2.1 name attribute information item with input, or output [owner].

  • A message attribute information item as described below in 2.8.2.2 message attribute information item with input, or output [owner].

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

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

  • An optional documentation element information item (see 5. Documentation).

  • Zero or more namespace qualified element information items. Such element information items MUST be a member of one of the element substitution groups related to input, output or fault children of interface operations described in 6. Language Extensibility.

2.8.3 Mapping Message Reference's XML Representation to Component Properties

The mapping between the properties of the Message Reference Component (see 2.8.1 The Message Reference Component) and the XML Representation of the message reference element information item (see 2.8.2 XML Representation of Message Reference Component) is as described in Table 2-1.

2.9.1 The Fault Reference Component

A fault reference component refers to named fault messages that form part of an operation.

Fault reference components are local to a given interface operation component, they cannot be referred to by QName.

The properties of the Fault Reference Component are as follows:

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

• {direction} One of in or out.

• {messages} A set of references, by QName (see 2.17 QName resolution), to named message components.

For each fault reference component in the{fault references} properties of an interface operation component the {name} property must be unique.

2.9.2 XML Representation of Fault Reference Component

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

• A [local name] of infault or outfault

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

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

  • A name attribute information item as described below in 2.9.2.1 name attribute information item with infault or outfault [owner].

  • A messages attribute information item as described below in 2.9.2.2 messages attribute information item with infault or outfault [owner].

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

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

  • An optional documentation element information item (see 5. Documentation).

  • Zero or more namespace qualified element information items. Such element information items MUST be a member of one of the element substitution groups related to infault or outfault children of interface operations described in 6. Language Extensibility.

2.9.3 Mapping Fault Reference's XML Representation to Component Properties

The mapping between the properties of the Fault Reference Component (see 2.8.1 The Message Reference Component) and the XML Representation of the fault reference element information item (see 2.9.2 XML Representation of Fault Reference Component) is as described in Table 2-1.

2.10.1 The Binding Component

A binding component described a concrete binding of an interface component and associated operations to a particular concrete message format and transmission protocol.

No concrete binding details are given in this specification. The companion specification, WSDL (Version 1.2): Bindings [WSDL 1.2 Bindings] defines such bindings for SOAP 1.1 [SOAP 1.1], SOAP 1.2 [SOAP 1.2 Part 1: Messaging Framework], HTTP [IETF RFC 2616] and MIME [IETF RFC 2045]. 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.

Bindings are named constructs and can be referred to by QName (see 2.17 QName resolution). For instance, service 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} A named interface definition

• {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.10.2 XML Representation of Binding Component

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/2003/06/wsdl"

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

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

  • An interface attribute information item as described below in 2.10.2.2 interface attribute 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/2003/06/wsdl".

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

  • An optional documentation element information item (see 5. Documentation).

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

    • 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.5.2 XML Representation of Feature Component).

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

• Zero or more namespace qualified element information items amongst its [children]. Such element information items MUST be a member of one of the element substitution groups related to bindings described in 6. Language Extensibility. Such element information items are considered to be binding extension elements (see 2.10.2.3 Binding extension elements).

2.10.3 Mapping Binding's XML Representation to Component Properties

The mapping between the properties of the Binding Component (see 2.10.1 The Binding Component) and the XML Representation of the binding element information item (see 2.10.2 XML Representation of Binding Component) is as described in Table 2-1.

2.11.1 The Binding Operation Component

A binding operation component describes a concrete binding for a particular operation of an interface to a particular concrete message format.

Binding operation components are local to a given binding component

The properties of the Binding Operation Component are as follows:

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

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

• {messages} A set of binding message reference components

For each binding operation component in the {operations} property of a binding component the combination of {name} and {target namespace} properties must be unique.

2.11.2 XML Representation of Binding Operation Component

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/2003/06/wsdl"

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

  • A name attribute information item as described below in 2.11.2.1 name attribute 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/2003/06/wsdl".

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

  • An optional documentation element information item (see 5. Documentation).

  • 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 infault element information items (see 2.12 Binding Message Reference )

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

• Zero or more element information items amongst its [children] from among the following, in any order:

  • 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]. Such element information items MUST be a member of one of the element substitution groups related to binding operations described in 6. Language Extensibility. 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 binding element information item (see 2.11.2 XML Representation of Binding Operation Component) is as described in Table 2-1.

2.12.1 The Binding Message Reference Component

A binding message reference component describes a concrete binding for a particular message in an operation to a particular concrete message format.

Binding message reference components are local to a given binding operation component, they cannot be referred to by QName.

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

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

• {direction} One of in or out

For each binding message reference component in the {messages} property of a binding operation component the {name} property must be unique.

2.12.2 XML Representation of Binding Message Reference Component

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

• A [local name] of input , output , infault or outfault .

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

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

  • An optional name attribute information item as described below in 2.12.2.1 name attribute information item with input, output or 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/2003/06/wsdl".

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

  • An optional documentation element information item (see 5. Documentation).

  • Zero or more namespace qualified element information items. Such element information items MUST be a member of one of the element substitution groups related to input, output or fault children of binding operations described in 6. Language Extensibility. 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 2-1.

2.13.1 The Service Component

A service component describes one and only one interface that a service provides, and the endpoints it is provided over.

Service 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].

• {target resource} A URI as defined by [IETF RFC 2396].

• {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

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

• A [local name] of service

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

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

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

  • An optional targetResource attribute information item as described below in 2.13.2.2 targetResource attribute information item with service [owner].

  • A mandatory interface attribute information item as described below in 2.13.2.3 interface attribute 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/2003/06/wsdl".

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