[W3C] Web Services Description Language (WSDL) Version 1.2 Part 1: Core Language W3C Working Draft 11 June 2003 This version: http://www.w3.org/TR/2003/WD-wsdl12-20030611 Latest version: http://www.w3.org/TR/wsdl12 Previous versions: http://www.w3.org/TR/2003/WD-wsdl12-20030303 Editors: Roberto Chinnici, Sun Microsystems Martin Gudgin, Microsoft Jean-Jacques Moreau, Canon Sanjiva Weerawarana, IBM Research This document is also available in these non-normative formats: postscript, PDF, XML, and plain text. Copyright © 2003 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. ---------------------------------------------------------------------------- Abstract This document describes the Web Services Description Language (WSDL) Version 1.2, an XML language for describing Web services. This specification defines the core language which can be used to describe Web services based on an abstract model of what the service offers. Status of this Document This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C. This is a W3C Working Draft of the Web Services Description Language (WSDL) 1.2 document. This document has been produced as part of the W3C Web Services Activity. The authors of this document are the Web Services Description Working Group members. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress". This is work in progress and does not imply endorsement by, or the consensus of, either W3C or members of the Web Services Description Working Group. Comments on this document are invited and are to be sent to public-ws-desc-comments@w3.org (public archive). It is inappropriate to send discussion emails to this address. Discussion of this document takes place on the public www-ws-desc@w3.org mailing list (public archive). Patent disclosures relevant to this specification may be found on the Working Group's patent disclosure page. A list of current W3C Recommendations and other technical documents can be found at http://www.w3.org/TR. ---------------------------------------------------------------------------- Short Table of Contents 1. Introduction 2. Component Model 3. Types 4. Modularizing WSDL descriptions 5. Documentation 6. Language Extensibility 7. References A. The application/wsdl+xml Media Type B. Acknowledgements (Non-Normative) C. URI References for WSDL constructs (Non-Normative) D. Migrating from WSDL 1.1 to WSDL 1.2 (Non-Normative) E. Examples of Specifications of Extension Elements for Alternative Schema Language Support. (Non-Normative) F. Part 1 Change Log (Non-Normative) ---------------------------------------------------------------------------- Table of Contents 1. Introduction 1.1 Web Service 1.2 Notational Conventions 2. Component Model 2.1 Definitions 2.1.1 The Definitions Component 2.1.2 XML Representation of Definitions Component 2.1.2.1 targetNamespace attribute information item 2.1.3 Mapping Definitions' XML Representation to Component Properties 2.2 Message 2.2.1 The Message Component 2.2.2 XML Representation of Message Component 2.2.2.1 name attribute information item with message [owner] 2.2.3 Mapping Message's XML Representation to Component Properties 2.3 Part 2.3.1 The Part Component 2.3.2 XML Representation of Part Component 2.3.2.1 name attribute information item with part [owner] 2.3.2.2 element attribute information item 2.3.2.3 type attribute information item 2.3.3 Mapping Part's XML Representation to Component Properties 2.4 Interface 2.4.1 The Interface Component 2.4.2 XML Representation of Interface Component 2.4.2.1 name attribute information item with interface [owner] 2.4.2.2 extends attribute information item 2.4.3 Mapping Interface's XML Representation to Component Properties 2.5 Feature 2.5.1 The Feature Component 2.5.2 XML Representation of Feature Component 2.5.2.1 uri attribute information item with feature [owner] 2.5.2.2 required attribute information item with feature [owner] 2.5.3 Mapping Feature's XML Representation to Component Properties 2.6 Property 2.6.1 The Property Component 2.6.2 XML Representation of Property Component 2.6.2.1 uri attribute information item with property [owner] 2.6.2.2 value element information item with property [parent] 2.6.2.3 constraint element information item with property [parent] 2.6.3 Mapping Property's XML Representation to Component Properties 2.7 Interface Operation 2.7.1 The Interface Operation Component 2.7.2 XML Representation of Interface Operation Component 2.7.2.1 name attribute information item with operation [owner] 2.7.2.2 pattern attribute information item with operation [owner] 2.7.3 Mapping Interface Operation's XML Representation to Component Properties 2.8 Message Reference 2.8.1 The Message Reference Component 2.8.2 XML Representation of Message Reference Component 2.8.2.1 name attribute information item with input, or output [owner] 2.8.2.2 message attribute information item with input, or output [owner] 2.8.3 Mapping Message Reference's XML Representation to Component Properties 2.9 Fault Reference 2.9.1 The Fault Reference Component 2.9.2 XML Representation of Fault Reference Component 2.9.2.1 name attribute information item with infault or outfault [owner] 2.9.2.2 messages attribute information item with infault or outfault [owner] 2.9.3 Mapping Fault Reference's XML Representation to Component Properties 2.10 Binding 2.10.1 The Binding Component 2.10.2 XML Representation of Binding Component 2.10.2.1 name attribute information item with binding [owner] 2.10.2.2 interface attribute information item with binding [owner] 2.10.2.3 Binding extension elements 2.10.3 Mapping Binding's XML Representation to Component Properties 2.11 Binding Operation 2.11.1 The Binding Operation Component 2.11.2 XML Representation of Binding Operation Component 2.11.2.1 name attribute information item with operation [owner] 2.11.2.2 Binding operation extension elements 2.11.3 Mapping Binding Operation's XML Representation to Component Properties 2.12 Binding Message Reference 2.12.1 The Binding Message Reference Component 2.12.2 XML Representation of Binding Message Reference Component 2.12.2.1 name attribute information item with input, output or fault [owner] 2.12.2.2 Binding message reference extension elements 2.12.3 Mapping Binding Message Reference's XML Representation to Component Properties 2.13 Service 2.13.1 The Service Component 2.13.2 XML Representation of Service Component 2.13.2.1 name attribute information item with service [owner] 2.13.2.2 targetResource attribute information item with service [owner] 2.13.2.3 interface attribute information item with service [owner] 2.13.3 Mapping Service's XML Representation to Component Properties 2.14 Endpoint 2.14.1 The Endpoint Component 2.14.2 XML Representation of Endpoint Component 2.14.2.1 name attribute information item with endpoint [owner] 2.14.2.2 binding attribute information item with endpoint [owner] 2.14.2.3 Endpoint extension elements 2.14.3 Mapping Endpoint's XML Representation to Component Properties 2.15 Equivalence of components 2.16 Symbol Spaces 2.17 QName resolution 3. Types 3.1 Using W3C XML Schema Description Language 3.1.1 Importing XML Schema 3.1.1.1 namespace attribute information item 3.1.1.2 schemaLocation attribute information item 3.1.2 Embedding XML Schema 3.1.2.1 targetNamespace attribute information item 3.1.3 References to Type and Element Definitions 3.2 Using Other Schema Languages 4. Modularizing WSDL descriptions 4.1 Including Descriptions 4.1.1 location attribute information item with include [owner] 4.2 Importing Descriptions 4.2.1 namespace attribute information item 4.2.2 location attribute information item with import [owner] 5. Documentation 6. Language Extensibility 6.1 Element based extensibility 6.1.1 Mandatory extensions 6.1.2 required attribute information item 6.2 Attribute based extensibility 7. References 7.1 Normative References 7.2 Informative References Appendices A. The application/wsdl+xml Media Type A.1 Registration A.2 Security considerations B. Acknowledgements (Non-Normative) C. URI References for WSDL constructs (Non-Normative) C.1 WSDL URIs C.2 Fragment Identifiers C.3 Extension Elements C.4 Example C.5 Relation to WSDL 1.1 D. Migrating from WSDL 1.1 to WSDL 1.2 (Non-Normative) D.1 Operation Overloading D.2 PortTypes D.3 Ports E. Examples of Specifications of Extension Elements for Alternative Schema Language Support. (Non-Normative) E.1 DTD E.1.1 namespace attribute information item E.1.2 location attribute information item E.1.3 References to Element Definitions E.2 RELAX NG E.2.1 Importing RELAX NG E.2.1.1 ns attribute information item E.2.1.2 href attribute information item E.2.2 Embedding RELAX NG E.2.2.1 ns attribute information item E.2.3 References to Type and Element Definitions F. Part 1 Change Log (Non-Normative) F.1 WSDL Specification Changes ---------------------------------------------------------------------------- 1. Introduction Web Services Description Language (WSDL) provides a model and an XML format for describing Web services. WSDL enables one to separate the description of the abstract functionality offered by a service from concrete details of a service description such as "how" and "where" that functionality is offered. This specification defines a language for describing the abstract functionality of a service as well as a framework for describing the concrete details of a service description. The WSDL Version 1.2 Part 2: Message Patterns specification [WSDL 1.2 Message Patterns] defines define the sequence, direction, and cardinality of abstract messages sent or received by an operation. The WSDL Version 1.2 Part 3: Bindings specification [WSDL 1.2 Bindings] defines a language for describing such concrete details for SOAP 1.2 [SOAP 1.2 Part 1: Messaging Framework], HTTP [IETF RFC 2616] and MIME [IETF RFC 2045]. 1.1 Web Service WSDL describes Web services starting with the messages that are exchanged between the service provider and requester. The messages themselves are described abstractly and then bound to a concrete network protocol and message format. A message consists of a collection of typed data items. An exchange of messages between the service provider and requester is described as an operation. A collection of operations is called an interface. An interface is bound to a concrete protocol and message format via one or more bindings. A binding, and therefore an interface, is accessible via one or more endpoint, each endpoint having its own URI. A service is a collection of endpoints bound to the same interface. WSDL further considers that an interface represents (some of) the behavior of a resource on the World-Wide-Web. A service can thus be seen as a collection of endpoints bound to the same resource. Figure 1-1 shows a service offering a single interface to a resource, but this interface being accessible at multiple addresses (endpoints). [A resource offering a single Web Service] Figure 1-1. A resource offering a single Web Service [SVG 1.0 version] Figure 1-2 shows two services (Service1 and Service2) bound to the same resource (Resource1), but offering different interfaces (Interface1 and Interface2). Interface1 and Interface2 may be related to each other, but this specification is NOT defining what this relationship might be. For example, Interface1 may be an operational interface, may Interface2 might be a management interface. [Two resources and three Web Services] Figure 1-2. Two resources and three Web Services In addition, Figure 1-2 shows a third service (Service3) bound to a different resource (Resource2), and offering a single interface (Interface4). Resource1 and Resource2 are shown as having NO relationship; but they may in fact be related. This relationship can be defined using languages such as RDF, if necessary, but this is outside the scope of this specification. 1.2 Notational Conventions The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [IETF RFC 2119]. This specification uses properties from the XML Information Set [XML Information Set]. Such properties are denoted by square brackets, e.g. [namespace name]. This specification uses namespace prefixes throughout; they are listed in Table 1-1. Note that the choice of any namespace prefix is arbitrary and not semantically significant (see [XML Information Set]). Table 1-1. Prefixes and Namespaces used in this specification Prefix Namespace Notes A normative XML Schema [XML Schema: Structures], [XML Schema: Datatypes] document for the "http://www.w3.org/2003/06/wsdl" namespace can be found at http://www.w3.org/2003/06/wsdl. wsdl "http://www.w3.org/2003/06/wsdl" WSDL documents that do NOT conform to this schema are not valid WSDL documents. WSDL documents that DO conform to this schema and also conform to the other constraints defined in this specification are valid WSDL documents. soap12"http://www.w3.org/2003/06/wsdl/soap12" Defined by WSDL 1.2: Bindings http "http://www.w3.org/2003/06/wsdl/http" [WSDL 1.2 Bindings]. mime "http://www.w3.org/2003/06/wsdl/mime" xs "http://www.w3.org/2001/XMLSchema" Defined in the W3C XML Schema specification [XML Schema: Structures], [XML Schema: xsi "http://www.w3.org/2001/XMLSchema-instance" Datatypes]. Namespace names of the general form "http://example.org/..." and "http://example.com/..." represent application or context-dependent URIs [IETF RFC 2396]. All parts of this specification are normative, with the EXCEPTION of pseudo-schemas, examples, and sections explicitly marked as "Non-Normative". Pseudo-schemas are provided for each component, before the description of this component. 2. Component Model This section describes the conceptual model for WSDL as a set of components with properties, each aspect of a Web service that WSDL can describe having its own property. In addition an XML Infoset representation for these components is provided, along with a mapping from that representation to the various component properties. How the XML Infoset representation of a given set of WSDL components is constructed is outside the scope of this specification. 2.1 Definitions ? [ | ]* ? [ | | | ]* 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: o A targetNamespace attribute information item as described below in 2.1.2.1 targetNamespace attribute information item. o 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.2.1 targetNamespace attribute information item The targetNamespace attribute information item defines the namespace affiliation of top-level components defined in this definitions element information item. Messages, interfaces, bindings and services are top level components. The targetNamespace attribute information item has the following Infoset properties: * A [local name] of targetNamespace * A [namespace name] which has no value The type of the targetNamespace attribute information item is xs:anyURI. 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. Table 2-1. Mapping between Definitions Component Properties and XML Representation Property Mapping The message definitions corresponding to all the message element information items in the [children] {messages} of the definitions element information item, if any, plus any included or imported definitions (see 4. Modularizing WSDL descriptions). The interface definitions corresponding to all the interface element information items in the {interfaces} [children] of the definitions element information item, if any, plus any included or imported definitions (see 4. Modularizing WSDL descriptions). The binding definitions corresponding to all the binding element information items in the [children] {bindings} of the definitions element information item, if any, plus any included or imported definitions (see 4. Modularizing WSDL descriptions). The service definitions corresponding to all the service element information items in the [children] {services} of the definitions element information item, if any, plus any included or imported definitions (see 4. Modularizing WSDL descriptions). The type definition components corresponding to all the type definitions defined as descendants of the types element information item, if any, plus any imported definitions. At a minimum this will include {type definitions} all the types defined by XML Schema simpleType and complexType element information items. It MAY also include any definition from some other type system which describes the [attributes] and [children] properties of an element information item. The element declaration components corresponding to all the element declarations defined as descendants of the types element information item, if any, plus any imported definitions. At a minimum this will {element declarations}include all the global element declarations defined by XML Schema element element information items. It MAY also include any definition from some other type system which describes the [local name], [namespace name], [attributes] and [children] properties of an element information item. 2.2 Message ? * 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: o A name attribute information item as described below in 2.2.2.1 name attribute information item with message [owner]. o 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: o An optional documentation element information item (see 5. Documentation). o 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.2.1 name attribute information item with message [owner] The name attribute information item together with the targetNamespace attribute information item of the definitions element information item forms the QName of the message, The name attribute information item has the following Infoset properties: * A [local name] of name * A [namespace name] which has no value The type of the name attribute information item is xs:NCName. 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. Table 2-1. Mapping between Message Component Properties and XML Representation Property Mapping {name} The actual value of the name attribute information item The actual value of the targetNamespace attribute {target namespace}information item of the [parent] definitions element information item {parts} The list of part definitions corresponding to the part element information items in [children], if any. 2.3 Part ? 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: o A name attribute information item as described below in 2.3.2.1 name attribute information item with part [owner]. o 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. o 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: o An optional documentation element information item (see 5. Documentation) amongst its [children]. o 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.2.1 name attribute information item with part [owner] The name attribute information item identifies a given part element information item inside a given message element information item. The name attribute information item has the following Infoset properties: * A [local name] of name * A [namespace name] which has no value The type of the name attribute information item is xs:NCName. 2.3.2.2 element attribute information item The element attribute information item refers, by QName, to an element declaration component. The element attribute information item has the following Infoset properties: * A [local name] of element * A [namespace name] which has no value The type of the element attribute information item is xs:QName. 2.3.2.3 type attribute information item The type attribute information item refers, by QName, to a type description component. The type attribute information item has the following Infoset properties: * A [local name] of type * A [namespace name] which has no value The type of the type attribute information item is xs:QName. 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. Table 2-1. Mapping between Part Component Properties and XML Representation Property Mapping {name} The actual value of the name attribute information item The element declaration resolved to by the value of the element attribute information item if present, {content reference}otherwise the type definition resolved to by the value of the type attribute information item if present, otherwise a similar construct in some type system as referred to by some other attribute information item 2.4 Interface ? [ | | ]* 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: o A name attribute information item as described below in 2.4.2.1 name attribute information item with interface [owner]. o An optional extends attribute information item as described below in 2.4.2.2 extends attribute information item. o 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: o An optional documentation element information item (see 5. Documentation). o 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.2.1 name attribute information item with interface [owner] The name attribute information item together with the targetNamespace attribute information item of the definitions element information item forms the QName of the interface. The name attribute information item has the following Infoset properties: * A [local name] of name * A [namespace name] which has no value The type of the name attribute information item is xs:NCName. 2.4.2.2 extends attribute information item The extends attribute information item lists the interfaces that this interface derives from. The extends attribute information item has the following Infoset properties: * A [local name] of extends * A [namespace name] which has no value The type of the extends attribute information item is a list of xs:QName. 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. Table 2-1. Mapping between Interface Component Properties and XML Representation Property Mapping {name} The actual value of the name attribute information item The actual value of the targetNamespace attribute {target namespace} information item of the [parent] definitions element information item The set of interface definitions resolved to by the values in the extends attribute information item if {extended interfaces}any, plus the set of interface definitions in the {extended interfaces} property of those interface definitions, otherwise empty. The set of interface operation definitions corresponding to the operation element information {operations} items in [children], if any, plus the set of interface operation definitions in the {operations} property of the interface definitions in {extended interfaces}, if any. The set of feature definitions corresponding to the feature element information items in [children], if {features} any, plus the set of feature definitions in the {features} property of the feature definitions in {extended interfaces}, if any. The set of property definitions corresponding to the property element information items in [children], if {properties} any, plus the set of property definitions in the {properties} property of the property definitions in {extended interfaces}, if any. Note: Per 2.4.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.5 Feature ? 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: o A uri attribute information item as described below in 2.5.2.1 uri attribute information item with feature [owner]. o An optional required attribute information item as described below in 2.5.2.2 required attribute information item with feature [owner]. o 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: o An optional documentation element information item (see 5. Documentation). o 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.2.1 uri attribute information item with feature [owner] The uri attribute information item specifies the URI of the feature. The uri attribute information item has the following Infoset properties: * A [local name] of uri * A [namespace name] which has no value The type of the uri attribute information item is xs:anyURI. 2.5.2.2 required attribute information item with feature [owner] The required attribute information item specifies whether the use of the feature is mandatory or optional. The required attribute information item has the following Infoset properties: * A [local name] of required * A [namespace name] which has no value The type of the required attribute information item is xs:boolean. 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. Table 2-1. Mapping between Feature Component Properties and XML Representation Property Mapping {name} The actual value of the uri attribute information item {required}If the value of the required attribute information item is "true" or "1", then "true", otherwise "false". 2.6 Property ? [ | ] 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: o A uri attribute information item as described below in 2.6.2.1 uri attribute information item with property [owner]. o 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: o An optional documentation element information item (see 5. Documentation). o 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] o 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. 2.6.2.1 uri attribute information item with property [owner] The uri attribute information item specifies the URI of the property. It has the following Infoset properties: * A [local name] of uri * A [namespace name] which has no value The type of the uri attribute information item is xs:anyURI. 2.6.2.2 value element information item with property [parent] xs:anySimpleType The value element information item specifies the value of the property. It has the following Infoset properties: * A [local name] of value * A [namespace name] of "http://www.w3.org/2003/06/wsdl" The type of the value element information item is xs:anySimpleType. 2.6.2.3 constraint element information item with property [parent] xs:QName The constraint element information item specifies a constraint on the value of the property. It has the following Infoset properties: * A [local name] of constraint * A [namespace name] of "http://www.w3.org/2003/06/wsdl" The type of the constraint attribute information item is xs:QName. 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. Table 2-1. Mapping between Property Component Properties and XML Representation Property Mapping {name} The actual value of the uri attribute information item If the constraint element information item is present, the type referred to by the value of this element information item. Otherwise, if the value element {value constraint}information item is present, an anonymous simple type, whose base type is "xs:anySimpleType", with a single "enumeration" facet whose value is that of the element information item. Otherwise, "xs:anySimpleType". 2.7 Interface Operation ? [ | | [ | | | ]+ ]* 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. Note: 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 it is considered good practice to ensure, where necessary, that operation names within a namespace are unique, thus allowing such derivation to occur without error. 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: o A name attribute information item as described below in 2.7.2.1 name attribute information item with operation [owner]. o A pattern attribute information item as described below in 2.7.2.2 pattern attribute information item with operation [owner]. o 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: o An optional documentation element information item (see 5. Documentation). o 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: o A feature element information item (see 2.5.2 XML Representation of Feature Component). o 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.2.1 name attribute information item with operation [owner] The name attribute information item identifies a given operation element information item inside a given interface element information item. The name attribute information item has the following Infoset properties: * A [local name] of name * A [namespace name] which has no value The type of the name attribute information item is xs:NCName. 2.7.2.2 pattern attribute information item with operation [owner] The pattern attribute information item identifies the message pattern a given operation uses. The pattern attribute information item has the following Infoset properties: * A [local name] of pattern * A [namespace name] which has no value The type of the pattern attribute information item is xs:anyURI. 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. Table 2-1. Mapping between Interface Operation Component Properties and XML Representation Property Mapping {name} The actual value of the name attribute information item The actual value of the targetNamespace attribute {target namespace} information item of the [parent] definitions element information item of the [parent] interface element information item. {message pattern} The actual value of the pattern attribute information item The set of message references corresponding to the {message references}input and output element information items in [children], if any. The set of fault references corresponding to the {fault references} infault and outfault element information items in [children] if any. {features} The set of features corresponding to the feature element information items in [children], if any. {properties} The set of properties corresponding to the property element information items in [children], if any. 2.8 Message Reference ? ? 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: o A name attribute information item as described below in 2.8.2.1 name attribute information item with input, or output [owner]. o A message attribute information item as described below in 2.8.2.2 message attribute information item with input, or output [owner]. o 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: o An optional documentation element information item (see 5. Documentation). o 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.2.1 name attribute information item with input , or output [owner] The name attribute information item identifies a given message reference element information item within a given operation element information item. The name attribute information item has the following Infoset properties: * A [local name] of name * A [namespace name] which has no value The type of the name attribute information item is xs:NCName. 2.8.2.2 message attribute information item with input , or output [owner] The message attribute information item refers, by QName, to a message component. The message attribute information item has the following Infoset properties: * A [local name] of message * A [namespace name] which has no value The type of the message attribute information item is xs:QName. 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. Table 2-1. Mapping between Message Reference Component Properties and XML Representation Property Mapping {name} The actual value of the name attribute information item If the [local name] of the element information item is input {direction}then "in", else if the [local name] of the element information item is output then "out". {message} The message component resolved to by the value of the message attribute information item 2.9 Fault Reference ? ? 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: o A name attribute information item as described below in 2.9.2.1 name attribute information item with infault or outfault [owner]. o A messages attribute information item as described below in 2.9.2.2 messages attribute information item with infault or outfault [owner]. o 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: o An optional documentation element information item (see 5. Documentation). o 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.2.1 name attribute information item with infault or outfault [owner] The name attribute information item identifies a given fault reference element information item within a given operation element information item. The name attribute information item has the following Infoset properties: * A [local name] of name * A [namespace name] which has no value The type of the name attribute information item is xs:NCName. 2.9.2.2 messages attribute information item with infault or outfault [owner] The messages attribute information item refers, by QNames, to a set of message components. The messages attribute information item has the following Infoset properties: * A [local name] of message * A [namespace name] which has no value The type of the message attribute information item is a list of xs:QName. 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. Table 2-1. Mapping between Fault Reference Component Properties and XML Representation Property Mapping {name} The actual value of the name attribute information item If the [local name] of the element information item is infault {direction}then "in", else if the [local name] of the element information item is outfault then "out". {messages} The message components resolved to by the value of the QNames listed in the message attribute information item 2.10 Binding ? [ | | ]* Editorial note: Should WSDL 1.2 (part June 25, 2002 3) including bindings for SOAP 1.1? The WS Description WG currently investigating whether it will support SOAP 1.1 in this specification, as a W3C note, or otherwise. We will of course support SOAP 1.2. 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: o A name attribute information item as described below in 2.10.2.1 name attribute information item with binding [owner]. o An interface attribute information item as described below in 2.10.2.2 interface attribute information item with binding [owner]. o 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: o An optional documentation element information item (see 5. Documentation). o 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.2.1 name attribute information item with binding [owner] The name attribute information item together with the targetNamespace attribute information item of the definitions element information item forms the QName of the binding. The name attribute information item has the following Infoset properties: * A [local name] of name * A [namespace name] which has no value The type of the name attribute information item is xs:NCName. 2.10.2.2 interface attribute information item with binding [owner] The interface attribute information item refers, by QName, to an interface component The interface attribute information item has the following Infoset properties: * A [local name] of interface * A [namespace name] which has no value The type of the interface attribute information item is xs:QName. 2.10.2.3 Binding extension elements Binding extension elements are used to provide information specific to a particular binding. The semantics of such element information items are defined by the specification for those element information items. Such specifications are expected to annotate the binding component with additional properties and specify the mapping between those properties and the XML representation. 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. Table 2-1. Mapping between Binding Component Properties and XML Representation Property Mapping {name} The actual value of the name attribute information item The actual value of the targetNamespace attribute {target namespace}information item of the [parent] definitions element information item {interface} The interface definition resolved to by the actual value of the interface attribute information item. The set of binding operation definitions corresponding {operations} to the operation element information items in [children], if any. {features} The set of feature definitions corresponding to the feature element information items in [children], if any. The set of property definitions corresponding to the {properties} property element information items in [children], if any. 2.11 Binding Operation ? [ | | [ | | | ]+ ]* 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: o A name attribute information item as described below in 2.11.2.1 name attribute information item with operation [owner]. o 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: o An optional documentation element information item (see 5. Documentation). o 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: o Zero or more feature element information items o 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.2.1 name attribute information item with operation [owner] The name attribute information item identified a given operation element information item within a given binding element information item. The name attribute information item has the following Infoset properties: * A [local name] of name * A [namespace name] which has no value The type of the name attribute information item is xs:NCName. 2.11.2.2 Binding operation extension elements Binding operation extension elements are used to provide information specific to a particular operation in a binding. The semantics of such element information items are defined by the specification for those element information items. Such specifications are expected to annotate the binding operation component with additional properties and specify the mapping between those properties and the XML representation. 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. Table 2-1. Mapping between Binding Operation Component Properties and XML Representation Property Mapping {name} The actual value of the name attribute information item The actual value of the targetNamespace attribute {target namespace}information item of the [parent] definitions element information item of the [parent] interface element information item. The set of binding message reference components {messages} corresponding to the input , output and fault element information items in [children], if any. {features} The set of feature components corresponding to the feature element information item in [children], if any. {properties} The set of property components corresponding to the property element information item in [children], if any. 2.12 Binding Message Reference ? ? ? ? 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: o An optional name attribute information item as described below in 2.12.2.1 name attribute information item with input, output or fault [owner]. o 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: o An optional documentation element information item (see 5. Documentation). o 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.2.1 name attribute information item with input , output or fault [owner] The name attribute information item identifies a given binding message reference element information item within a given operation element information item. The name attribute information item has the following Infoset properties: * A [local name] of name * A [namespace name] which has no value The type of the name attribute information item is xs:NCName. 2.12.2.2 Binding message reference extension elements Binding message reference extension elements are used to provide information specific to a particular message in an operation. The semantics of such element information items are defined by the specification for those element information items. Such specifications are expected to annotate the binding message reference component with additional properties and specify the mapping between those properties and the XML representation. 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. Table 2-1. Mapping between Binding Message Reference Component Properties and XML Representation Property Mapping The actual value of the name attribute information item if present, otherwise the actual value of the name attribute information item on the element information item with the same [local name] whose [parent] operation element information item {name} has the same value for its name attribute information item as the operation element information item in the binding element information item but is rather in the interface element information item referred to by the type attribute information item. If the [local name] of the element information item is input or {variety}infault then in, else if the [local name] of the element information item is output or outfault then out. 2.13 Service ? * 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: o A mandatory name attribute information item as described below in 2.13.2.1 name attribute information item with service [owner]. o An optional targetResource attribute information item as described below in 2.13.2.2 targetResource attribute information item with service [owner]. o A mandatory interface attribute information item as described below in 2.13.2.3 interface attribute information item with service [owner]. o 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: o An optional documentation element information item (see 5. Documentation). o 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]. Such element information items MUST be a member of one of the element substitution groups related to services described in 6. Language Extensibility. 2.13.2.1 name attribute information item with service [owner] The name attribute information item together with the targetNamespace attribute information item of the definitions element information item forms the QName of the service. The name attribute information item has the following Infoset properties: * A [local name] of name * A [namespace name] which has no value The type of the name attribute information item is xs:NCName. 2.13.2.2 targetResource attribute information item with service [owner] The targetResource attribute information item identifies the resource that the service is a representation of. The targetResource attribute information item has the following Infoset properties: * A [local name] of targetResource * A [namespace name] which has no value The type of the targetResource attribute information item is xs:anyURI. 2.13.2.3 interface attribute information item with service [owner] The interface attribute information item identifies the interface that the service is an instantiation of. The interface attribute information item has the following Infoset properties: * A [local name] of interface * A [namespace name] which has no value The type of the interface attribute information item is xs:NCName. 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 2-1. Table 2-1. Mapping between Service Component Properties and XML Representation Property Mapping {name} The actual value of the name attribute information item The actual value of the targetNamespace attribute {target namespace}information item of the [parent] definitions element information item {target resource} The actual value of the targetResource attribute information item, if present, otherwise the empty URI. The interface component resolved to by the actual value of the interface attribute information item on the {interface} bindings resolved to by the binding attribute information item on the endpoint element information items in [children], if any. {endpoints} The endpoint components corresponding to the endpoint element information items in [children] if any. 2.14 Endpoint ? 2.14.1 The Endpoint Component An endpoint component defines the particulars of a specific end-point 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 {name} property must be unique. 2.14.2 XML Representation of Endpoint Component The XML representation for a endpoint definition component is an element information item with the following Infoset properties: * A [local name] of endpoint * A [namespace name] of "http://www.w3.org/2003/06/wsdl" * Two or more attribute information items amongst its [attributes] as follows: o A name attribute information item as described below in 2.14.2.1 name attribute information item with endpoint [owner]. o A binding attribute information item as described below in 2.14.2.2 binding attribute information item with endpoint [owner]. o 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 item amongst its [children], as follows: o An optional documentation element information item (see 5. Documentation). o 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 endpoints described in 6. Language Extensibility. Such element information items are considered to be endpoint extension elements (see 2.14.2.3 Endpoint extension elements). 2.14.2.1 name attribute information item with endpoint [owner] The name attribute information item together with the targetNamespace attribute information item of the definitions element information item forms the QName of the endpoint. The name attribute information item has the following Infoset properties: * A [local name] of name * A [namespace name] which has no value The type of the name attribute information item is xs:NCName. 2.14.2.2 binding attribute information item with endpoint [owner] The binding attribute information item refers, by QName, to a binding component The binding attribute information item has the following Infoset properties: * A [local name] of binding * A [namespace name] which has no value The type of the binding attribute information item is xs:QName. 2.14.2.3 Endpoint extension elements Endpoint extension elements are used to provide information specific to a particular endpoint in a server. The semantics of such element information items are defined by the specification for those element information items. Such specifications are expected to annotate the endpoint component with additional properties and specify the mapping between those properties and the XML representation. 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 2-1. Table 2-1. Mapping between Endpoint Component Properties and XML Representation Property Mapping {name} The actual value of the name attribute information item {binding}The binding component resolved to by the actual value of the binding attribute information item 2.15 Equivalence of components Two components of the same type are considered equivalent if the values of the properties of one component are the same as the values of the properties in the second component. With respect to top-level components (messages, interfaces, bindings and services) this effectively translates to name-based equivalence given the constraints on names. That is, given two top-level components of the same type, if the {name} properties have the same value and the {target namespace} properties have the same values then the two components are in fact, the same component. 2.16 Symbol Spaces This specification defines 4 symbol spaces, one for each top-level component type (message, interface, binding and service). Within a symbol space all names, that is the combination of {name} and {target namespace} properties, are unique. Between symbol spaces, the combination of these two properties need not be unique. Thus it is perfectly coherent to have, for example, a binding and an interface that have the same name. When XML Schema is being used as one of the type systems for a WSDL description, then 6 other symbol spaces also exist, one for each of global element declarations, global attribute declarations, named model groups, named attribute groups, type definitions and key constraints, as defined by [XML Schema: Structures]. Other type systems may define additional symbol spaces. 2.17 QName resolution In its serialized form WSDL makes significant use of references between components. Such references are made using the Qualified Name, or QName of the component being referred to. QNames are a tuple, consisting of two parts; a namespace name and a local name. For example, in the case of an interface component, the namespace name is represented by the {namespace name} property and the local name is represented by the {name} property. QName references are resolved by looking in the appropriate property of the definitions component. For example, to resolve a QName of an interface (as referred to by the interface attribute information item on a binding), the {interfaces} property of the definitions component would be inspected. If the appropriate property of the definitions component does not contains a component with the required QName then the reference is a broken reference, it cannot be resolved. 3. Types ? [extension elements]* At the abstract level, the {type definitions} and {element declarations} properties of 2.1.1 The Definitions Component are collections of imported and embedded schema components. By design, WSDL supports any schema language for which the syntax and semantics of import or embed have been defined. Support for the W3C XML Schema Description Language [XML Schema: Structures],[XML Schema: Datatypes] is required of all processors. Instances of WSDL may require support for an alternative schema language by using the standard wsdl:required attribute information item (any imported or embedded XML Schema element information items may be regarded as having this attribute information item set). Only the XML Schema implementation is defined in this specification. The schema components contained in the {type definitions} and {element declarations} properties of 2.1.1 The Definitions Component provide the type system used for message parts. Message parts indicate their structure and content by using the standard attribute information items type and element, or for alternate schema languages in which these concepts do not map well, by defining alternative attribute information item extensions to the part element information item. Such extensions should define how they reference type system components. Such type system components MAY appear in additional collection properties on 2.1.1 The Definitions Component. The types element information item encloses data type definitions used to define messages and has the following Infoset properties: * A [local name] of types . * A [namespace name] of "http://www.w3.org/2003/06/wsdl". * Zero or more namespace qualified attribute information items in its [attributes] property. The [namespace name] property of such attribute information items MUST NOT be http://www.w3.org/2003/06/wsdl * Zero or more element information items amongst its [children] as follows: o An optional documentation element information item (see 5. Documentation) in its [children] property. o Zero or more element information items from among the following, in any order: + xs:import element information items + xs:schema element information items + Other namespace qualified element information items whose namespace is NOT http://www.w3.org/2003/06/wsdl 3.1 Using W3C XML Schema Description Language XML Schema MAY be used as the schema language, via import or embedding. Each method defines a different element information item. All processors MUST support XML Schema type definitions. Using the xs:import and/or xs:schema constructs is a necessary condition for making XML Schema components available to a WSDL description. That is, a WSDL description cannot refer to XML Schema components in a given namespace unless an xs:import and/or xs:schema statement for that namespace is present. 3.1.1 Importing XML Schema Importing an XML Schema uses the xs:import mechanism defined by XML Schema [XML Schema: Structures],[XML Schema: Datatypes], with its syntax and semantics, plus some 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 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: o A namespace attribute information item as described below. o An optional schemaLocation attribute information item as described below. 3.1.1.1 namespace attribute information item The namespace attribute information item defines the namespace of the type and element definitions imported from the referenced schema. If the referenced schema contains a targetNamespace attribute information item on its xs:schema element information item, then these values of these two attribute information items MUST be identical. If the schema does not have a targetNamespace attribute information item, then the namespace specified by the namespace attribute information item is applied to all components of the schema as if it contained a corresponding targetNamespace declaration. The namespace attribute information item has the following Infoset properties: * A [local name] of namespace * A [namespace name] which has no value. The type of the namespace attribute information item is xs:anyURI. 3.1.1.2 schemaLocation attribute information item The schemaLocation attribute information item, if present, provides a hint to the processor as to where the schema may be located. Caching and cataloging technologies may provide better information than this hint. The schemaLocation attribute information item has the following infoset properties: * A [local name] of schemaLocation. * A [namespace name] that has no value. The type of the schemaLocation attribute information item is xs:anyURI. 3.1.2 Embedding XML Schema Embedding an XML schema uses the existing top-level xs:schema element information item. 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 via xs:include are available to WSDL. Specifically components that the schema imports via xs:import are NOT available to WSDL. 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 targetNamespace attribute information item, amongst its [attributes] as described below. * Additional attribute information items as specified for the xs:schema element information item in the XML Schema specification. * Child element information items as specified for the xs:schema element information item in the XML Schema specification. 3.1.2.1 targetNamespace attribute information item The targetNamespace attribute information item defines the namespace of the type and element definitions embedded in this schema. WSDL modifies the XML Schema definition of the xs:schema element information item to make this attribute information item required. The targetNamespace attribute information item has the following infoset properties: * A [local name] of targetNamespace. * A [namespace name] that has no value. The type of the targetNamespace attribute information item is xs:anyURI. 3.1.3 References to Type and Element Definitions Whether embedded or imported, the type and element definitions present in a schema may be referenced from a message part. A named, global xs:simpleType or xs:complexType definition may be referenced from the part element information item using the type attribute information item. The QName is constructed from the targetNamespace of the schema and the content of the name attribute information item of the simpleType or complexType element information item. A type attribute information item may not be used to refer to an xs:element element information item. A named, global xs:element definition may be referenced from the part element information item using the element attribute information item. The QName is constructed from the targetNamespace of the schema and the content of the name attribute information item of the xs:element element information item. An element attribute information item may not be used to refer to an xs:simpleType or xs:complexType element information item. 3.2 Using Other Schema Languages Since it is unreasonable to expect that a single schema language can be used to describe all possible message parts and their constraints, WSDL allows alternate schema languages to be specified via extensibility elements. An extensibility element information item MAY appear under the types element information item to identify the schema language employed, and to locate the schema instance defining the grammar for message parts. Depending upon the schema language used, an element information item MAY be defined to allow embedding, if and only if the schema language can be expressed in XML. A specification of extension syntax for an alternative schema language MUST include an element information item definition, intended to appear as a child of the wsdl:types element information item, which references, names, and locates the schema instance (an "import" element information item). The extension specification SHOULD, if necessary, define additional properties of 2.1.1 The Definitions Component to hold the components of the referenced type system. It is expected that additional extensibility attributes for wsdl:part will also be defined, along with a mechanism for resolving the values of those attributes to a particular imported type system component. See E. Examples of Specifications of Extension Elements for Alternative Schema Language Support. for examples of using other schema languages. These example reuse the {element declarations} and {type definitions} properties of 2.1.1 The Definitions Component and the type and element attribute information items of wsdl:part . 4. Modularizing WSDL descriptions This specification provides two mechanisms, described in this section, for modularizing WSDL descriptions. These mechanisms help to make WSDL descriptions clearer by allowing separation of the various components of a description. Such separation could be performed according to the level of abstraction of a given set of components, or according to the namespace affiliation required of a given set of components or according to some other grouping such as application applicability. Both mechanisms work at the level of WSDL components and NOT at the level of XML Information Sets or XML 1.0 serializations. 4.1 Including Descriptions ? The WSDL include element information item allows for the separation of different components of a service definition, from the same target namespace, into independent WSDL documents which can be merged as needed. The WSDL include element information item is modeled after the XML Schema include element information item (see [XML Schema: Structures], section 4.2.3 "References to schema components in the same namespace"). Specifically it can be used to include components from WSDL descriptions that share a target namespace with the including description. Components in included descriptions are part of the component model of the including description. The included components can be referenced by QName. Note that because all WSDL descriptions have a target namespace, no-namespace includes (sometimes known as chameleon includes) never occur in WSDL. The include element information item has: * A [local name] of include . * A [namespace name] of "http://www.w3.org/2003/06/wsdl". * One or more attribute information items amongst its [attributes] as follows: o A location attribute information item as described below in 4.1.1 location attribute information item with include [owner]. o 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 one element information item amongst its [children], as follows: o An optional documentation element information item (see 5. Documentation). 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 for the namespace identified by the targetNamespace attribute information item of the containing definitions element information item. 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 Importing Descriptions ? The WSDL import element information item, like the include element information item (see 4.1 Including Descriptions) also allows for the separation of the different components of a WSDL description into independent descriptions, but in this case with different target namespaces, which can be imported as needed. This technique helps writing clearer WSDL descriptions, by separation the definitions according to their level of abstraction, and maximizes reusability. The WSDL import element information item is modeled after the XML Schema import element information item (see [XML Schema: Structures], section 4.2.3 "References to schema components across namespaces"). Specifically it can be used to import components from WSDL descriptions that do not share a target namespace with the importing document. Components in imported descriptions are part of the component model of the importing description. The imported components can be referenced by QName. Using the import construct is a necessary condition for making components from another namespace available to a WSDL description. That is, a WSDL description cannot refer to components in a namespace other that the target namespace unless an import statement for that namespace is present. The import element information item has the following Infoset properties: * A [local name] of import . * A [namespace name] of "http://www.w3.org/2003/06/wsdl". * Two or more attribute information items amongst its [attributes] as follows: o A namespace attribute information item as described below in 4.2.1 namespace attribute information item. o An optional location attribute information item as described below in 4.2.2 location attribute information item with import [owner]. o 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 one element information item amongst its [children], as follows: o An optional documentation element information item (see 5. Documentation). 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 can 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 for the namespace identified by the namespace attribute information item. The location attribute information item is optional to allow WSDL components to be constructed from information other than serialized XML 1.0 and to allow for WSDL processors that have a priori knowledge of certain namespaces. 5. Documentation [extension elements]* WSDL uses the optional documentation element information item as a container for human readable documentation. The content of the element information item is arbitrary character information items and element information items ("mixed" in XML Schema[XML Schema: Structures]). The documentation element information item is allowed inside any WSDL element information item. The documentation element information item has: * A [local name] of documentation . * A [namespace name] of "http://www.w3.org/2003/06/wsdl". * Zero or more attribute information items in its [attributes] property. * Zero or more child element information items in its [children] property. * Zero or more character information items in its [children] property. 6. Language Extensibility The schema for WSDL has two extensibility models, one based on element substitution groups and another based on qualified attributes. 6.1 Element based extensibility WSDL allows extensions to be defined in terms of element information items. Several abstract global element declarations serve as the heads of substitution groups. Some are specific to a particular point in the schema while others appear in multiple places. This allows extension to be specific to a particular point of the WSDL schema or more general. Table 6-1 shows the complete list of element substitution groups that along with their allowed locations. It is expected that extensions will want to add to the existing properties of components in the component model. The specification for an extension element information item should include definitions of any such properties and the mapping between the XML representation of the extension and the properties in the component model. The WSDL schema also defines a base type for use by extensibility elements. Example 6-1 shows the type definition. The use of this type as a base type is optional. The element declarations which serve as the heads of the defined substitution groups are all of type "xs:anyType". Extensibility elements are commonly used to specify some technology specific binding. They allow innovation in the area of network and message protocols without having to revise the base WSDL specification. WSDL recommends that specifications defining such protocols also define any necessary WSDL extensions used to describe those protocols or formats. An extension element is said to be processed if a WSDL processor decides (through whatever means) that its parent (an element information item in the "http://www.w3.org/2003/06/wsdl" namespace) will be processed. Note that it is possible for WSDL processors to process only a subset of a given WSDL document. For instance, a tool may wish to focus on interfaces and operations only, and will consequently skip bindings. Table 6-1. Element substitution groups defined for element based extensibility Element name Allowed in [children] Notes property of * wsdl:definitions after wsdl:import , wsdl:include and wsdl:types element information items if present. * wsdl:message This element information item serves as the head of a * wsdl:part substitution group for extensibility elements that wish globalExt * wsdl:interface to appear as a child of any element information item in the * wsdl:operation "http://www.w3.org/2003/06/wsdl" namespace with the exception of * wsdl:input wsdl:import , wsdl:include and wsdl:types . * wsdl:output * wsdl:fault * wsdl:binding * wsdl:service * wsdl:endpoint This element information item serves as the head of a * wsdl:message substitution group for msgAndinterfaceExt extensibility elements that wish * wsdl:interface to appear as a child of wsdl:message and/or wsdl:interface This element information item * wsdl:message serves as the head of a substitution group for msginterfaceAndBindingExt * wsdl:interface extensibility elements that wish to appear as a child of * wsdl:binding wsdl:message , wsdl:interface and/or wsdl:binding * wsdl:message This element information item serves as the head of a * wsdl:interface substitution group for msginterfaceBindingServiceExt extensibility elements that wish * wsdl:binding to appear as a child of wsdl:message , wsdl:interface , * wsdl:service wsdl:binding and/or wsdl:service This element information item * wsdl:binding serves as the head of a bindingAndServiceExt substitution group for * wsdl:service extensibility elements that wish to appear as a child of wsdl:binding and/or wsdl:service This element information item * wsdl:definitions serves as the head of a before substitution group for preImportInclude wsdl:import and extensibility elements that wish wsdl:include , to appear before the wsdl:import if present. and wsdl:include element information items * wsdl:definitions This element information item before, between serves as the head of a substitution group for inImportInclude or after extensibility elements that wish wsdl:import and wsdl:include , to appear interleaved with the if present. wsdl:import and wsdl:include element information items This element information item * wsdl:definitions serves as the head of a after substitution group for wsdl:import and extensibility elements that wish preTypes wsdl:include and to appear after the wsdl:import before and wsdl:include element wsdl:types , if information items but before the present. wsdl:types element information item This element information item serves as the head of a substitution group for * wsdl:definitions extensibility elements that wish postTypes after wsdl:types to appear after the wsdl:types , if present. element information item (potentially interleaved with wsdl:message , wsdl:interface , wsdl:/binding and wsdl:service element information items). Abstract elements related to message This element information item serves as the head of a msgExt * wsdl:message substitution group for extensibility elements that wish to appear as children of wsdl:message * wsdl:message This element information item before wsdl:part serves as the head of a msgPrePartExt element substitution group for information extensibility elements that wish items, if to appear as children of present. wsdl:message before wsdl:part * wsdl:message This element information item after wsdl:part serves as the head of a msgPostPartExt element substitution group for information extensibility elements that wish items, if to appear as children of present. wsdl:message after wsdl:part This element information item serves as the head of a msgPartExt * wsdl:part substitution group for extensibility elements that wish to appear as children of wsdl:message/wsdl:part Abstract elements related to interface This element information item serves as the head of a interfaceExt * wsdl:interface substitution group for extensibility elements that wish to appear as children of wsdl:interface * wsdl:interface This element information item before serves as the head of a wsdl:operation substitution group for interfacePreOpExt element extensibility elements that wish information to appear as children of items, if wsdl:interface before present. wsdl:operation * wsdl:interface This element information item after serves as the head of a wsdl:operation substitution group for interfacePostOpExt element extensibility elements that wish information to appear as children of items, if wsdl:interface after present. wsdl:operation This element information item * wsdl:operation serves as the head of a substitution group for interfaceOpExt with extensibility elements that wish wsdl:interface [parent] to appear as children of wsdl:operation when it is a child of wsdl:interface * wsdl:input with wsdl:operation [parent] which This element information item itself has serves as the head of a wsdl:interface substitution group for [parent] extensibility elements that wish interfaceOpMsgExt to appear as children of * wsdl:output with wsdl:input or wsdl:output when wsdl:operation they appear as children of [parent] which wsdl:operation which itself itself has appears as a child of wsdl:interface wsdl:interface [parent] This element information item * wsdl:fault with serves as the head of a wsdl:operation substitution group for extensibility elements that wish interfaceOpFaultExt [parent] which to appear as children of itself has wsdl:interface wsdl:fault when it appears as a [parent] child of wsdl:operation which itself appears as a child of wsdl:interface Abstract elements related to features and properties This element information item serves as the head of a featureExt * wsdl:feature substitution group for extensibility elements that wish to appear as children of wsdl:feature This element information item serves as the head of a propertyExt * wsdl:property substitution group for extensibility elements that wish to appear as children of wsdl:property Abstract elements related to bindings This element information item serves as the head of a bindingExt * wsdl:binding substitution group for extensibility elements that wish to appear as children of wsdl:binding * wsdl:binding This element information item before serves as the head of a wsdl:operation substitution group for bindingPreOpExt element extensibility elements that wish information to appear as children of items, if wsdl:binding before present. wsdl:operation * wsdl:binding after This element information item wsdl:operation serves as the head of a bindingPostOpExt element substitution group for information extensibility elements that wish items, if to appear as children of present. wsdl:binding after wsdl:operation This element information item * wsdl:operation serves as the head of a substitution group for bindingOpExt with extensibility elements that wish wsdl:binding [parent] to appear as children of wsdl:operation appearing as children of wsdl:binding * wsdl:input with wsdl:operation [parent] which This element information item itself has serves as the head of a wsdl:binding substitution group for [parent] extensibility elements that wish bindingOpMsgExt to appear as children of * wsdl:output with wsdl:input or wsdl:output when wsdl:operation they appear as children of [parent] which wsdl:operation which itself itself has appears as a child of wsdl:binding wsdl:binding [parent] This element information item * wsdl:fault with serves as the head of a wsdl:operation substitution group for extensibility elements that wish bindingOpFaultExt [parent] which to appear as children of itself has wsdl:binding wsdl:fault when it appears as a [parent] child of wsdl:operation which itself appears as a child of wsdl:binding Abstract elements related to service This element information item serves as the head of a serviceExt * wsdl:service substitution group for extensibility elements that wish to appear as children of wsdl:service * wsdl:service before This element information item wsdl:endpoint serves as the head of a servicePreEndpointExt element substitution group for information extensibility elements that wish items, if to appear as children of present. wsdl:service before wsdl:endpoint * wsdl:service after This element information item wsdl:endpoint serves as the head of a servicePostEndpointExt e