This document is also available in these non-normative formats: <a href= "http://www.w3.org/TR/2003/WD-wsdl20-20031110/wsdl20.ps"> postscript , <a href= "http://www.w3.org/TR/2003/WD-wsdl20-20031110/wsdl20.pdf"> PDF , <a href= "http://www.w3.org/TR/2003/WD-wsdl20-20031110/wsdl20.xml"> XML , and <a href= "http://www.w3.org/TR/2003/WD-wsdl20-20031110/wsdl20.txt"> plain text .
Copyright © 2003 © 2004 W3C ® ( <a href="http://www.lcs.mit.edu/"> MIT , ERCIM , Keio ), All Rights Reserved. W3C liability , trademark , document use and software licensing rules apply.
This document describes the Web Services Description Language (WSDL) Version 2.0, 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. It also defines criteria for a conformant processor of this language.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
This is a <a href= "http://www.w3.org/2003/06/Process-20030618/tr.html#RecsWD"> W3C Working Draft of the Web Services Description Language (WSDL) 2.0 document.
A diff-marked version against the previous version of this document is available. For a detailed list of changes since the last publication of this document, please refer to appendix F. Part 1 Change Log .A list of open issues against this document is also available.
This document has been produced as part of the W3C Web Services Activity . The authors of this document are the Web Services Description Working Group members.
Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
Comments on this document are invited and have are to be sent to the public www-ws-desc@w3.org mailing list ( public archive ).
This document has been produced under the 24 January 2002 Current Patent Practice as amended by the W3C Patent Policy Transition Procedure . Patent disclosures relevant to this specification may be found on the Working Group's patent disclosure page . An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) with respect to this specification should disclose the information in accordance with section 6 of the W3C Patent Policy .
1. Introduction
2. Component Model
3. Types
4. Modularizing WSDL descriptions
5. Documentation
6. Language
Extensibility
7. Locating WSDL
Documents
8. Conformance
9. XML Syntax Summary
(Non-Normative)
10. 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 2.0 (Non-Normative)
D. E.
Examples of Specifications of Extension
Elements for Alternative Schema Language Support.
(Non-Normative)
E. F.
Part 1 Change Log (Non-Normative)
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 Interface
2.2.1 The Interface Component
2.2.2 XML Representation of Interface
Component
2.2.2.1
name attribute information item
with interface [owner]
2.2.2.2
extends attribute
information item
2.2.2.3
styleDefault attribute
information item
2.2.3 Mapping Interface's XML Representation to
Component Properties
2.3 <a
href="#InterfaceOperation"> Interface Operation
Fault
2.3.1 <a href= "#InterfaceOperation_details">
The Interface Operation Fault
Component
2.3.1.1
<a href="#InterfaceOperationStyle"> Operation Style
2.3.2
XML
Representation of Interface Fault Component
2.3.1.1.1
<a href="#RPCStyle"> RPC Style 2.3.2.1
name attribute information item with fault
[owner]
2.3.1.1.2
<a href="#AttrSetStyle"> Set-Attribute Style
2.3.2.2
element attribute information item with fault
[owner]
2.3.1.1.3
<a href="#AttrGetStyle"> Get-Attribute 2.3.3
Mapping
Interface Fault's XML Representation to Component
Properties
2.4 Interface
Operation
2.4.1
The
Interface Operation Component
2.4.1.1
Operation Style
2.3.2
2.4.2
XML Representation of
Interface Operation Component
2.3.2.1
2.4.2.1
name attribute
information item with operation [owner]
2.3.2.2
2.4.2.2
pattern attribute
information item with operation [owner]
2.3.2.3
2.4.2.3
style attribute
information item with operation [owner]
2.3.3
2.4.2.4
safe attribute information item with operation
[owner]
2.4.3
Mapping Interface Operation's
XML Representation to Component Properties
2.4
2.4.4
RPC
Style
2.4.4.1
wrpc:signature Extension
2.4.4.2
XML Representation of the wrpc:signature
Extension
2.4.4.3
wrpc:signature Extension Mapping To Properties of an
Interface Operation Component
2.5 Message Reference
2.4.1
2.5.1
The Message Reference
Component
2.4.2
2.5.2
XML Representation of Message
Reference Component
2.4.2.1
<a href= "#MessageReference_messageReference_attribute">
messageReference 2.5.2.1
messageLabel attribute information item with
input, or output [owner]
2.4.2.2
<a href="#MessageReference_message_attribute"> message
2.5.2.2
element attribute information item with input, or
output [owner]
2.4.3
2.5.3
Mapping Message Reference's XML
Representation to Component Properties
2.5
2.6 Fault Reference
2.5.1
2.6.1
The Fault Reference
Component
2.5.2
2.6.2
XML Representation of Fault
Reference Component
2.5.2.1
<a href="#FaultReference_name_attribute"> name attribute
information item with infault, or outfault [owner] </a>
<br />
2.5.2.2
<a href= "#FaultReference_messageReference_attribute">
messageReference 2.6.2.1
ref attribute information item with infault, or
outfault [owner]
2.5.2.3
<a href="#FaultReference_message_attribute"> message
2.6.2.2
messageLabel attribute information item with
infault, or outfault [owner]
2.5.3
2.6.3
Mapping Fault Reference's XML
Representation to Component Properties
2.6
2.7 Feature
2.6.1
2.7.1
The Feature Component
2.6.2
2.7.1.1
Feature
Composition Model
2.7.1.1.1
Example of Feature Composition Model
2.7.2
XML Representation of Feature
Component
2.6.2.1
2.7.2.1
uri attribute information item
with feature [owner]
2.6.2.2
2.7.2.2
required attribute
information item with feature [owner]
2.6.3
2.7.3
Mapping Feature's XML Representation to
Component Properties
2.7
2.8 Property
2.7.1
2.8.1
The Property Component
2.7.2
2.8.1.1
Property Composition Model
2.8.2
XML Representation of Property
Component
2.7.2.1
2.8.2.1
uri attribute information item
with property [owner]
2.7.2.2
2.8.2.2
required attribute
information item with feature [owner]
2.7.2.3
2.8.2.3
value element information item
with property [parent]
2.7.2.4
2.8.2.4
constraint element
information item with property [parent]
2.7.3
2.8.3
Mapping Property's XML Representation
to Component Properties
2.8
2.9 Binding
2.8.1
2.9.1
The Binding Component
2.8.2
2.9.2
XML Representation of Binding
Component
2.8.2.1
2.9.2.1
name attribute information item
with binding [owner]
2.8.2.2
2.9.2.2
interface attribute
information item with binding [owner]
2.8.2.3
2.9.2.3
Binding extension
elements
2.8.3
2.9.3
Mapping Binding's XML Representation to
Component Properties
2.9 <a
href="#Binding_Operation"> 2.10 Binding Operation
Fault
2.9.1
<a href= "#Binding_Operation_details"> 2.10.1
The Binding Operation Fault
Component
2.9.2
<a href= "#Binding_Operation_XMLRep"> 2.10.2
XML Representation of Binding
Operation Fault Component
2.9.2.1
<a href="#Binding_Operation_name_attribute"> name
2.10.2.1
ref attribute information item with operation fault
[owner]
2.9.2.2
<a href="#Binding_Operation_extension_elements">
2.10.2.2
Binding Operation Fault
extension elements
2.9.3
<a href= "#Binding_Operation_Mapping"> 2.10.3
Mapping Binding Operation's Fault's
XML Representation to Component Properties
2.10 <a href=
"#Binding_Message_Reference"> 2.11 Binding Message
Reference Operation
2.10.1
<a href= "#Binding_Message_Reference_details">
2.11.1
The Binding Message Reference Operation Component
2.10.2
<a href= "#Binding_Message_Reference_XMLRep">
2.11.2
XML Representation of Binding
Message Reference Operation Component
2.10.2.1
<a href= "#Binding_Message_Reference_name_attribute">
messageReference 2.11.2.1
ref attribute information item with input or output operation [owner]
2.10.2.2
<a
href="#Binding_Message_Reference_extension_elements">
2.11.2.2
Binding
Message Reference Operation extension elements
2.10.3
<a href= "#Binding_Message_Reference_Mapping">
2.11.3
Mapping Binding Message Reference's Operation's XML Representation to Component
Properties
2.11 <a href=
"#Binding_Fault_Reference"> 2.12 Binding Fault Message
Reference
2.11.1
<a href= "#Binding_Fault_Reference_details">
2.12.1
The Binding
Fault Message Reference Component
2.11.2
<a href= "#Binding_Fault_Reference_XMLRep">
2.12.2
XML Representation of
Binding Fault Message Reference Component
2.11.2.1
<a href="#Binding_Fault_Reference_name_attribute"> name
attribute information item with infault or outfault [owner]
</a> <br />
2.11.2.2
<a href=
"#Binding_Fault_Reference_messageReference_attribute">
messageReference 2.12.2.1
messageLabel attribute information item with
infault input or outfault
output [owner]
2.11.2.3
<a href="#Binding_Fault_Reference_extension_elements">
2.12.2.2
Binding
Fault Message Reference extension elements
2.11.3
<a href= "#Binding_Fault_Reference_Mapping">
2.12.3
Mapping Binding
Fault Message Reference's XML Representation to
Component Properties
2.12
2.13 Service
2.12.1
2.13.1
The Service Component
2.12.2
2.13.2
XML Representation of Service
Component
2.12.2.1
2.13.2.1
name attribute information item
with service [owner]
2.12.2.2
2.13.2.2
interface attribute
information item with service [owner]
2.12.3
2.13.3
Mapping Service's XML Representation to
Component Properties
2.13
2.14 Endpoint
2.13.1
2.14.1
The Endpoint Component
2.13.2
2.14.2
XML Representation of Endpoint
Component
2.13.2.1
2.14.2.1
name attribute information item
with endpoint [owner]
2.13.2.2
2.14.2.2
binding attribute information
item with endpoint [owner]
2.13.2.3
2.14.2.3
Endpoint extension
elements
2.13.3
2.14.3
Mapping Endpoint's XML Representation
to Component Properties
2.14
2.15 Equivalence of Components
2.15
2.16 Symbol Spaces
2.16
2.17 QName resolution
2.18 Comparing
URIs
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 Element Declarations
deleted text: and Type 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 Extensibility
6.1.1 Mandatory extensions
6.1.2 required attribute information item
6.2 <a href=
"#aii-extensbility"> Attribute-based extensibility Extensibility
6.3 Extensibility
Semantics
7. Locating WSDL
Documents
7.1 wsdli:wsdlLocation
attribute information item
8. Conformance
8.1 Document
Conformance
8.2 XML Information Set
Conformance
8.3 Processor
Conformance
9. XML Syntax Summary
(Non-Normative)
10. References
7.1
10.1 Normative References
7.2
10.2 Informative References
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
D. Migrating
from WSDL 1.1 to WSDL 2.0 (Non-Normative)
C.1
D.1 Operation Overloading
C.2
D.2 PortTypes
C.3
D.3 Ports
D. E.
Examples of Specifications of Extension
Elements for Alternative Schema Language Support.
(Non-Normative)
D.1
E.1 DTD
D.1.1
E.1.1
namespace attribute information
item
D.1.2
E.1.2
location attribute information
item
D.1.3
E.1.3
References to Element Definitions
D.2
E.2 RELAX NG
D.2.1
E.2.1
Importing RELAX NG
D.2.1.1
E.2.1.1
ns attribute information
item
D.2.1.2
E.2.1.2
href attribute information
item
D.2.2
E.2.2
Embedding RELAX NG
D.2.2.1
E.2.2.1
ns attribute information
item
D.2.3
E.2.3
References to Element Declarations
E. F.
Part 1 Change Log (Non-Normative)
E.1
F.1 WSDL Specification Changes
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. It also defines criteria for a conformant processor of this language. The WSDL Version 2.0 Part 2: Message Exchange Patterns specification [ WSDL 2.0 Message Exchange Patterns ] defines deleted text: define the sequence and cardinality of abstract messages sent or received by an operation. The WSDL Version 2.0 Part 3: Bindings specification [ <a href="#WSDL-PART3"> WSDL 2.0 Bindings ] defines a language for describing such concrete details for SOAP 1.2 [ <a href="#SOAP12-PART1"> SOAP 1.2 Part 1: Messaging Framework ], HTTP [ IETF RFC 2616 ] and MIME [ IETF RFC 2045 ].
WSDL describes a Web service in two fundamental stages: one abstract and one concrete. Within each stage, the description uses a number of constructs to promote reusability of the description and separate independent design concerns.
At an abstract level, WSDL describes a Web service in terms of the messages it sends and receives; messages are described independent of a specific wire format using a type system, typically XML Schema.
An operation associates a message exchange pattern with one or more messages. A message exchange pattern identifies the sequence and cardinality of messages sent and/or received as well as who they are logically sent to and/or received from. An interface groups together operations without any commitment to transport or wire format.
At a concrete level, a binding specifies transport and wire format details for one or more interfaces. An endpoint associates a network address with a binding. And finally, a service groups together endpoints that implement a common interface.
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 ]).
Prefix | Namespace | Notes |
---|---|---|
wsdl | "http://www.w3.org/2003/11/wsdl" "http://www.w3.org/2004/03/wsdl" | A normative XML Schema [ XML Schema: Structures ], [ XML Schema: Datatypes ] document for the "http://www.w3.org/2003/11/wsdl" "http://www.w3.org/2004/03/wsdl" namespace can be found at <a href= "http://www.w3.org/2003/11/wsdl"> http://www.w3.org/2003/11/wsdl http://www.w3.org/2004/03/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. |
wsdli | "http://www.w3.org/2004/03/wsdl-instance" | A normative XML Schema [ XML Schema: Structures ], [ XML Schema: Datatypes ] document for the "http://www.w3.org/2004/03/wsdl-instance" namespace can be found at http://www.w3.org/2004/03/wsdl-instance . |
wrpc | "http://www.w3.org/2004/03/wsdl/rpc" | A normative XML Schema [ XML Schema: Structures ], [ XML Schema: Datatypes ] document for the "http://www.w3.org/2004/03/wsdl/rpc" namespace can be found at http://www.w3.org/2004/03/wsdl/rpc . 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. |
wsoap12 | "http://www.w3.org/2003/11/wsdl/soap12" | Defined by WSDL 2.0: Bindings [ WSDL 2.0 Bindings ]. |
whttp | "http://www.w3.org/2003/11/wsdl/http" | |
deleted text: wmime </td> <td rowspan="1" colspan="1"> "http://www.w3.org/2003/11/wsdl/mime" </td> </tr> <tr> <td rowspan="1" colspan="1"> xs | "http://www.w3.org/2001/XMLSchema" | Defined in the W3C XML Schema specification [ XML Schema: Structures ], [ XML Schema: Datatypes ]. |
xsi | "http://www.w3.org/2001/XMLSchema-instance" |
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 notes, pseudo-schemas, examples, and sections explicitly marked as "Non-Normative". Pseudo-schemas are provided for each component, before the description of this the component.
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.
At the abstract level, the Definitions component is just a container for two categories of component; components; WSDL components and type system components.
WSDL components are interfaces, bindings and services.
Type system components are element declarations deleted text: and type definitions drawn from some type system. The former They define the [local name], [namespace name], [children] and [attributes] properties of an element information item </em> ; the latter define only the [children] and [attributes] properties. .
The properties of the Definitions component are as follows:
{interfaces} A set of named interface definitions
{bindings} A set of named binding definitions
{services} A set of named service definitions
deleted text: {type definitions} A set of named type definitions, each one isomorphic to a simple or complex type as defined by XML Schema </p> </li> <li> <p> {element declarations} A set of named element declarations, each one isomorphic to a global element declaration as defined by XML Schema
The set of interfaces/binding/services/etc. available in the Definitions component include those that are defined within the component itself and those that are imported and/or included. At Note that at the component model level, there is no distinction between directly defined components vs. imported/included components.
The components directly defined within a single Definitions component are said to belong to the same target namespace . The target namespace therefore groups a set of related component definitions and provides a hint of represents an unambiguous name for the intended semantics of the components. The target namespace URI SHOULD point to a human or machine processable document that directly or indirectly defines the intended semantics of those components.
Note that it is RECOMMENDED that the
value of the targetNamespace
attribute information item SHOULD be a dereferencible URI and that it resolve to a
WSDL document which provides service description information for
that namespace.
If a service description is split into
multiple documents (which may be combined as needed via
4.1 Including
Descriptions ), then
the targetNamespace
attribute information item SHOULD resolve to a master document which includes all
the WSDL documents needed for that service description. This
approach enables the WSDL component designators' fragment
identifiers to be properly resolvable.
Imported components have different target namespace values from the Definitions component that is importing them. Thus importing is the mechanism to use components from one namespace in another set of definitions.
Each WSDL or type/element type system component MUST be uniquely identified by its qualified name. That is, if two distinct components of the same kind (Interface, Binding etc.) are in the same target namespace, then their QNames MUST be unique. However, different kids kinds of components (e.g., an Interface component and a Binding component) MAY have the same QName. Thus, QNames of components must be unique within the space of those components in a given target namespace.
In addition to WSDL components and type and element system components, additional extension components MAY be added via extensibility 6. Language Extensibility . Further, additional properties to WSDL and type/element type system components MAY also be added via extensibility.
<definitions targetNamespace="xs:anyURI" > <documentation />? [ <import /> | <include /> ]* <types />? [ <interface /> | <binding /> | <service /> ]* </definitions>
WSDL definitions are represented in XML by one or more WSDL
Information Sets (Infosets), that is one or more
definitions
element information item s. A
WSDL Infoset contains representations for a collection of WSDL
components which share a common target namespace. A WSDL Infoset
which contains one or more import
element
information item s 4.2 Importing
Descriptions corresponds to a collection with components
drawn from multiple target namespaces.
The deleted text: target namespace represents an unambiguous name for the intended semantics of the WSDL Infoset. The targetNamespace URI SHOULD point to a human or machine processable document that directly or indirectly defines the semantics of the WSDL Infoset. MUST be an absolute URI (see [ IETF RFC 2396 ]).
The definitions
element information item
has the following Infoset properties:
A [local name] of definitions
.
A [namespace name] of "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
One or more attribute information item s amongst its [attributes] as follows:
A REQUIRED targetNamespace
attribute
information item as described below in 2.1.2.1 targetNamespace
attribute information item .
Zero or more namespace qualified attribute information item s. The [namespace name] of such attribute information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
Zero or more element information item s amongst its [children], in order as follows:
An OPTIONAL documentation
element information
item (see 5.
Documentation ).
Zero or more element information item s from among the following, in any order:
Zero or more include
element information
item s (see 4.1 Including
Descriptions )
Zero or more import
element information
item s (see 4.2 Importing
Descriptions )
Zero or more namespace-qualified element information item s. The [namespace name] of such element information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
An OPTIONAL types
element information item
(see 3. Types ).
Zero or more element information item s from among the following, in any order:
interface
element information item s (see
2.2.2 XML Representation of
Interface Component ).
binding
element information item s (see
2.8.2
2.9.2 XML Representation of Binding
Component ).
service
element information item s (see
2.12.2
2.13.2 XML Representation of Service
Component ).
Zero or more namespace-qualified element information item s. The [namespace name] of such element information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
targetNamespace
attribute information
itemThe targetNamespace
attribute information
item defines the namespace affiliation of top-level components
defined in this definitions
element information
item . 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 .
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 .
Property | Mapping |
---|---|
{interfaces} | The interface definitions corresponding
to all the interface element information item
s in the [children] of the definitions element
information item , if any, plus any included or imported
interface definitions (see 4. Modularizing
WSDL descriptions ). |
{bindings} | The binding definitions corresponding
to all the binding element information item s
in the [children] of the definitions element
information item , if any, plus any included or imported
binding definitions (see 4. Modularizing
WSDL descriptions ). |
{services} | The service definitions corresponding
to all the service element information item s
in the [children] of the definitions element
information item , if any, plus any included or imported
service definitions (see 4. Modularizing
WSDL descriptions ). |
deleted text: {type definitions} </td> <td rowspan="1" colspan="1"> The type definition components corresponding to all the type definitions defined as descendants of the <code> types </code> <em> element information item </em>, if any, plus any imported type definitions. At a minimum this will include all the types defined by XML Schema <code> simpleType </code> and <code> complexType </code> <em> element information item </em> s. It MAY also include any definition from some other type system which describes the [attributes] and [children] properties of an <em> element information item </em>. </td> </tr> <tr> <td rowspan="1" colspan="1"> {element declarations} | The element declaration components
corresponding to all the element declarations defined as
descendants of the types element information
item , if any, plus any imported element definitions. At a
minimum this will include all the global element declarations
defined by XML Schema element element information
item s. 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 . |
An Interface component describes sets sequences of messages that a service sends and/or receives. It does this by grouping related messages into operations. An operation is a set sequence of input and output messages, an interface is a set of operations.
An interface can optionally extend one or more other interfaces. In such cases the interface contains the operations of the interfaces it extends, along with any operations it defines. The interfaces a given interface extends MUST NOT themselves extend that interface either directly or indirectly.
Interfaces are named constructs and can be referred to by QName (see 2.16 2.17 QName resolution ). For instance, Binding components refer to interfaces in this way.
The properties of the Interface component are as follows:
{name} An NCName as defined by [ XML Namespaces ].
{target namespace} A namespace name, as defined in [ XML Namespaces ].
{extended interfaces} A set of named interface definitions which this interface extends.
{style default} The default style of message schemas of the operations. If a per-operation value is not specified for this property, then this value becomes the default value {faults} A set of the property. See <a href= "#InterfaceOperation_style_attribute"> <b> 2.3.2.3 style attribute information item with operation [owner] </b> </a> named interface fault definitions.
{operations} A set of named interface operation definitions.
{features} A set of named feature definitions.
{properties} A set of named property definitions.
For each Interface component in the {interfaces} property of a definitions container container, the combination of {name} and {target namespace} properties must MUST be unique.
<definitions> <interface name="xs:NCName" extends="list of xs:QName"? styleDefault="xs:anyURI"? > <documentation />? [ <operation /> | <feature /> | <property /> ]* [ <fault /> | <operation /> | <feature /> | <property /> ]* </interface> </definitions>
The XML representation for an Interface component is an element information item with the following Infoset properties:
A [local name] of interface
A [namespace name] of "http://www.w3.org/2003/11/wsdl" "http://www.w3.org/2004/03/wsdl"
One or more attribute information item s amongst its [attributes] as follows:
A REQUIRED name
attribute information item
as described below in 2.2.2.1 name attribute information
item with interface [owner] .
An OPTIONAL extends
attribute information
item as described below in 2.2.2.2 extends attribute
information item .
An OPTIONAL styleDefault
attribute information
item as described below in 2.2.2.3 styleDefault
attribute information item .
Zero or more namespace qualified attribute information item s. The [namespace name] of such attribute information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
Zero or more element information item s amongst its [children], in order, as follows:
An OPTIONAL documentation
element information
item (see 5.
Documentation ).
Zero or more element information item s from among the following, in any order:
Zero or more fault
element information item
s 2.3.2 XML
Representation of Interface Fault Component .
Zero or more
operation
element information item s 2.3.2
2.4.2 XML Representation of Interface
Operation Component .
Zero or more feature
element information
item s 2.6.2 2.7.2 XML
Representation of Feature Component .
Zero or more property
element information
item s 2.7.2 2.8.2 XML
Representation of Property Component .
Zero or more namespace-qualified element information item s amongst its [children]. The [namespace name] of such element information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
name
attribute information item with interface
[owner]The name
attribute information item
together with the targetNamespace
attribute
information item of the [parent]
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 .
extends
attribute information itemThe 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 .
styleDefault
attribute information itemThe styleDefault
attribute information
item indicates the default style used to construct the
{message} {element} properties of {message references} of
all operations contained within the [owner] interface
.
The styleDefault
attribute information
item has the following Infoset properties:
A [local name] of styleDefault.
A [namespace name] which has no value.
The type of the styleDefault
attribute
information item is xs:anyURI . Moreover, the value of the styleDefault
attribute information item ,if present, MUST be an absolute URI (see [
IETF RFC
2396 ]).
The mapping between the properties of the Interface component
(see 2.2.1 The Interface
Component ) and the XML Representation of the
interface
element information item (see
2.2.2 XML Representation of
Interface Component ) is as described in Table 2-2 .
Property | Mapping |
---|---|
{name} | The actual value of the
name attribute information item |
{target namespace} | The actual value of the
targetNamespace attribute information item of
the [parent] definitions element information
item |
{style default} {extended interfaces} | The actual
value set of interface definitions resolved to by the values
in the styleDefault
extends attribute
information item if any, plus the set
of interface definitions in the {extended interfaces} property of
those interface definitions, otherwise empty. |
{extended interfaces} {faults} | The set of interface fault definitions resolved corresponding to deleted
text: by the values in the
extends fault attribute element
information item s in
[children], if any, plus the set of interface fault definitions in the {extended interfaces} {faults} property of those the interface
definitions, otherwise empty.
definitions in {extended interfaces}, if
any. |
{operations} | The set of interface operation
definitions corresponding to the operation element
information item s in [children], if any, plus the set of
interface operation definitions in the {operations} property of the
interface definitions in {extended interfaces}, if any. |
{features} | The set of feature definitions
corresponding to the feature element information
item s in [children], if any, plus the set of feature
definitions in the {features} property of the feature definitions
in {extended interfaces}, if any. |
{properties} | The set of property definitions
corresponding to the property element information
item s in [children], if any, plus the set of property
definitions in the {properties} property of the property
definitions in {extended interfaces}, if any. |
Per Note that, per 2.2.1 The Interface Component , the Interface components in the {extended interfaces} property of a given Interface component MUST NOT contain that Interface component in any of their {extended interfaces} properties, that is to say, recursive extension of interfaces is disallowed.
An Interface Fault component describes a fault that MAY be occur during execution of an operation of the interface. The Interface Fault component declares a fault by naming it and indicating the content or payload of the fault message. When and how the fault message flows is indicated by the Interface Operation component 2.4 Interface Operation .
The reason the Interface Fault component is a property of the Interface component is because that provides a convenient mechanism to declare a set of fault message types and then indicate which operations use those types, thus allowing one to easily indicate that the same fault message type can occur in multiple operations.
The properties of the Interface Fault component are as follows:
{name} An NCName as defined by [ XML Namespaces ].
{element} A reference to an XML element declaration in the {element declarations} property of 2.1.1 The Definitions Component .This element represents the content or "payload" of the fault.
If a non-XML type system is in use (as considered in 3.2 Using Other Schema Languages ) then additional properties would need to be added to the Fault Component (along with extensibility attributes to its XML representation) to allow associating such message types with the message reference.
For each Interface Fault component in the {faults} property of an Interface component, the combination of {name} and {target namespace} properties must be unique.
Interface Fault components are local to Interface components; they cannot be referred to by QName, despite having both {name} and {target namespace} properties. That is, two Interface components sharing the same {target namespace} property but with different {name} properties MAY contain Interface Fault components which share the same {name} property. Thus, the {name} and {target namespace} properties of the Interface Fault components are not sufficient to form the unique identity of an Interface Fault component. To uniquely identify an Interface Fault component one must first identify the Interface component (by QName) and then identify the Interface Fault within that Interface component (by a further QName).
In cases where, due to an interface extending one or more other interfaces, two or more Interface Faults components have the same value for their {name} and {target namespace} properties, then the component models of those Interface Fault components MUST be equivalent (see 2.15 Equivalence of Components ). If the Interface Fault components are equivalent then they are considered to collapse into a single component. It is an error if two Interface Fault components have the same value for their {name} and {target namespace} properties but are not equivalent.
Note that, due to the above rules, if two interfaces that have the same value for their {target namespace} property also have one or more faults that have the same value for their {name} property then those two interfaces cannot both form part of the derivation chain of a derived interface unless those faults are the same fault.
Note:
For the above reason, it is considered good practice to ensure, where necessary, that the {name} property of Interface Fault components within a namespace are unique, thus allowing such derivation to occur without inadvertent error.
<definitions>
<interface>
<fault
name="xs:NCName"
element="xs:QName"? >
<documentation />?
</fault>
</interface>
</definitions>
The XML representation for an Interface Fault component is an element information item with the following Infoset properties:
A [local name] of
fault
A [namespace name] of "http://www.w3.org/2004/03/wsdl"
Two or more attribute information item s amongst its [attributes] as follows:
A REQUIRED name
attribute
information item as described
below in 2.3.2.1
name attribute information item with fault [owner]
.
An OPTIONAL element
attribute information item as described below in 2.3.2.2
element attribute information item with fault
[owner] .
Zero or more namespace qualified attribute information item s. The [namespace name] of such attribute information item s MUST NOT be "http://www.w3.org/2004/03/wsdl".
Zero or more element information item amongst its [children], in order, as follows:
An OPTIONAL documentation
element information item (see 5. Documentation ).
Zero or more namespace-qualified element information item s amongst its [children]. The [namespace name] of such element information item s MUST NOT be "http://www.w3.org/2004/03/wsdl".
name
attribute
information item with
fault
[owner]The name
attribute
information item identifies a
given fault
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 .
element
attribute information item with fault
[owner]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 .
The mapping between the properties of the
Interface Fault component (see 2.3.1 The
Interface Fault Component )
and the XML Representation of the fault
element
information item (see
2.3.2
XML Representation of Interface Fault Component
) is as described in Table
2-3 .
Property | Mapping |
---|---|
{name} | The actual value
of the name
attribute information item
. |
{target namespace} | The actual value
of the targetNamespace attribute information item of the [parent] definitions element information item of the [parent] interface element information item . |
{element} | The element
declaration from the {element declarations} property of
2.1.1 The
Definitions Component resolved to by the value of the
element attribute information item if present, otherwise empty. It is an error for
the element
attribute information item
to have a value and for it to not resolve to
a global element declaration from the {element declarations}
property of 2.1.1 The Definitions Component . |
An Interface Operation component describes an operation that a given interface supports. An operation is an interaction with the service consisting of a set (ordinary and fault) messages exchanged between the service and the other roles involved in the interaction, in particular the service requester. requestor. The sequencing and cardinality of the messages involved in a particular interaction is governed by the message exchange pattern used by the operation (see {message exchange pattern} property).
A message exchange pattern defines placeholders for messages, the participants in the pattern (i.e., the sources and sinks of the messages), and the cardinality and sequencing of messages exchanged by the participants. The message placeholders are associated with specific message types by the operation using that uses the pattern via by means of message and fault references (see {message references} and {fault references} properties). The service whose operation is using the pattern becomes one of the participants of the pattern. This specification does not define a machine understandable language for defining message exchange patterns patterns, nor does it define any specific patterns. The companion specification, [ WSDL 2.0 Message Exchange Patterns ] defines a set of such patterns and defines identifying URIs any of which MAY be used as the value of the {message exchange pattern} property.
The properties of the Interface Operation component are as follows:
{name} An NCName as defined by [ XML Namespaces ].
{target namespace} A namespace name, as defined in [ XML Namespaces ].
{message exchange pattern} A URI identifying the message exchange pattern used by the operation. This URI MUST be an absolute URI (see [ IETF RFC 2396 ]).
{message references} A set of Message Reference components for the ordinary messages the operation accepts or sends. (See 2.4 2.5 Message Reference .)
{fault references} A set of Fault Reference components for the fault messages the operation accepts or sends. (See 2.5 2.6 Fault Reference .)
{style} A URI identifying the rules that were used to construct the {message} {element} properties of {message references}. (See 2.3.1.1 2.4.1.1 Operation Style .)This URI MUST be an absolute URI (see [ IETF RFC 2396 ]).
{safety} A boolean indicating whether the operation is asserted to be safe (as defined in Section 3.5 of [ Web Architecture ]) for users of the described service to invoke. If this property is false or is not set, then no assertion has been made about the safety of the operation, thus the operation MAY or MAY NOT be safe. However, an operation SHOULD be marked safe if it meets the criteria for a safe interaction defined in Section 3.5 of [ Web Architecture ]. The default value of this property is false.
{features} A set of named feature definitions used by the operation
{properties} A set of named property definitions used by the operation
For each Interface Operation component in the {operations} property of an Interface component, the combination of {name} and {target namespace} properties MUST be unique.
Interface Operation components are local to Interface components; they cannot be referred to by QName, despite having both {name} and {target namespace} properties. That is, deleted text: this specification does not preclude one from having two deleted text: distinct Interface deleted text: Operation components which have sharing the same deleted text: {name} and {target namespace} properties, as long as they are in property but with different {name} properties MAY contain Interface Operation components (with which share the same {name} property. Thus, the {name} and {target namespace} property). </p> <p> For each properties of the Interface Operation component in the {operations} property of components are not sufficient to uniquely identify an Interface component Operation component. In order to uniquely identify an Interface Operation component, one must first identify the combination of {name} Interface component (by QName) and {target namespace} properties must be unique. then identify the Interface Operation within that Interface component (by a further QName).
In cases where, due to an interface extending one or more other interfaces, two or more Interface Operation components have the same value for their {name} and {target namespace} properties, then the component models of those Interface Operation components MUST be equivalent (see 2.14 2.15 Equivalence of Components ). If the Interface Operation components are equivalent then they are considered to collapse into a single component. It is an error if two Interface Operation components have the same value for their {name} and {target namespace} properties but are not equivalent.
deleted text: <div class="note"> <p class="prefix"> <b> Note: </b> </p>Due Note that, due to the above rules, if two interfaces that have the same value for their {target namespace} property also have one or more operations that have the same value for their {name} property then those two interfaces cannot both form part of the derivation chain of a derived interface unless those operations are the same operation. Therefore
Note:
For the above reason, it is considered good practice to ensure, where necessary, that the {name} property of Interface Operation components within a namespace are unique, thus allowing such derivation to occur without inadvertent error.
If the {style} property of an Interface Operation component has a value then that value (a URI) implies the rules that were used to define the {message} {element} properties (or other property which defines the content of the message properties; see 3.2 Using Other Schema Languages ) of all the Message Reference components which are members of the {message reference}s within references} property of that component. Note that the property MAY not have any value. If this property has a given value, then the rules implied by that value (such as rules that govern the schemas) MUST be followed or it is an error.
This specification defines the following pre-defined operation styles: style:
RPC Style (see 2.3.1.1.1 2.4.4 RPC Style )
<definitions> <interface> <operation name="xs:NCName" pattern="xs:anyURI" style="<em>xs:anyURI</em>"? > style="xs:anyURI"? safe="xs:boolean"? > <documentation />? [ <feature /> | <property /> | [ <input /> | <output /> | <infault /> | <outfault /> ]+ ]* </operation> </interface> </definitions>
The XML representation for an Interface Operation component is an element information item with the following Infoset properties:
A [local name] of operation
A [namespace name] of "http://www.w3.org/2003/11/wsdl" "http://www.w3.org/2004/03/wsdl"
Two or more attribute information item s amongst its [attributes] as follows:
A REQUIRED name
attribute information item
as described below in 2.3.2.1 2.4.2.1
name attribute information item with operation [owner]
.
A REQUIRED pattern
attribute information
item as described below in 2.3.2.2 2.4.2.2
pattern attribute information item with operation [owner]
.
An OPTIONAL style
attribute information
item as described below in 2.3.2.3 2.4.2.3
style attribute information item with operation [owner]
.
An OPTIONAL safe
attribute
information item as described
below in 2.4.2.4 safe attribute information item with operation
[owner] .
Zero or more namespace qualified attribute information item s. The [namespace name] of such attribute information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
Zero or more element information item amongst its [children], in order, as follows:
An OPTIONAL documentation
element information
item (see 5.
Documentation ).
Zero or more element information item s from among the following, in any order:
Zero or more input
element information
item s (see 2.4.2 2.5.2 XML
Representation of Message Reference Component ).
Zero or more output
element information
item s (see 2.4.2 2.5.2 XML
Representation of Message Reference Component ).
Zero or more infault
element information
item s (see 2.5.2 2.6.2 XML
Representation of Fault Reference Component ).
Zero or more outfault
element information
item s (see 2.5.2 2.6.2 XML
Representation of Fault Reference Component ).
A feature
element information item (see
2.6.2
2.7.2 XML Representation of Feature
Component ).
A property
element information item (see
2.7.2
2.8.2 XML Representation of Property
Component ).
Zero or more namespace-qualified element information item s amongst its [children]. The [namespace name] of such element information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
At least one of the [children] MUST be an input
,
output
, infault
, or
outfault
element information item .
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 .
pattern
attribute information item with
operation
[owner]The pattern
attribute information item
identifies the message exchange 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 .
style
attribute information item with
operation
[owner]The style
attribute information item
indicates the rules that were used to construct the {message} {element}
properties of {message reference}
the Message Reference components
which are members of the {message
references} property of the [owner] operation.
The style
attribute information item has
the following Infoset properties:
A [local name] of style
A [namespace name] which has no value
The type of the style
attribute information
item is xs:anyURI .
safe
attribute
information item with
operation
[owner]The safe
attribute
information item indicates
whether the operation is safe or
not.
The safe
attribute
information item has the
following Infoset properties:
A [local name] of
safe
A [namespace name] which has no value
The type of the safe
attribute
information item is
xs:boolean and does not have a default value.
The mapping between the properties of the Interface Operation
component (see 2.3.1
2.4.1 The Interface Operation
Component ) and the XML Representation of the
interface operation
element information
item (see 2.3.2 2.4.2 XML
Representation of Interface Operation Component ) is as
described in Table
2-3 2-4 .
Property | Mapping |
---|---|
{name} | The actual value of the
name attribute information item |
{target namespace} | The actual value of the
targetNamespace attribute information item of
the [parent] definitions element information
item of the [parent] interface element
information item . |
{message exchange pattern} | The actual value of the
pattern attribute information item |
{message references} | The set of message references
corresponding to the input and output
element information item s in [children], if any. |
{fault references} | The set of fault references
corresponding to the infault and outfault
element information item s in [children] [children], if any. |
{style} | The actual value of the
style attribute information item if present,
otherwise the actual value of the styleDefault
attribute information item of the [parent]
interface element information item if
present, otherwise none. |
{safety} | The actual value
of the safe
attribute information item
if present, otherwise the value
false . |
{features} | The set of features corresponding to
the feature element information item s in
[children], if any. |
{properties} | The set of properties corresponding to
the property element information item s in
[children], if any. |
The RPC style is selected by assigning to an Interface Operation component's {style} property the value http://www.w3.org/2004/03/wsdl/style/rpc .
The RPC style MUST NOT be used for Interface Operation components whose {message exchange pattern} property has a value other than 'http://www.w3.org/2004/03/wsdl/in-only' or 'http://www.w3.org/2004/03/wsdl/in-out'.
Use of this value indicates that XML Schema [ XML Schema: Structures ] was used to define the schemas of the {element} properties of all {message reference} components of the Interface Operation component. Those schemas MUST adhere to the rules below.
Note that if the Interface Operation component uses the {message exchange pattern} 'http://www.w3.org/2004/03/wsdl/in-only' then there is no output element and hence the rules which refer to the output element do not apply.
The content model of input and output {element} elements are defined using a complex type that contains a sequence from XML Schema.
The sequence MUST only contain elements. It MUST NOT contain other structures such as xs:choice.
The sequence MUST contain only local element children. Note that these child elements MAY contain the following attributes: nillable, minOccurs and maxOccurs.
The LocalPart of input element's QName MUST be the same as the Interface operation component's name.
The LocalPart of the output element's QName is obtained by concatenating the name of the operation and the string value "Response", i.e. concat(operation/@name,"Response").
Input and output elements MUST both be in the same namespace.
The complex type that defines the body of an input or an output element MUST NOT contain any attributes.
If elements with the same qualified name appear as children of both the input and output elements, then they MUST both be declared using the same type.
The input or output sequence MUST NOT contain multiple children elements declared with the same name.
wrpc:signature
ExtensionThe wrpc:signature
extension AII MAY be be used in conjunction with the RPC
style to describe the exact signature of the function represented
by an operation that uses the RPC style.
When present, the
wrpc:signature
extension contributes the following property
to the interface operation component it is applied to:
{rpc-signature} A (possibly empty) list of pairs (q, t) whose first component is of type xs:QName (as defined by [ XML Namespaces ]) and whose second component is of type xs:Token (as defined by [ XML Namespaces ]). Values for the second component MUST be chosen among the following four: "#in", "#out", "#inout" "#return".
The value of the {rpc-signature} property MUST satisfy the following conditions:
The value of the first component of each pair (q, t) MUST be unique within the list.
For each child element of the input and output messages of the operation, a pair (q, t) whose first component q is equal to the qualified name of that element MUST be present in the list, with the caveat that elements that appear with cardinality greater than one MUST be treated as as a single element.
For each pair (q, #in) ,there MUST be a child element of the input element with a name of q and there MUST NOT be a child element of the output element with the same name.
For each pair (q, #out) ,there MUST be a child element of the output element with a name of q and there MUST NOT be a child element of the input element with the same name.
For each pair (q, #inout) ,there MUST be a child element of the input element with a name of q and there MUST be a child element of the output element with the same name. Furthermore, those two elements MUST have the same type.
For each pair (q, #return) ,there MUST be a child element of the output element with a name of q and there MUST NOT be a child element of the input element with the same name.
The function signature defined by
a wrpc:signature
extension is determined as
follows:
Start with the value of the {rpc-signature} property, a (possibly empty) list of pairs of this form:
[(q0, t0), (q1, t1), ...]
Filter the elements of this list into two lists, the first one (L1) comprising pairs whose t component is one of {#in, #out, #inout} ,the second (L2) pairs whose t component is #return .
For ease of visualization, let's denote the two lists as
(L1) [(a0, u0), (a1, u1),...]
and
(L2) [(r0, #return), (r1, #return),...]
respectively.
Then the formal signature of the function is
f([d0] a0, [d1] a1, ...) => (r0, r1, ...)
i.e.
the list of formal arguments to the function is [a0, a1, ...] ;
the direction of each formal argument a is one of [in] ,[out] ,[inout] ,determined according to the value of its corresponding u token;
the list of formal return parameters of the function is [r0, r1, ...] ;
each formal argument and formal return parameter is typed according to the type of the child element identified by it (unique per the conditions given above).
wrpc:signature
ExtensionThe XML representation for the RPC signature extension is an attribute information item with the following Infoset properties:
A [local name] of
signature
A [namespace name] of "http://www.w3.org/2004/03/wsdl/rpc"
The type of the name
attribute
information item is a list type
whose item type is the union of the xs:QName type and the
subtype of the xs:Token type
restricted to the following four values: "#in", "#out", "#inout",
"#return". See Example 2-1 for a
definition of this type.
Additionally, each even-numbered item (0, 2, 4, ...) in the list MUST be of type xs:QName and each odd-numbered item (1, 3, 5, ...) in the list MUST be of type xs:Token .
Example 2-1. Definition of the wrpc:signature extension
<xs:attribute name="signature" type="wrpc:signatureType"/>
<xs:simpleType name="signatureType">
<xs:list itemType="wrpc:signatureItemType"/>
</xs:simpleType>
<xs:simpleType name="signatureItemType">
<xs:union memberTypes="wrpc:directionToken xsd:QName"/>
</xs:simpleType>
<xs:simpleType name="directionToken">
<xs:restriction base="xs:token">
<xs:enumeration value="#in"/>
<xs:enumeration value="#out"/>
<xs:enumeration value="#inout"/>
<xs:enumeration value="#return"/>
</xs:restriction>
</xs:simpleType>
wrpc:signature
Extension Mapping To Properties of an Interface
Operation ComponentA wrpc:signature
extension attribute
information item is mapped to
the following property of the Interface Operation component
(see 2.4.1 The Interface Operation Component
) defined by its [owner].
Property | Mapping |
---|---|
{rpc-signature} | A list of
(xs:QName, xs:Token)
pairs formed by grouping the items present
in the actual value of the wrpc:signature attribute information item in the order in which they appear there. |
A Message Reference component associates to a message exchanged in an operation an XML element declarations declaration that define the specifies its message content for one of the messages participating in an operation. content.
Message Reference components are identified by the role the message plays in the {message exchange pattern} that the operation is using. That is, a message exchange pattern defines a set of /meof placeholder messages that participate in the pattern and assigns them unique names within the pattern. The purpose of a Message Reference component is to associate an actual message type (XML element declaration or some other declaration (see 3.2 Using Other Schema Languages ) for message content) for with the message that will perform a specific role in the message exchange pattern.
The properties of the Message Reference component are as follows:
{message reference} label} An NCName as defined by [ XML Namespaces ]. This property identifies the role this message plays in the {message exchange pattern} of the Interface Operation component this is contained within. The value of this property MUST match the name of a placeholder message defined by the message exchange pattern.
{direction} One of in or out indicating whether the message is coming to the service or going from the service, respectively. The direction MUST be the same as the direction of the message identified by the {message reference} label} property in the {message exchange pattern} of the Interface Operation component this is contained within.
{message} {message content model} A token with one of the values #any ,#none ,or #element .A value of #any indicates that the message content is any single element. A value of #none indicates there is no message content. A value of #element indicates that the message consists of a single element described by the global element declaration reference by the {element} property.
{element} A reference to an XML element declaration. declaration in the {element declarations} property of 2.1.1 The Definitions Component . This element represents the content or "payload" of the message. When the {message content model} property has the value #any or #none the {element} property has no value.
If a non-XML type system is in use (as considered in 3.2 Using Other Schema Languages ) then additional properties would need to be added to the Message Reference Component (along with extensibility attributes to its XML representation) to allow associating such message types with the message reference.
For each Message Reference component in the {message references} property of an Interface Operation component the component, its {message reference} label} property MUST be unique.
<definitions> <interface> <operation> <input messageReference="<em>xs:NCName</em>"? message="<em>xs:QName</em>"? > messageLabel="xs:NCName"? element="union of xs:QName, xs:Token"? > <documentation />? </input> <output messageReference="<em>xs:NCName</em>"? message="<em>xs:QName</em>"? > messageLabel="xs:NCName"? element="union of xs:QName, xs:Token"? > <documentation />? </output> </operation> </interface> </definitions>
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/11/wsdl" "http://www.w3.org/2004/03/wsdl"
Zero or more attribute information item s amongst its [attributes] as follows:
An OPTIONAL messageReference
messageLabel
attribute
information item as described below in 2.4.2.1 messageReference 2.5.2.1 messageLabel attribute information item
with input, or output [owner] .
If the {message exchange pattern} of the Interface Operation
component has only one message with a given value for {direction},
then the messageReference
messageLabel
attribute
information item is optional for the XML representation of the
Message Reference component with that {direction}.
An OPTIONAL message
element
attribute
information item as described below in <a href=
"#MessageReference_message_attribute"> 2.4.2.2 message 2.5.2.2
element attribute information item with input, or output
[owner] .
Zero or more namespace qualified attribute information item s. The [namespace name] of such attribute information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
Zero or more element information item s amongst its [children], in order, as follows:
An OPTIONAL documentation
element information
item (see 5.
Documentation ).
Zero or more namespace-qualified element information item s. The [namespace name] of such element information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
messageReference messageLabel
attribute information
item with input
, or output
[owner]The messageReference
messageLabel
attribute
information item identifies the role of this message in the
message exchange pattern of the given operation
element information item .
The messageReference
messageLabel
attribute
information item has the following Infoset properties:
A [local name] of messageReference messageLabel
A [namespace name] which has no value
The type of the messageReference messageLabel
attribute information
item is xs:NCName .
message element
attribute information
item with input
, or output
[owner]The deleted text:
message </code> <em> attribute
information item </em> refers, by QName, to an element
deleted text: declaration component. </p> <p> The
<code> message
attribute information
item has the following Infoset properties:
A [local name] of message
element
.
A [namespace name] which has no value.
The type of the message
element
attribute
information item is a union of
xs:QName and
xs:Token where the allowed token values are
#any or #none
.
The mapping between the properties of the Message Reference component (see 2.4.1 2.5.1 The Message Reference Component ) and the XML Representation of the message reference element information item (see 2.4.2 2.5.2 XML Representation of Message Reference Component ) is as described in Table 2-4 2-6 .
Property | Mapping |
---|---|
{message reference} label} | The actual value of the
messageReference messageLabel attribute information
item if any; otherwise the {message reference} label}
property of the message with same {direction} from the {message
exchange pattern} of the Interface Operation component, provided
there is exactly one such message; otherwise empty. |
{direction} | If the [local name] of the element
information item is input then "in", else if the
[local name] of the element information item is
output then "out". |
{message} {message content model} | The
If the element declaration resolved to by
attribute information item
is present and its value is a QName,
then #element
.Otherwise the actual value of the message element attribute information item
</em> , if present, otherwise any. |
{element} | If the
element attribute information item is present and its value is a similar construct in some type system as referred
QName, then the element declaration from the
{element declarations} property of 2.1.1 The
Definitions Component resolved to by some
other the value of the
element attribute
information item </em> if
present, , otherwise empty. It
is an error for the element attribute information item to have a value and for it to not resolve to a global
element declaration from the {element declarations} property
of 2.1.1 The Definitions Component . |
A Fault Reference component associates an XML element declaration a Fault component that defines the fault message contents type for a fault that occurs related to a message participating in an operation.
Fault Reference components are identified by the role the related message plays in the {message exchange pattern} that the operation is using. That is, a message exchange pattern defines a set of placeholder messages that participate in the pattern and assigns them unique names labels within the pattern. The purpose of a Fault Reference component is to associate an actual message type (XML element declaration) Fault component for the fault that will occur related to with a specific message in the message exchange pattern.
The companion specification [ WSDL 2.0 Message Exchange Patterns ] defines two fault patterns that a given message exchange pattern may use. For the pattern fault-replaces-message , the message that the fault relates to identifies the message in place of which the declared fault message will occur. Thus, the fault message will travel in the same direction as the message it replaces in the pattern. For the pattern message-triggers-fault , the message that the fault relates to identifies the message after which the indicated fault may occur, in the opposite direction of the referred to message. That is, the fault message will travel in the opposite direction of the message it comes after in the pattern.
More than one Fault Reference component may refer to the same message role. label. This allows one to indicate that there is more than one type of fault that is related to that message.
The properties of the Fault Reference component are as follows:
deleted text: {name} An NCName as defined by [ <cite> <a href="#XMLNS"> XML Namespaces </a> </cite> ]. This property is used to identify the fault. </p> </li> <li> <p> {message reference} label} An NCName as defined by [ XML Namespaces ]. This property identifies the message deleted text: which this fault relates to among those defined in the {message exchange pattern} property of the Interface Operation component this it is contained within. The value of this property MUST match the name of a placeholder message defined by the message exchange pattern.
{direction} One of in or out indicating whether the fault is coming to the service or going from the service, respectively. The direction MUST be consistent with the direction implied by the fault rule used in the message exchange pattern of the operation. For example, if the fault rule fault-replaces-message is used, then a fault which refers to an outgoing message would have a {direction} property value of out . If On the other hand, if the fault rule message-triggers-fault is used, then a fault which refers to an outgoing message would have a {direction} property value of in as the fault travels in the opposite direction of the message.
{message} {fault reference} A reference to an XML element declaration. This element represents a Fault component in the content or "payload" {faults} property of the fault. </p> </li> </ul> <p> If two or more parent Interface Operation components in the same component's parent Interface component have Fault Reference components with component. Identifying the same {name} value, then their {message} properties MUST have Fault component therefore indirectly defines the same value. This allows two actual content or more operations to indicate that they both produce payload of the same fault. fault message.
<definitions> <interface> <operation> <infault name="<em>xs:NCName</em>" messageReference="<em>xs:NCName</em>"? message="<em>xs:QName</em>"? ref="xs:QName" messageLabel="xs:NCName"? > <documentation />? </infault>* <outfault name="<em>xs:NCName</em>" messageReference="<em>xs:NCName</em>"? message="<em>xs:QName</em>"? ref="xs:QName" messageLabel="xs:NCName"? > <documentation />? </outfault>* </operation> </interface> </definitions>
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/11/wsdl" "http://www.w3.org/2004/03/wsdl"
One or more attribute information item s amongst its [attributes] as follows:
A REQUIRED name ref
attribute information item as
described below in <a href=
"#FaultReference_name_attribute"> 2.5.2.1
name 2.6.2.1 ref attribute
information item with infault, or outfault [owner] .
An OPTIONAL messageReference
messageLabel
attribute
information item as described below in 2.5.2.2 messageReference 2.6.2.2 messageLabel attribute information item
with infault, or outfault [owner] .
If the {message exchange pattern} of the Interface Operation
component has only one message with a given value for {direction},
the messageReference
messageLabel
attribute
information item is optional for the XML representation of any
Fault Reference component with the same value for {direction} (if
the fault pattern of the {message exchange pattern} is
fault-replaces-message ) or of any Fault Reference
component with the opposite value for {direction} (if the fault
pattern is message-triggers-fault ).
deleted text: An OPTIONAL <code> message </code> <em> attribute information item </em> as described below in <a href= "#FaultReference_message_attribute"> <b> 2.5.2.3 message attribute information item with infault, or outfault [owner] </b> </a>. </p> </li> <li> <p> Zero or more namespace qualified attribute information item s. The [namespace name] of such attribute information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
Zero or more element information item s amongst its [children], in order, as follows:
An OPTIONAL documentation
element information
item (see 5.
Documentation ).
Zero or more namespace-qualified element information item s. The [namespace name] of such element information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
name ref
attribute information item
with infault
, or outfault
[owner]The name ref
attribute information item
identifies the fault. refers to a fault component.
The name ref
attribute information item
has the following Infoset properties:
A [local name] of name
ref
A [namespace name] which has no value
The type of the name
fault
attribute
information item is xs:NCName xs:QName .
messageReference messageLabel
attribute information
item with infault
, or outfault
[owner]The messageReference
messageLabel
attribute
information item identifies the message in the message
exchange pattern of the given operation
element
information item to which this fault is related to.
The messageReference
messageLabel
attribute
information item has the following Infoset properties:
A [local name] of messageReference messageLabel
A [namespace name] which has no value
The type of the messageReference messageLabel
attribute information
item is xs:NCName .
The mapping between the properties of the Fault Reference component (see 2.5.1 2.6.1 The Fault Reference Component ) and the XML Representation of the message reference element information item (see 2.5.2 2.6.2 XML Representation of Fault Reference Component ) is as described in Table 2-5 2-7 .
Property | Mapping |
---|---|
{name} {fault reference} | The actual value of the
name ref attribute information
item |
{message reference} label} | The actual value of the
messageReference messageLabel attribute information
item if any; otherwise the {message reference} label}
property of the message with the same {direction} from the {message
exchange pattern} of the Interface Operation component, provided
there is exactly one such message and the fault pattern of
the {message exchange pattern} is fault-replaces-message ;
otherwise the {message reference} property of the message with the
opposite {direction}, provided there is exactly one such message
and the fault pattern is message-triggers-fault ;
otherwise empty. |
{direction} | If the [local name] of the element
information item is infault then "in", else if
the [local name] of the element information item is
outfault then "out". |
A feature component describes an abstract piece of functionality typically associated with the exchange of messages between communicating parties. Although WSDL poses no constraints on the potential scope of such features, examples might include "reliability", "security", "correlation", and "routing". The presence of a feature component in a WSDL description indicates that the service supports the feature is either accepted or required in particular interactions. </p> <p> Features in and may require a requester agent that interacts with the service to use that feature. Each Feature component are is identified by their its URI. deleted text: 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 An absolute URI as defined by [ <a href="#RFC2396"> IETF RFC 2396 ]. This URI SHOULD be dereferenceable to a document that directly or indirectly defines the meaning and use of the Feature that it identifies.
{required} A boolean value. If the {require} property is true, then the requester agent MUST use the Feature that is identified by the {name} URI. Otherwise, the requester agent MAY use the Feature that is identified by the {name} URI. In either case, if the requester agent does use the Feature that is identified by the {name} URI, then the requester agent MUST obey all semantics implied by the definition of that Feature.
The set of features which are required or available for a given service and a particular interaction consists of the combined set of ALL feature declarations in the following scope. The list is in order of increasing specificity.
The interface component.
The specific interface operation component.
The specific message reference component.
The binding component.
The specific binding operation component.
The specific binding message or fault reference component.
Note that multiple declarations of the
same feature have no effect on the combined set of active features,
since features are either in use or not, with no multiplicity. If
multiple declarations of the same feature are in scope for a given
interaction, the feature is required if ANY of the in scope
declarations have the required
attribute
set to "true".
In the following example, the
depositFunds
operation on the BankService
has to
be used with the ISO9001
,
the notarization
and the secure-channel
features; they are all in scope. The fact that
the notarization
feature is declared both in the operation
and in the service has no effect.
<definitions targetNamespace="http://example.com/bank"
xmlns:ns1="http://example.com/bank">
<interface name="ns1:Bank">
<!-- All uses of this interface must be secure -->
<feature uri="http://example.com/secure-channel"
required="true"/>
<operation name="withdrawFunds">
<!-- This operation must have ACID properties -->
<feature uri="http://example.com/transaction"
required="true"/>
...
</operation>
<operation name="depositFunds">
<!-- This operation requires notarization -->
<feature uri="http://example.com/notarization"
required="true"/>
...
</operation>
</interface>
<binding name="ns1:BankSOAPBinding">
</binding>
<service name="ns1:BankService"
interface="tns:Bank">
<!-- This particular service requires ISO9001
compliance to be verifiable -->
<feature uri="http://example.com/ISO9001"
required="true"/>
<!-- This service also requires notarization -->
<feature uri="http://example.com/notarization"
required="true"/>
<endpoint>
...
</endpoint>
</service>
</definitions>
<feature uri="<em>xs:QName</em>" uri="xs:anyURI" required="xs:boolean"? > <documentation />? </feature>
The XML representation for a Feature 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/11/wsdl" "http://www.w3.org/2004/03/wsdl"
One or more attribute information item s amongst its [attributes] as follows:
A REQUIRED uri
attribute information item
as described below in 2.6.2.1
2.7.2.1 uri attribute information
item with feature [owner] .
An OPTIONAL required
attribute information
item as described below in 2.6.2.2 2.7.2.2
required attribute information item with feature [owner]
.
Zero or more namespace qualified attribute information item s. The [namespace name] of such attribute information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
Zero or more element information item s amongst its [children], in order as follows:
An OPTIONAL documentation
element information
item (see 5.
Documentation ).
Zero or more namespace-qualified element information item s. The [namespace name] of such element information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
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
.
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
.
The mapping between the properties of the Feature component (see
2.6.1
2.7.1 The Feature Component )
and the XML Representation of the feature
element
information item (see 2.6.2
2.7.2 XML Representation of Feature
Component ) is as described in Table 2-6
2-8 .
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". |
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 An absolute URI as defined by [ <a href="#RFC2396"> IETF RFC 2396 ]. This URI SHOULD be dereferenceable to a document that directly or indirectly defines the meaning and use of the Property that it identifies.
{required} A boolean value. If the {required} property is true, then the requester agent MUST use the Property that is identified by the {name} URI. Otherwise, the requester agent MAY use the Property that is identified by the {name} URI. In either case, if the requester agent does use the Property that is identified by the {name} URI, then the requester agent MUST obey all semantics implied by the definition of that Property.
{value constraint} A type definition constraining the value of the property.
{value} The value of the property.
At runtime, the behaviour of features, (SOAP) modules and bindings may be affected by the values of in-scope properties. Properties combine into a virtual "execution context" which maps property names (URIs) to constraints. Each property URI MAY therefore be associated with AT MOST one property constraint for a given interaction.
The particular set of constraints for a given service and a particular interaction consists of the combined set of ALL constraints in the following scope. The list is in order of increasing specificity, and if a given property URI is constrained in a later scope, it overrides the earlier constraint.
The interface component.
The specific interface operation component.
The specific message reference component.
The binding component.
The specific binding operation component.
The specific binding message or fault reference component.
Note that, in the text above, "property
constraint" (or, simply, "constraint") is used to mean EITHER
a constraint
inside a property component OR a
value
, since value
may be
considered a special case of constraint
.
<property uri="<em>xs:QName</em>" uri="xs:anyURI" required="xs:boolean"? > <documentation />? [ <value /> | <constraint /> ] </property>
The XML representation for a Property component is an element information item with the following Infoset properties:
A [local name] of property
A [namespace name] of "http://www.w3.org/2003/11/wsdl" "http://www.w3.org/2004/03/wsdl"
One or more attribute information item s amongst its [attributes] as follows:
A REQUIRED uri
attribute information item
as described below in 2.7.2.1
2.8.2.1 uri attribute information
item with property [owner] .
An OPTIONAL required
attribute information
item as described below in 2.7.2.2 2.8.2.2
required attribute information item with feature [owner]
.
Zero or more namespace qualified attribute information item s. The [namespace name] of such attribute information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
One or more element information item s amongst its [children], in order as follows:
An OPTIONAL documentation
element information
item (see 5.
Documentation ).
One REQUIRED element information item from among the following:
A value
element information item as
described in 2.7.2.3 2.8.2.3
value element information item with property [parent]
A constraint
element information item as
described in 2.7.2.4 2.8.2.4
constraint element information item with property
[parent]
Zero or more namespace-qualified element information item s amongst its [children]. The [namespace name] of such element information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
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
.
required
attribute information item with
feature
[owner]The required
attribute information item
specifies whether deleted text:
the use of the property 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
.
value
element information item with property
[parent]<property> <value> <em>xs:anySimpleType</em> xs:anyType </value> </property>
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/11/wsdl" "http://www.w3.org/2004/03/wsdl"
The type of the value
element information
item is xs:anySimpleType
xs:anyType
.
constraint
element information item with
property
[parent]<property> <constraint> xs:QName </constraint> </property>
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/11/wsdl" "http://www.w3.org/2004/03/wsdl"
The type of the constraint
attribute
information item is xs:QName
.
The mapping between the properties of the Property component
(see 2.7.1 2.8.1 The
Property Component ) and the XML Representation of the
property
element information item (see
2.7.2
2.8.2 XML Representation of Property
Component ) is as described in Table 2-7
2-9 .
Property | Mapping |
---|---|
{name} | The actual value of the
uri attribute information item |
{value constraint} | If the constraint
element information item is present, the type referred to
by the value of this element information item . Otherwise,
deleted text: if the <code> value </code> <em>
element information item </em> is present, an
anonymous deleted text:
simple type, whose base type is
"xs:anySimpleType", "xs:anyType", with a single "enumeration" facet
whose value is that the type of the value of the value element information item .
Otherwise, "xs:anySimpleType".
"xs:anyType". |
{value} | The actual value
of the value
element information item
,if any. |
A Binding component describes a concrete message format and transmission protocol which may be used to define an endpoint (see 2.13 2.14 Endpoint ). Binding components can be used to describe such information in a re-usable manner for any interface or specifically for a given interface. Furthermore, binding information MAY be specified on a per-operation basis (see 2.9.1 2.11.1 The Binding Operation Component ) within an interface in addition to across all operations of an interface.
If a Binding component specifies any operation-specific binding details (by including Binding Operation components) or any fault binding details (by including Binding Fault components) then it MUST specify an interface the Binding component applies to to, so as to indicate which interface the operations come from.
Conversely, a Binding component MAY omit which omits any operation-specific binding details and any fault binding details MAY omit specifying an interface. Binding components that do not specify an interface MAY be used to specify operation-independent binding details for Service components with different interfaces. That is, such Binding components are reusable across one or more interfaces.
No concrete binding details are given in this specification. The companion specification, WSDL (Version 2.0): Bindings [ WSDL 2.0 Bindings ] defines such bindings for SOAP 1.2 [ SOAP 1.2 Part 1: Messaging Framework ], ] and HTTP [ IETF RFC 2616 deleted text: ] and MIME [ <cite> <a href= "#RFC2045"> IETF RFC 2045 </a> </cite> ]. Other specifications MAY define additional binding details. Such specifications are expected to annotate the Binding component (and its sub-components) with additional properties and specify the mapping between those properties and the XML representation.
A Binding component which defines bindings for an Interface component MUST define bindings for all the operations of that Interface component. The bindings may occur via defaulting rules which allow one to specify default bindings for all operations (see, for example [ WSDL 2.0 Bindings ]) or by directly listing each Operation component of the Interface component and defining bindings for them. Thus, it is an error for a Binding component to not define bindings for all the Operation components of the Interface component for which the Binding component purportedly defines bindings for.
Bindings are named constructs and can be referred to by QName (see 2.16 2.17 QName resolution ). For instance, Endpoint components refer to bindings in this way.
The properties of the Binding component are as follows:
{name} An NCName as defined by [ XML Namespaces ].
{target namespace} A namespace name, as defined in [ XML Namespaces ].
{interface} An named interface definition indicating the interface for which binding information is being specified.
{faults} A set of named binding fault definitions.
{operations} A set of named binding operation definitions definitions.
{features} A set of named feature definitions definitions.
{properties} A set of named property definitions definitions.
For each Binding component in the {bindings} property of a definitions container, the combination of {name} and {target namespace} properties must be unique.
<definitions> <binding name="xs:NCName" interface="xs:QName"? > <documentation />? [ <feature /> | <property /> | <operation /> ]* [ <fault /> | <operation /> | <feature /> | <property /> ]* </binding> </definitions>
The XML representation for a Binding component is an element information item with the following Infoset properties:
A [local name] of binding
A [namespace name] of "http://www.w3.org/2003/11/wsdl" "http://www.w3.org/2004/03/wsdl"
One or more attribute information item s amongst its [attributes] as follows:
A REQUIRED name
attribute information item
as described below in 2.8.2.1
2.9.2.1 name attribute information
item with binding [owner] .
An OPTIONAL interface
attribute information
item as described below in 2.8.2.2 2.9.2.2
interface attribute information item with binding [owner]
.
Zero or more namespace qualified attribute information item s. The [namespace name] of such attribute information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
Zero or more element information item s amongst its [children], in order, as follows:
An OPTIONAL documentation
element information
item (see 5.
Documentation ).
Zero or more element information item s from among the following, in any order:
Zero or more fault
element information item
s (see 2.10.2 XML
Representation of Binding Fault Component
).
Zero or more
operation
element information item s (see
2.9.2 2.11.2 XML
Representation of Binding Operation Component ).
Zero or more feature
element information
item s (see 2.6.2 2.7.2 XML
Representation of Feature Component ).
Zero or more property
element information
item s (see 2.7.2 2.8.2 XML
Representation of Property Component ).
Zero or more namespace-qualified element information item s. The [namespace name] of such element information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl". Such element information item s are considered to be binding extension elements(see 2.8.2.3 2.9.2.3 Binding extension elements ).
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 .
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 .
Binding extension elements are used to provide information specific to a particular binding. The semantics of such element information item s are defined by the specification for those element information item s. Such specifications are expected to annotate the Binding component with additional properties and specify the mapping between those properties and the XML representation.
The mapping between the properties of the Binding component (see
2.8.1
2.9.1 The Binding Component )
and the XML Representation of the binding
element
information item (see 2.8.2
2.9.2 XML Representation of Binding
Component ) is as described in Table 2-8
2-10 .
Property | Mapping |
---|---|
{name} | The actual value of the
name attribute information item |
{target namespace} | The actual value of the
targetNamespace attribute information item of
the [parent] definitions element information
item . |
{interface} | The Interface component resolved to by
the actual value of the interface attribute
information item , if any. |
{faults} | The set of
Binding Fault components corresponding to the
fault element information item s in [children], if any. |
{operations} | The set of Binding Operation components
corresponding to the operation element information
item s in [children], if any. |
{features} | The set of Feature components
corresponding to the feature element information
item s in [children], if any. |
{properties} | The set of Property components
corresponding to the property element information
item s in [children], if any. |
A Binding Operation Fault component describes a concrete binding for of a particular operation of fault within an interface to a particular concrete message format. A particular operation fault of an interface is uniquely identified by the target namespace of the interface and the name of the operation fault within that interface.
Note that the fault does not occur by itself - it occurs as part of a message exchange as defined by an Interface Operation component (and its binding counterpart the Binding Operation component). Thus, the fault binding information specified in a Binding Fault component describes how faults that occur within a message exchange of an operation will be formatted.
The properties of the Binding Operation Fault component are as follows:
{name} An NCName {fault reference} A QName as defined by [ <a href="#XMLNS"> XML Namespaces ]. </p> </li> <li> <p> {target namespace} A namespace name, as defined ] which refers to an Interface Fault component in [ <cite> <a href="#XMLNS"> XML Namespaces </a> </cite> ]. </p> </li> <li> <p> {message references} A set the {faults} property of Binding Message Reference components </p> </li> <li> <p> {fault references} A set the Interface component identified by the {interface} property of the parent Binding Fault Reference components </p> </li> </ul> <p> The tuple of properties {name} and {target namespace} identify component. This is the operation Interface Fault component for which binding information is being specified.
For each Binding Operation Fault component in the {operations} {faults} property of a Binding component component, the combination of {name} and {target namespace} properties must {fault reference} property MUST be unique. That is, one cannot define multiple bindings for the same operation. fault within a given Binding component.
<definitions> <binding> <<b>operation</b> name="<em>xs:QName</em>" > <fault ref="xs:QName" > <documentation />? [ <feature /> | <property /> | [ <input /> | <output /> | <infault /> | <outfault /> ]+ ]* </<b>operation</b>> </fault> </binding> </definitions>
The XML representation for a Binding Operation Fault component is an element information item with the following Infoset properties:
A [local name] of operation
fault
A [namespace name] of "http://www.w3.org/2003/11/wsdl" "http://www.w3.org/2004/03/wsdl"
One or more attribute information item s amongst its [attributes] as follows:
A REQUIRED name ref
attribute information item as
described below in <a href=
"#Binding_Operation_name_attribute"> 2.9.2.1
name 2.10.2.1 ref attribute
information item with operation
fault [owner] .
Zero or more namespace qualified attribute information item s. The [namespace name] of such attribute information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
Zero or more element information item s amongst its [children], in order, as follows:
An OPTIONAL documentation
element information
item (see 5.
Documentation ).
Zero or more deleted text: <em> element information item </em> s from among the following, in any order: </p> <ul> <li> <p> Zero or more <code> input </code> <em> element information item </em> s (see <a href="#Binding_Message_Reference"> <b> 2.10 Binding Message Reference </b> </a> ) </p> </li> <li> <p> Zero or more <code> output </code> <em> element information item </em> s (see <a href="#Binding_Message_Reference"> <b> 2.10 Binding Message Reference </b> </a> ) </p> </li> <li> <p> Zero or more <code> infault </code> <em> element information item </em> s (see <a href="#Binding_Message_Reference"> <b> 2.10 Binding Message Reference </b> </a> ) </p> </li> <li> <p> Zero or more <code> outfault </code> <em> element information item </em> s (see <a href="#Binding_Message_Reference"> <b> 2.10 Binding Message Reference </b> </a> ) </p> </li> <li> <p> Zero or more <code> feature </code> <em> element information item </em> s </p> </li> <li> <p> Zero or more <code> property </code> <em> element information item </em> s </p> </li> <li> <p> Zero or more namespace-qualified element information item s amongst its [children]. The [namespace name] of such element information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl". Such element information item s are considered to be binding operation fault extension elements as described below (see <a href= "#Binding_Operation_extension_elements"> 2.9.2.2 2.10.2.2 Binding Operation Fault extension elements ).
name
ref
attribute information
item with operation
fault
[owner]The name </code> <em>
attribute information item </em> identified a given
<code> operation </code> <em> element information
item </em> within a given <code> binding </code>
<em> element information item </em>. </p>
<p> The <code> name ref
attribute information item
has the following Infoset properties:
A [local name] of name
ref
A [namespace name] which has no value
The type of the name
ref
attribute information
item is xs:QName .
Binding Operation Fault extension elements are used to provide information specific to a particular operation fault in a binding. The semantics of such element information item s are defined by the specification for those element information item s. Such specifications are expected to annotate the Binding Operation Fault component with additional properties and specify the mapping between those properties and the XML representation.
The mapping between the properties of the Binding Operation Fault
component (see <a
href="#Binding_Operation_details"> 2.9.1
2.10.1 The Binding Operation Fault
Component ) and the XML Representation of the
binding fault
element information item
(see <a
href="#Binding_Operation_XMLRep"> 2.9.2
2.10.2 XML Representation of Binding
Operation Fault Component ) is as described in
<a href=
"#tab_Binding_Operation_Mapping"> Table 2-9 2-11 .
Property | Mapping |
---|---|
{name} </td> <td rowspan="1" colspan="1"> The value of the [local name] Infoset property of the qualified name which is the actual value of the <code> name </code> <em> attribute information item </em>. </td> </tr> <tr> <td rowspan="1" colspan="1"> {target namespace} {fault reference} | The deleted
text: value of the [namespace name]
Infoset property of the qualified name which is the actual
value of the name ref attribute information item
. |
A Binding Message Reference Operation component describes a concrete binding for of a particular deleted text: message participating in an operation of an interface to a particular concrete message format. A particular operation of an interface is uniquely identified by the target namespace of the interface and the name of the operation within that interface.
The properties of the Binding Message Reference Operation component are as follows:
{message {operation reference} An NCName A QName as defined by [ XML Namespaces ]. The value ] which refers to an Interface Operation component in the {operations} property of this the Interface component identified by the {interface} property identifies of the message within parent Binding component. This is the operation Interface Operation component for which binding details are information is being specified.
{direction} One {message references} A set of <em> in </em> or <em> out </em> indicating whether the message is coming to the service or going from the service, respectively. Binding Message Reference components
For each Binding Message Reference Operation component in the {message references} {operations} property of a Binding Operation component component, the {message {operation reference} property must MUST be unique. That is, one cannot define multiple bindings for the same message operation within a given Binding component.
Interface Operation components are local to Interface components; they cannot be bound twice within referred to by QName, despite having both {name} and {target namespace} properties. That is, two Interface components sharing the same operation. {target namespace} property but with different {name} properties MAY contain Interface Operation components which share the same {name} property. Thus, the {name} and {target namespace} properties of the Interface Operation components are not sufficient to form the unique identity of an Interface Operation component. To uniquely identify an Interface Operation component one must first identify the Interface component (by QName) and then identify the Interface Operation within that Interface component (by a further QName).
<definitions> <binding> <operation> <<b>input</b> messageReference="<em>xs:NCName</em>" > <documentation />? </<b>input</b>> <<b>output</b> messageReference="<em>xs:NCName</em>" > <documentation />? </<b>output</b>> </operation> <operation ref="xs:QName" > <documentation />? [ <input /> | <output /> | <feature /> | <property /> ]* </operation> </binding> </definitions>
The XML representation for a Binding Message Reference Operation component is an element information item with the following Infoset properties:
A [local name] of input
</code> or <code> output operation
.
A [namespace name] of "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl"
One or more attribute information item s amongst its [attributes] as follows:
A REQUIRED messageReference
ref
attribute information
item as described below in <a href=
"#Binding_Message_Reference_name_attribute"> 2.10.2.1 messageReference 2.11.2.1 ref attribute information item with
input or output operation [owner] .
Zero or more namespace qualified attribute information item s. The [namespace name] of such attribute information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
Zero or more element information item s amongst its [children], in order, as follows:
An OPTIONAL documentation
element information
item (see 5.
Documentation ).
Zero or more element information item s from among the following, in any order:
Zero or more input
element
information item s (see
2.12
Binding Message Reference )
Zero or more output
element
information item s (see
2.12
Binding Message Reference )
Zero or more feature
element
information item s
Zero or more property
element information item s
Zero or more namespace-qualified element information item s amongst its [children]. The [namespace name] of such element information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl". Such element information item s are considered to be binding message reference operation extension elements, elements as described below (see <a href= "#Binding_Message_Reference_extension_elements"> 2.10.2.2 2.11.2.2 Binding Message Reference Operation extension elements ).
messageReference ref
attribute information item
with input </code> or
<code> output operation
[owner]The messageReference
ref
attribute information
item has the following Infoset properties:
A [local name] of messageReference ref
.
A [namespace name] which has no value. value
The type of the messageReference ref
attribute information item is
xs:NCName xs:QName .
Binding Message Reference Operation extension elements are used to provide information specific to a particular message operation in an operation. a binding. The semantics of such element information item s are defined by the specification for those element information item s. Such specifications are expected to annotate the Binding Message Reference Operation component with additional properties and specify the mapping between those properties and the XML representation.
The mapping between the properties of the Binding Message Reference Operation component (see <a href=
"#Binding_Message_Reference_details"> 2.10.1 2.11.1 The
Binding Message Reference
Operation Component ) and the
XML Representation of the binding operation
element information
item (see <a
href="#Binding_Message_Reference_XMLRep"> 2.10.2
2.11.2 XML Representation of Binding
Message Reference Operation Component ) is as described in
<a href=
"#tab_Binding_Message_Reference_Mapping"> Table 2-10 2-12 .
Property | Mapping |
---|---|
{message {operation reference} | The actual value of the
messageReference ref attribute information item
</em> . |
{direction} {messages references} | If the [local
name] The set of Binding Message Reference components corresponding
to the input
and output element information item
is <code> input </code> then
"in", else s in [children], if
the [local name] any. |
{features} | The set
of Feature components corresponding
to the feature
element information item is
in [children], if any. |
{properties} | The set of
Property components corresponding to the output property then
"out". element information
item in [children], if
any. |
A Binding Fault Message Reference component describes a concrete binding of a particular deleted text: fault message of participating in an operation to a particular concrete message format.
The properties of the Binding Fault Message Reference component are as follows:
{name} {message label} An NCName as defined by [ <a href="#XMLNS"> XML Namespaces ]. The value of this property MUST be the same as identifies the {name} property of a Fault Reference component of role that the Interface Operation component message for which binding details are being specified. </p> </li> <li> <p> specified plays in the {message reference} An NCName as defined by [ <cite> <a href= "#XMLNS"> XML Namespaces </a> </cite> ]. The value exchange pattern} of deleted text: this property identifies the message within the operation for which this fault relates to and for which fault binding details are Interface Operation component being specified. bound by the containing Binding Operation component.
{direction} One of in or out indicating whether the message is coming to the service or going from the service, respectively. The direction MUST be the same as the direction of the message identified by the {message label} property in the {message exchange pattern} of the Interface Operation component being bound by the containing Binding Operation component.
For each Binding Fault Message Reference component in the {message references} property of a Binding Operation component component, the {message reference} label} property must MUST be unique. That is, the same deleted text: fault message cannot be bound twice within the same operation.
<definitions> <binding> <operation> <<b>infault</b> name="<em>xs:NCName</em>" messageReference="<em>xs:NCName</em>" > <input messageLabel="xs:NCName"? > <documentation />? </<b>infault</b>> <<b>outfault</b> name="<em>xs:NCName</em>" messageReference="<em>xs:NCName</em>" > </input> <output messageLabel="xs:NCName"? > <documentation />? </<b>outfault</b>> </output> </operation> </binding> </definitions>
The XML representation for a Binding Fault Message Reference component is an element information item with the following Infoset properties:
A [local name] of infault
input
or outfault output
.
A [namespace name] of "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
Two One or more attribute information item s amongst its [attributes] as follows:
A REQUIRED An OPTIONAL name messageLabel
attribute information
item as described below in <a href=
"#Binding_Fault_Reference_name_attribute"> 2.11.2.1 name 2.12.2.1
messageLabel attribute information item with infault input or
outfault output [owner] .
A REQUIRED If the {message exchange pattern} of the Interface
Operation component being bound has only one message with a given
value for {direction}, then the messageReference messageLabel
attribute information
item as described below in <a href=
"#Binding_Fault_Reference_messageReference_attribute"> <b>
2.11.2.2 messageReference attribute information item
is optional for the XML representation of
the Binding Message Reference component with infault or outfault [owner] </b>
</a>. that
{direction}.
Zero or more namespace qualified attribute information item s. The [namespace name] of such attribute information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
Zero or more element information item s amongst its [children], in order, as follows:
An OPTIONAL documentation
element information
item (see 5.
Documentation ).
Zero or more namespace-qualified element information item s amongst its [children]. The [namespace name] of such element information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl". Such element information item s are considered to be Binding Fault binding message reference extension elements, as described below (see <a href= "#Binding_Fault_Reference_extension_elements"> 2.11.2.3 2.12.2.2 Binding Fault Message Reference extension elements ).
messageReference messageLabel
attribute information
item with infault
input
or outfault output
[owner]The messageReference
messageLabel
attribute
information item has the following Infoset properties:
A [local name] of messageReference messageLabel
.
A [namespace name] which has no value.
The type of the messageReference messageLabel
attribute information
item is xs:NCName .
Binding Fault Message Reference extension elements are used to provide information specific to a particular message in an operation. The semantics of such element information item s are defined by the specification for those element information item s. Such specifications are expected to annotate the Binding Fault Message Reference component with additional properties and specify the mapping between those properties and the XML representation.
The mapping between the properties of the Binding Fault Message
Reference component (see <a href=
"#Binding_Fault_Reference_details"> 2.11.1 2.12.1 The
Binding Fault Message Reference Component ) and the XML
Representation of the binding
element information
item (see <a
href="#Binding_Fault_Reference_XMLRep"> 2.11.2 2.12.2 XML
Representation of Binding Fault
Message Reference Component )
is as described in <a
href="#tab_Binding_Fault_Reference_Mapping"> Table 2-11 2-13 .
Property | Mapping |
---|---|
{message reference} label} | The actual value of the
messageReference messageLabel attribute information
item if any; otherwise the {message
label} property of the message with same {direction} from the
{message exchange pattern} of the Interface Operation component
being bound, provided there is exactly one such message; otherwise
empty. |
{direction} | If the [local name] of the element
information item is infault input then "in", else if the [local name]
of the element information item is outfault output then "out". |
A Service component describes a set of endpoints (see 2.13 2.14 Endpoint ) at which the single interface of the service is provided. The endpoints thus are in effect alternate places at which the service is provided.
Service Services are named constructs and can be referred to by QName (see 2.16 2.17 QName resolution ).
The properties of the Service component are as follows:
{name} An NCName as defined by [ XML Namespaces ].
{target namespace} A namespace name, as defined in [ XML Namespaces ].
{interface} An Interface component.
{endpoints} A set of Endpoint components.
For each Service component in the {services} property of a definitions container, the combination of {name} and {target namespace} properties MUST be unique.
<definitions> <service name="xs:NCName" interface="<em>xs:QName</em>" interface="xs:QName" > <documentation />? <endpoint />+ </service> </definitions>
The XML representation for a Service component is an element information item with the following Infoset properties:
A [local name] of service
A [namespace name] of "http://www.w3.org/2003/11/wsdl" "http://www.w3.org/2004/03/wsdl"
Two or more attribute information item s amongst its [attributes] as follows:
A REQUIRED name
attribute information item
as described below in 2.12.2.1
2.13.2.1 name attribute information
item with service [owner] .
A REQUIRED interface
attribute information
item as described below in 2.12.2.2 2.13.2.2
interface attribute information item with service [owner]
.
Zero or more namespace qualified attribute information item s. The [namespace name] of such attribute information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
One or more element information item amongst its [children], in order, as follows:
An OPTIONAL documentation
element information
item (see 5.
Documentation ).
One or more element information item s from among the following, in any order:
One or more endpoint
element information
item s (see 2.13.2 2.14.2 XML
Representation of Endpoint Component
Zero or more namespace-qualified element information item s amongst its [children]. The [namespace name] of such element information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
Note that the XML Schema [
XML Schema:
Structures ] type of
the element information
item service
as defined in the WSDL schema MAY be used as
the basis for defining new elements which can be used as service
references in message exchanges. To enable such reuse, the WSDL
schema defines the attribute
information item name
as optional in
the type of the element
information item service
, while it
is REQUIRED for the element
information item service
as
indicated above.
Note:
See the primer [ WSDL 2.0 Primer ] for more information and examples.
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 .
interface
attribute information item with
service
[owner]The interface
attribute information item
identifies the interface that the service is an instantiation instance 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:QName. .
The mapping between the properties of the Service component (see
2.12.1
2.13.1 The Service Component
) and the XML Representation of the service
element information item (see 2.12.2
2.13.2 XML Representation of Service
Component ) is as described in Table 2-12
2-14 .
Property | Mapping |
---|---|
{name} | The actual value of the
name attribute information item |
{target namespace} | The actual value of the
targetNamespace attribute information item of
the [parent] definitions element information
item |
{interface} | The Interface component resolved to by
the actual value of the interface attribute
information item . |
{endpoints} | The Endpoint components corresponding
to the endpoint element information item s in
[children] if any. |
An Endpoint component defines the particulars of a specific endpoint at which a given service is available.
Endpoint components are local to a given Service component; they cannot be referred to by QName.
The properties of the Endpoint component are as follows:
{name} An NCName as defined by [ XML Namespaces ].
{binding} A named Binding component.
For each Endpoint component in the {endpoints} property of a Service component, the {binding} property (see 2.13.1 2.14.1 The Endpoint Component ) MUST either be a Binding component with an unspecified {interface} property (see 2.8.1 2.9.1 The Binding Component or a Binding component with an {interface} property equal to the {interface} property of the Service component.
For each Endpoint component in the {endpoints} property of a Service component component, the {name} property must MUST be unique.
<definitions> <service> <endpoint name="xs:NCName" binding="xs:QName" > <documentation />? </endpoint> </service> </service>+ </definitions>
The XML representation for a Endpoint component is an element information item with the following Infoset properties:
A [local name] of endpoint
.
A [namespace name] of "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
Two or more attribute information item s amongst its [attributes] as follows:
A REQUIRED name
attribute information item
as described below in 2.13.2.1 2.14.2.1
name attribute information item with endpoint [owner] .
A REQUIRED binding
attribute information
item as described below in 2.13.2.2 2.14.2.2
binding attribute information item with endpoint [owner]
.
Zero or more namespace qualified attribute information item s. The [namespace name] of such attribute information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
Zero or more element information item amongst its [children], in order, as follows:
An OPTIONAL documentation
element information
item (see 5.
Documentation ).
Zero or more namespace-qualified element information item s amongst its [children]. The [namespace name] of such element information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl". Such element information item s are considered to be endpoint extension elements (see 2.13.2.3 2.14.2.3 Endpoint extension elements ).
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 .
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 .
Endpoint extension elements are used to provide information specific to a particular endpoint in a server. The semantics of such element information item s are defined by the specification for those element information item s. Such specifications are expected to annotate the Endpoint component with additional properties and specify the mapping between those properties and the XML representation.
The mapping between the properties of the Endpoint component
(see 2.13.1 2.14.1 The
Endpoint Component ) and the XML Representation of the
endpoint
element information item (see
2.13.2
2.14.2 XML Representation of Endpoint
Component ) is as described in Table 2-13
2-15 .
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 . |
Two components of the same type are considered equivalent if if, for each property, the values of value in the properties of one first component are is the same as the values of the properties value in the second component.
With respect to top-level components (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 their {name} properties have the same value and the their {target namespace} properties have the same values then the two components are in fact, the same component.
This specification defines 3 three symbol spaces, one for each top-level component type (Interface, Binding and Service).
Within a symbol space space, all names, that is qualified names (that is, the combination of {name} and {target namespace} properties, 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 six other symbol spaces also exist, one for each of of: global element declarations, global attribute declarations, named model groups, named attribute groups, type definitions and key constraints, as defined by [ <a href="#XMLSchemaP1"> XML Schema: Structures ]. Other type systems may define additional symbol spaces.
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 contain a component with the required QName then the reference is a broken reference, it cannot reference. It is an error for a Definitions component to have such broken references.
This specification uses absolute URIs to identify several components (for example, features and properties) and components characteristics (for example, operation message exchange patterns and styles). When such absolute URIs are being compared to determine equivalency (see 2.15 Equivalence of Components ) the URIs MUST be resolved. compared character-by-character as indicated in [ TAG URI FINDING ].
<definitions> <types> <documentation />? [extension elements]* </types> </definitions>
At the abstract level, the deleted
text: {type definitions} and
{element declarations} properties
property of 2.1.1 The Definitions Component
are collections is a collection of imported and embedded schema
components. By design, WSDL supports any schema language for which
the syntax and semantics of import (i.e.,
the ability to import some schema by reference) or embed
(i.e., the ability to embed a schema
directly into another document) have been defined.
Support for However, only the deleted text: W3C
XML Schema Description Language [
<cite> <a href="#XMLSchemaP1"> XML Schema: Structures
</a> </cite> ],[ <cite> <a
href="#XMLSchemaP2"> XML Schema: Datatypes </a>
</cite> ] implementation
is required of all processors.
defined in this specification.
Instances of WSDL may (i.e., WSDL documents) 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 item s
may be regarded as having this attribute information item
set). Only
Note:
Support for the W3C XML Schema implementation Description Language [ XML Schema: Structures ],[ XML Schema: Datatypes ] is defined in this specification. required of all processors.
The schema components contained in the deleted text: {type
definitions} and {element declarations} properties of
<a href=
"#Definitions_details"> 2.1.1 The Definitions Component
provide the type system used for Message Reference and Interface Fault deleted
text: Reference components.
Message Reference components indicate their structure and content
by using the standard attribute information item s
message element
, or for alternate schema
languages in which these concepts do not map well, by using
alternative attribute information item extensions.
Interface Fault deleted text: Reference components behave similarly. 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/11/wsdl". "http://www.w3.org/2004/03/wsdl".
Zero or more namespace qualified attribute information item s in its [attributes] property. The [namespace name] property of such attribute information item s MUST NOT be http://www.w3.org/2003/11/wsdl http://www.w3.org/2004/03/wsdl
Zero or more element information item s amongst its [children] as follows:
An OPTIONAL documentation
element information
item (see 5.
Documentation ) in its [children] property.
Zero or more element information item s from among the following, in any order:
xs:import
element information item s
xs:schema
element information item s
Other namespace qualified element information item s whose namespace is NOT http://www.w3.org/2003/11/wsdl http://www.w3.org/2004/03/wsdl
XML Schema MAY be used as the schema language, language
via import or embedding. Each method defines a different
element information item for use
within a types
element information item .
All processors MUST support XML Schema type definitions.
Using the <code> xs:import
</code> and/or <code> xs:schema </code>
constructs is a necessary condition for making XML Schema
components available to a WSDL description. That is, a
A WSDL description cannot MUST NOT
refer to XML Schema components in a given namespace unless an
xs:import
and/or xs:schema
statement for
that namespace is present. That is, using
the xs:import
and/or xs:schema
constructs is a necessary condition for making XML
Schema components available to a WSDL description.
Importing an XML Schema uses the syntax
and semantics of the xs:import
mechanism
defined by XML Schema [ XML Schema:
Structures ],[ XML Schema:
Datatypes ], with deleted
text: its syntax and semantics,
plus some additional
restrictions. The schema components defined in the imported schema
are available for reference by QName (see <a href= "#qnameres"> 2.16 2.17 QName resolution ). Note that only
components defined in the schema itself and components included by
it via xs:include
are available to WSDL. Specifically 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 item s as follows:
A REQUIRED namespace
attribute information
item as described below.
An OPTIONAL schemaLocation
attribute
information item as described below.
namespace
attribute information
itemThe namespace
attribute information item
defines the namespace of the deleted
text: type definitions and
element declarations imported from the referenced schema. The
referenced schema MUST contain a targetNamespace
attribute information item on its xs:schema
element information item and the values of these two
attribute information item s MUST be identical. It is an
error to import a schema that does not have a
targetNamespace
attribute information item on
its xs:schema
element information item . Such
schemas must first be included (using xs:include
) in
a schema that contains a targetNamespace
attribute
information item on its xs:schema
element
information item , which can then be either imported or
inlined in the WSDL document.
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 .
schemaLocation
attribute information itemThe 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] which has no value.
The type of the schemaLocation
attribute
information item is xs:anyURI.
Embedding an XML schema uses the existing top-level
xs:schema
element information item </em>. defined
by XML Schema [ XML Schema: Structures ]. It may be viewed as simply cutting and pasting
an existing, stand-alone schema, to a location inside the types
element information item .
The schema components defined in the embedded schema are
available to WSDL for reference by QName (see 2.16 2.17 QName resolution ). Note that only
components defined in the schema itself and components included by
it via xs:include
are available to WSDL. Specifically
components that the schema imports via xs:import
are
NOT available to WSDL.
Similarly, components defined in an
embedded XML schema are NOT automatically made available to a WSDL
description that imported (using wsdl:import
) the
description that embeds the schema (see 4.2 Importing
Descriptions for more
details). For this reason, it is recommended that XML schema
documents intended to be shared across several WSDL descriptions be
placed in separate documents and imported using
xs:import
, rather than embedded inside a WSDL
document.
Inside an embedded XML schema, the
xs:import
and xs:include
element information item s MAY be used to refer to other XML schemas embedded in
the same WSDL description, provided that an appropriate value is
specified for their schemaLocation
attribute information item s. The semantics of such element information item s are governed solely by the XML Schema specification
[ XML
Schema: Structures ].
The xs:schema
element information item has
the following Infoset properties:
A [local name] of schema.
A [namespace name] of "http://www.w3.org/2001/XMLSchema".
A REQUIRED targetNamespace
attribute
information item , amongst its [attributes] as described
below.
Additional OPTIONAL attribute
information item s as specified for the xs:schema
element information item in
by the XML Schema specification.
Child Zero
or more child element information item s as
specified for the xs:schema
element information
item in by the XML Schema specification.
targetNamespace
attribute information
itemThe targetNamespace
attribute information
item defines the namespace of the deleted text: type
definitions and element declarations embedded in
this schema. its [owner] xs:schema
element information item . 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] which has no value.
The type of the targetNamespace
attribute
information item is xs:anyURI .
Whether embedded or imported, the element declarations present in a schema may be referenced from a Message Reference or Interface Fault deleted text: Reference component.
A named, global xs:element
declaration may be
referenced from the message
element
attribute
information item of an input
or ,
output
or
fault
element
information item . The QName is constructed from the
targetNamespace
of the schema and the content value of
the name
attribute information item of the
xs:element
element information item .
A An
message element
attribute information
item may not MUST NOT refer to deleted text: an
<code> xs:simpleType </code> or an <code>
xs:complexType </code> <em> element information item
</em>. </p> <p> Similarly, a deleted text: named, global xs:simpleType
or
xs:complexType
definition may
be referenced by QName. The QName is constructed from the
<code> targetNamespace </code> of the schema and the
content of the <code> name </code> <em> attribute
information item </em> of the <code> xs:simpleType
</code> or <code> xsd:complexType </code>
<em> element information item </em>.
definition.
Since it is unreasonable to expect that a single schema language
can be used to describe all possible Message Reference and Fault
deleted text: Reference component content contents
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 Reference and Interface
Fault deleted text: Reference components. 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 the declaration
of an element information item </em> 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 (and
extensibility attributes) to hold the components of the
referenced type system. It is expected that additional
extensibility attributes for Message Reference and Interface Fault deleted
text: Reference components
will also be defined, along with a mechanism for resolving the
values of those attributes to a particular imported type system
component.
See D. E. Examples of
Specifications of Extension Elements for Alternative Schema
Language Support. for examples of using other schema
languages. These example examples reuse the {element declarations}
and {type definitions} properties
property of 2.1.1 The Definitions Component
and the deleted text:
type </code> and <code>
element
attribute information item s of
the wsdl:part wsdl:input
.
, wsdl:output
and wsdl:fault
element information item s.
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.
<definitions> <include location="xs:anyURI" > <documentation />? </include> </definitions>
The WSDL include
element information item
allows for the separation of different components of a service
definition, from belonging 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 Specifically, it can be used to include
components from WSDL descriptions that share a target namespace
with the including description. Components in directly included descriptions are become part of
the component model of the including description. Directly included means that component inclusion is not
transitive; components included by one of the included documents
are not available to the original including document unless the
are included directly by that document. 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) "chameleon
includes") never occur in WSDL.
A mutual include is direct inclusion by one WSDL document of another WSDL document which includes the first. A circular include achieves the same effect with greater indirection (WSDL A includes WSDL B includes WSDL A, for instance). Multiple inclusion of a single WSDL document resolves to a single set of components. Mutual, multiple, and circular includes are explicitly permitted, and do not represent multiple redefinitions of the same components. Multiple inclusion of a single WSDL document has the same meaning as including it only once. Processors are encouraged to keep track of the source of component definitions, so that multiple, mutual, and circular includes do not require establishing identity on a component-by-component basis.
The include
element information item
has:
A [local name] of include
.
A [namespace name] of "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
One or more attribute information item s amongst its [attributes] as follows:
A REQUIRED location
attribute information
item as described below in 4.1.1 location attribute
information item with include [owner] .
Zero or more namespace qualified attribute information item s. The [namespace name] of such attribute information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
Zero or more element information item amongst its [children], as follows:
An optional documentation
element information
item (see 5.
Documentation ).
Zero or more namespace-qualified element information item s amongst its [children]. The [namespace name] of such element information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
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 about the namespace identified by the
targetNamespace
attribute information item of
the containing definitions
element information
item .
If the URI indicated by
location
is not dereferenceable or does not resolve to a WSDL
document then the processor MUST fail immediately. That is,
include
elements MUST be processed immediately by WSDL
processors.
The actual value of the targetNamespace
attribute information item of the included WSDL document
MUST match the actual value of the targetNamespace
attribute information item of the definitions
element information item which is the [parent] of the
include
element information item .
<definitions> <import namespace="xs:anyURI" location="xs:anyURI"? > <documentation />? </import> </definitions>
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, descriptions by separation separating 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 Specifically, it can be used to import components
from WSDL descriptions that do not share a target namespace with
the importing document. Components in directly imported descriptions are part of
the component model of the importing description. Directly imported means that component importation is
not transitive; components imported by one of the imported
documents are not
available to the original importing document
unless the are imported directly by that document. 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 MUST NOT
refer to components in a namespace other that than the
target namespace unless an import statement for that namespace is
present. The same considerations apply to
schemas embedded in an imported WSDL description (see
3.1.2 Embedding XML
Schema ). More explicitely,
components defined by an XML schema document embedded inside an
imported WSDL description are NOT made available to the importer
unless the latter contains an explicit xs:import
statement
to that purpose.
This specification DOES NOT preclude
repeating the import
element
information item for the same
value of the namespace
attribute information item as long as they provide different values for the
location
attribute information item
.Repeating the import
element
information item for the
same namespace
value MAY be used as a way to provide
alternate locations to find information about a given
namespace.
Furthermore, this specification DOES NOT
require the location
attribute information item to be dereferenceable. If it is not dereferenceable then
no information about the imported namespace is provided by
that import
element information item
.It is possible that such lack of
information results in QNames in other parts of a WSDL Definitions
component to become broken references (see 2.17 QName
resolution ). Such broken
references are not errors of the imports
element
information item but rather
QName resolution errors which must be detected as described
in 2.17 QName
resolution .
The import
element information item has
the following Infoset properties:
A [local name] of import
.
A [namespace name] of "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
Two or more attribute information item s amongst its [attributes] as follows:
A REQUIRED namespace
attribute information
item as described below in 4.2.1 namespace attribute
information item .
An OPTIONAL location
attribute information
item as described below in 4.2.2 location attribute
information item with import [owner] .
Zero or more namespace qualified attribute information item s. The [namespace name] of such attribute information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
Zero or more element information item amongst its [children], as follows:
An optional documentation
element information
item (see 5.
Documentation ).
Zero or more namespace-qualified element information item s amongst its [children]. The [namespace name] of such element information item s MUST NOT be "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
namespace
attribute information itemThe namespace
attribute information item
has the following Infoset properties:
A [local name] of namespace
.
A [namespace name] which has no value.
The namespace
attribute information item
is of type xs:anyURI
. Its actual value indicates that
the containing WSDL document MAY contain qualified references to
WSDL definitions in that namespace (via one or more prefixes
declared with namespace declarations in the normal way). This value
MUST NOT match the actual value of the enclosing WSDL document
targetNamespace
attribute information item .
If the import statement results in the import of a WSDL document
then the actual value of the namespace
attribute
information item MUST be identical to the actual value of the
imported WSDL document's targetNamespace
attribute
information item .
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 about the namespace identified by the
namespace
attribute information item .
The location
attribute information item is
optional to allow optional. This allows WSDL components to be
constructed from information other than serialized XML 1.0 and to allow for 1.0.
It also allows the development of WSDL processors that have
a priori (i.e., built-in)
knowledge of certain namespaces.
<documentation> [extension elements]* </documentation>
WSDL uses the optional documentation
element
information item as a container for human readable and/or
machine processable documentation. The content of the element
information item is arbitrary character information
items and element information item s ("mixed"
content 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/11/wsdl". "http://www.w3.org/2004/03/wsdl".
Zero or more attribute information item s in its [attributes] property.
Zero or more child element information item s in its [children] property.
Zero or more character information item s in its [children] property.
The schema for WSDL has a two-part extensibility model based on namespace-qualified elements and attributes. The extension is identified by the qname consisting of its namespace URI and its element name. The meaning of the extension SHOULD be defined (directly or indirectly) in a document that is available at its namespace URI.
WSDL allows extensions to be defined in terms of element information item s. Where indicated herein, WSDL allows namespace-qualified element information item s whose [namespace name] is NOT "http://www.w3.org/2003/11/wsdl" "http://www.w3.org/2004/03/wsdl" to appear as a child among the [children] of specific element information item s whose namespace name IS "http://www.w3.org/2003/11/wsdl". [namespace name] is "http://www.w3.org/2004/03/wsdl". Such element information item s can MAY be used to annotate WSDL constructs such as interface, operation, etc.
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 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.
deleted text: <p> An extension element is said to be <em> processed </em> if a WSDL processor decides (through whatever means) that its parent (an <em> element information item </em> in the "http://www.w3.org/2003/11/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. </p>Example 6-1. Base type for extensibility elements
<xs:complexType name='ExtensibilityElement' abstract='true' > <xs:attribute ref='wsdl:required' use='optional' /> </xs:complexType>
Extension elements can be marked as mandatory by annotating them
with a wsdl:required
attribute information
item (see 6.1.2 required attribute
information item ) with a value of "true". Mandatory extensions are those A mandatory extension is an extension that
MUST be processed correctly
MAY change the meaning of the element to
which it is attached, such that the meaning of that element is no
longer governed by this
specification. Instead, the WSDL
processor. If meaning of an element
containing a mandatory extension deleted text: element is processed, governed
by the WSDL processor MUST either
agree meaning of that extension.
Thus, the definition of the element's meaning is
delegated to deleted text: fully
abide by all the rules and semantics
signaled by specification that
defines the extension.
An extension element's qualified name, or immediate cease processing (fault). In particular, if that is NOT marked as mandatory MUST NOT invalidate the meaning of any part of the WSDL processor document. Thus, a NON-mandatory extension merely provides additional description of capabilities of the service. Furthermore, any extension that is NOT marked as mandatory and which is NOT understood, MUST be ignored. Any NOT understood extension attributes MUST be ignored as this specification does not recognize provide a mechanism to mark extension attributes as being required.
Note:
A mandatory extension is considered mandatory because it has the qualified name ability to change the meaning of the extension element, element to which it MUST fault. If is attached. Thus, the WSDL processor recognizes meaning of the qualified name, and determines that element may not be fully understood without understanding the attached extension. A NON-mandatory extension, on the deleted text: extension in question is incompatible with any other aspect hand, can be safely ignored without danger of misunderstanding the document (including other required extensions), it MUST fault. rest of the WSDL document.
required
attribute information itemWSDL provides a global attribute information item with the following Infoset properties:
A [local name] of required
.
A [namespace name] of "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl".
A [specified] property with a value of "true".
The type of the required
attribute information item is
xs:boolean .
WSDL allows qualified attribute information item s whose [namespace name] is NOT "http://www.w3.org/2003/11/wsdl" "http://www.w3.org/2004/03/wsdl" to appear on any element information item whose namespace name IS "http://www.w3.org/2003/11/wsdl". "http://www.w3.org/2004/03/wsdl". Such attribute information item s can be used to annotate WSDL constructs such as interfaces, bindings, etc.
WSDL does not provide a mechanism for marking extension attribute information item s as mandatory.
As indicated above, it is expected that the presence of extensibility elements and attributes will result in additional properties appearing in the component model.
The presence of an optional extensibility element or attribute MAY therefore augment the semantics of a WSDL document in ways that do not invalidate the existing semantics. However, the presence of a mandatory extensibility element MAY alter the semantics of a WSDL document in ways that invalidate the existing semantics.
Note:
Authors of extensibility elements should avoid altering the existing semantics in ways that are likely to confuse users.
As an XML vocabulary, WSDL documents or fragments or references to WSDL components (via QNames) MAY appear within other XML documents. In such scenarios it could be necessary to provide some hints on where additional WSDL information for a given namespace can be found in order to help with QName resolution 2.17 QName resolution .
This specification defines a global
attribute, wsdlLocation
in the
namespace "http://www.w3.org/2004/03/wsdl-instance" for this
purpose (hereafter referred to as "wsdli:wsdlLocation"). This
global attribute MAY appear on any XML element which allows
attributes from other namespaces to occur. It MUST NOT appear on
a wsdl:definitions
element or any of its children/descendants.
wsdli:wsdlLocation
attribute information
itemWSDL provides a global attribute information item with the following Infoset properties:
A [local name] of
wsdlLocation
.
A [namespace name] of "http://www.w3.org/2004/03/wsdl-instance".
The type of the wsdlLocation
attribute information item is a list xs:anyURI .Its actual
value MUST be a list of pairs of URIs; where the first URI of a
pair, which MUST be an absolute URI as defined in [
IETF RFC
2396 ], indicates a WSDL
namespace name, and, the second a hint as to the location of a WSDL
document defining WSDL components for that namespace name. The
second URI of a pair MAY be abolute or relative.
An element information item whose namespace name is "http://www.w3.org/2004/03/wsdl"
and whose local part is definitions
conforms to this specification if conforms to the XML
Schema for that element as defined by this specification family and
additionally adheres to all the constraints contained in this
specification.
This specification conforms to the [ XML Information Set ]. The following information items MUST be present in the input infosets to enable correct processing of WSDL documents:
Document Information Items with children and base URI properties.
Element Information Items with namespace name ,local name ,children ,attributes ,base URI and parent properties.
Attribute Information Items with namespace name ,local name and normalized value properties.
Character Information Items with character code ,element content whitespace and parent properties.
This section defines a class of conformant WSDL processors that are intended to act on behalf of a party that wishes to make use of a Web service (i.e., the requester entity or requester agent), rather than the party that implements the Web service (i.e., the provider entity or provider agent).
An extension element is said to be processed if the WSDL processor decides (through whatever means) that its parent (an element information item in the "http://www.w3.org/2004/03/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 ignore bindings.
A conformant WSDL processor MUST adhere to the following rules:
Except as noted below for mandatory extensions, a conformant WSDL processor MUST accept any legal WSDL document as defined by this specification.
A conformant WSDL processor MUST fault if a portion of a WSDL document is illegal according to this specification and the WSDL processor attempts to process that portion.
A conformant WSDL processor MUST support at least XML Schema as a type system language.
A conformant WSDL processor MUST fail if it processes an element containing a wsdl:include statement having a URI that is not dereferenceable to a legal WSDL document.
If a mandatory extension (i.e., a mandatory element, feature or property) is processed, a conformant WSDL processor MUST either agree to fully abide by all the rules and semantics signaled by that extension, or immediately cease processing (fault). In particular, if the WSDL processor does not recognize the extension, it MUST fault. If the WSDL processor recognizes the extension, and determines that the extension in question is incompatible with any other aspect of the document (including other required extensions), it MUST fault.
A conformant WSDL processor MAY safely ignore a NON-mandatory extension that it does not recognize or that it does not choose to implement.
<definitions targetNamespace="xs:anyURI" >
<documentation />?
<import namespace="xs:anyURI" location="xs:anyURI"? >
<documentation />?
</import>*
<include location="xs:anyURI" >
<documentation />?
</include>*
<types>
<documentation />?
</types>
<interface name="xs:NCName" extends="list of xs:QName"? styleDefault="xs:anyURI"? >
<documentation />?
<fault name="xs:NCName" element="xs:QName"? >
<documentation />?
</fault>*
<operation name="xs:NCName" pattern="xs:anyURI" style="xs:anyURI"? safe="xs:boolean"? >
<documentation />?
<input messageLabel="xs:NCName"? element="union of xs:QName, xs:Token"? >
<documentation />?
</input>*
<output messageLabel="xs:NCName"? element="union of xs:QName, xs:Token"? >
<documentation />?
</output>*
<infault ref="xs:QName" messageLabel="xs:NCName"? >
<documentation />?
</infault>*
<outfault ref="xs:QName" messageLabel="xs:NCName"? >
<documentation />?
</outfault>*
<feature ... />*
<property ... />*
</operation>*
<feature uri="xs:anyURI" required="xs:boolean"? >
<documentation />?
</feature>*
<property uri="xs:anyURI" required="xs:boolean"? >
<documentation />?
<value> xs:anyType </value>?
<constraint> xs:QName </constraint>?
</property>*
</interface>*
<binding name="xs:NCName" interface="xs:QName"? >
<documentation />?
<fault ref="xs:QName" >
<documentation />?
</fault>*
<operation ref="xs:QName" >
<documentation />?
<input messageLabel="xs:NCName"? >
<documentation />?
</input>*
<output messageLabel="xs:NCName"? >
<documentation />?
</output>*
<feature ... />*
<property ... />*
</operation>*
<feature ... />*
<property ... />*
</binding>*
<service name="xs:NCName" interface="xs:QName"
<documentation />?
<endpoint name="xs:NCName" binding="xs:QName" >
<documentation />?
</endpoint>*
</service>*
</definitions>
Editorial note: JJM | 20021107 |
This was lifted from the SOAP 1.2 specification, and needs to be edited to reflect WSDL's own requirements. For example, the WG has not reached consensus on whether to use "text/xml", "text/wsdl+xml" or "application/wsdl+xml". |
This appendix defines the "application/wsdl+xml" media type which can be used to describe WSDL 2.0 documents serialized as XML. It is referenced by the corresponding IANA registration document [ WSDL MediaType ].
application
wsdl+xml
none
This parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in [ RFC 3023 ].
Identical to those of "application/xml" as described in [ RFC 3023 ], section 3.2, as applied to the WSDL document infoset.
See section A.2 Security considerations .
There are no known interoperability issues.
This document and [ WSDL 2.0 Bindings ].
No known applications currently use this media type.
WSDL documents are not required or expected to be stored as files.
Either a syntax identical to that of "application/xml" as described in [ RFC 3023 ], section 5 or the syntax defined in [ WSDL 2.0 RDF Mapping ].
As specified in [ RFC 3023 ], section 6.
TEXT
@@@ <@@@@>
COMMON
The WSDL 2.0 specification set is a work product of the World Wide Web Consortium's Web Service Description Working Group . The W3C has change control over these specifications.
Editorial note: JJM | 20021107 |
Are there any security considerations other than the standard ones. |
This media type uses the "+xml" convention, it shares the same security considerations as described in [ RFC 3023 ], section 10.
This document is the work of the W3C Web Service Description Working Group. Group .
Members of the Working Group are (at the time of writing, and by alphabetical order): Adi Sakala (IONA Technologies), Alan Davies (SeeBeyond), Mike Ballantyne (Electronic Data Systems), David Booth (W3C), Allen Brookes (Rogue Wave Softwave), Amelia Lewis (TIBCO/Extensibility), Arthur Ryman (IBM), Bijan Parsia (University of Maryland), Dale Moberg (Cyclone Commerce), Dan Kulp (IONA Technologies), David Booth (W3C), Dietmar Gaertner (Software AG), Don Mullen (TIBCO Software), Erik Ackerman (Lexmark), Roberto Chinnici (Sun Microsystems), Glen Daniels (Macromedia), Igor Sedukhin (Computer Associates), Ingo Melzer (DaimlerChrysler Research and Technology), Jacek Kopecky (Systinet), Jean-Jacques Moreau (Sonic Software), Alan Davies (SeeBeyond), Mike Davoren (W. W. Grainger), Paul Downey (British Telecommunications), Youenn Fablet (Canon), Jeff Mischkinsky (Oracle Corporation), Jeffrey Schlimmer Yaron Goland (BEA), Martin Gudgin (Microsoft Corporation), Jerry Thrasher (Lexmark), Jim Hendler (University of Maryland), Jonathan Marsh ( <em> Chair </em>, Microsoft Hugo Haas (W3C), Hao He (The Thomson Corporation), Tom Jordahl (Macromedia), Jacek Kopecky (Systinet), Dan Kulp (IONA Technologies), Sandeep Kumar (Cisco Systems), Amelia Lewis (TIBCO Software, Inc.), Kevin Canyang Liu (SAP), deleted text: Lily Liu (webMethods, Inc.), Martin Gudgin (Microsoft Corporation), Michael Champion (Software AG), Michael Mahan (Nokia), Michael Mealling (Verisign), Mike Ballantyne (Electronic Data Systems), Mike Davoren (W. W. Grainger), Jonathan Marsh (Microsoft Corporation), Mike McHugh (W. W. Grainger), Paul Downey (BT), Philippe Le Hégaret (W3C), Prasad Yendluri (webMethods, Inc.), Roberto Chinnici (Sun Microsystems), Sandeep Kumar (Cisco Systems), Sanjiva Weerawarana (IBM), Steve Graham (Global Grid Forum), Steve Tuecke (Global Grid Forum), Tom Jordahl (Macromedia), Umit Yalcinalp Michael Mealling (Verisign), Ingor Melzer (DaimlerChrysler Research and Technology), Jeff Mischkinsky (Oracle Corporation), Dale Moberg (Cyclone Commerce), Jean-Jacques Moreau (Canon), David Orchard (BEA), Bijan Parsia (University of Maryland), Arthur Ryman (IBM), Waqar Sadiq (Electronic Data Systems), Adi Sakala (IONA Technologies), Jeffrey Schlimmer (Microsoft Corporation), Igor Sedukhin (Computer Associates), Sandra Swearingen (U.S. Department of Defense, U.S. Air Force), Bryan Thompson (Hicks & Associates), Jerry Thrasher (Lexmark), William Vambenepe (Hewlett-Packard Company), Youenn Fablet (Canon) Asir Vedamuthu (webMethods, Inc.), Sanjiva Weerawarana (IBM), Ümit Yalçınalp (Oracle Corporation), Prasad Yendluri (webMethods, Inc.).
Previous members were: Aaron Skonnard (DevelopMentor), Jochen Ruetschlin (DaimlerChrysler Research and Technology), Keith Ballinger (Microsoft), Krishna Sankar (Cisco Systems), Mario Jeckle (DaimlerChrysler Research and Technology), Pallavi Malu (Intel Corporation), Lily Liu (webMethods, Inc.), Don Wright (Lexmark), Joyce Yang (Oracle Corporation), Daniel Schutzer (Citigroup), Dave Solo (Citigroup), Stefano Pogliani (Sun Microsystems), William Stumbo (Xerox), Stephen White (SeeBeyond), Barbara Zengler (DaimlerChrysler Research and Technology), Tim Finin (University of Maryland) Maryland), Laurent De Teneuille (L'Échangeur), (L'Echangeur), Johan Pauhlsson (L'Échangeur), (L'Echangeur), Mark Jones (AT&T), Steve Lind (AT&T), Sandra Swearingen (U.S. Department Philippe Le Hégaret (W3C), Jim Hendler (University of Defense, U.S. Air Force) Maryland), Dietmar Gaertner (Software AG), Michael Champion (Software AG), Don Mullen (TIBCO Software, Inc.), Steve Graham (Global Grid Forum), Steve Tuecke (Global Grid Forum).
The people who have contributed to discussions on deleted text: <a href= "mailto:www-ws-desc@w3.org"> www-ws-desc@w3.org are also gratefully acknowledged.
This appendix provides a syntax for URI references for named components found in a WSDL document. This includes the top level components: interface, binding and service and the subordinate components: operation, fault, and endpoint. The URI references are easy to understand and compare, while imposing no burden on the WSDL author.
There are two main cases for WSDL URIs:
the URI of a WSDL document
the URI of a WSDL namespace
The URI of a WSDL document can be dereferenced to give a resource representation that contributes component definitions to a single WSDL namespace. If the media type is set to the WSDL media type, then the fragment identifiers can be used to identify the main components that are defined in the document.
However, in keeping with the recommendation in 2.1.1 The Definitions Component that the namespace URI be dereferencible to a WSDL document, this appendix specifies the use of the namespace URI with the WSDL fragment identifiers to form a URI-reference.
The following fragment identifier syntax is compliant with the [ XPointer Framework ].
The URI in a URI-reference for a WSDL component is the {target namespace} property of either the component itself, in the case of interfaces, bindings, and services, or the {target namespace} property of an ancestor component. The URI provided by the {target namespace} property is combined with a fragment identifier, where the fragment identifier is constructed from the {name} property of the component and the {name} properties of its ancestors as a path according to Table C-1 .In that table the first column gives the name of the WSDL component as the [local name] of the element information item that represents that construct in a WSDL document. Columns two and three populate the variables x and y respectively. These variables are then used to construct the fragment in column four.
Construct | x | y | Fragment |
---|---|---|---|
interface | {name} property of interface | n/a | interface(x) |
operation | {name} property of operation | {name} property of parent interface | operation(y/x) |
fault | {name} property of fault | {name} property of parent interface | fault(y/x) |
binding | {name} property of binding | n/a | binding(x) |
service | {name} property of service | n/a | service(x) |
endpoint | {name} property of endpoint | {name} property of parent service | endpoint(y/x) |
Note that the above rules are defined in terms of component properties rather the XML Infoset representation of the component model.
WSDL has an open content model. It is therefore possible for an extension to define new components. The XPointer Framework scheme for components added by extensions is:
extension(extension-namespace,
extension-specific-syntax)
where extension-namespace is the namespace that identifies the extension, e.g. for SOAP the namespace is http://www.w3.org/2003/06/wsdl/soap12, and extension-specific-syntax is defined by the extension. The owner of the extension must define any components contributed by the extension and a syntax for identifying them.
Consider the following WSDL located at http://example.org/TicketAgent.wsdl:
Example C-1. URI References - Example WSDL
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions
targetNamespace="http://example.org/TicketAgent.wsdl20"
xmlns:xsTicketAgent="http://example.org/TicketAgent.xsd"
xmlns:wsdl="http://www.w3.org/2004/03/wsdl"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.w3.org/2004/03/wsdl wsdl20.xsd">
<wsdl:types>
<xs:import schemaLocation="TicketAgent.xsd"
namespace="http://example.org/TicketAgent.xsd" />
</wsdl:types>
<wsdl:interface name="TicketAgent">
<wsdl:operation name="listFlights" pattern="http://www.w3.org/@@@@/@@/wsdl/in-out">
<wsdl:input element="xsTicketAgent:listFlightsRequest"/>
<wsdl:output element="xsTicketAgent:listFlightsResponse"/>
</wsdl:operation>
<wsdl:operation name="reserveFlight" pattern="http://www.w3.org/@@@@/@@/wsdl/in-out">
<wsdl:input element="xsTicketAgent:reserveFlightRequest"/>
<wsdl:output element="xsTicketAgent:reserveFlightResponse"/>
</wsdl:operation>
</wsdl:interface>
</wsdl:definitions>
Its conceptual elements have the following URI-references:
This section will attempt to document some of the migration concerns of going from WSDL 1.1 to WSDL 2.0. We do not claim that all migration problems will be addressed here.
A DTD may be used as the schema language for WSDL. It may not be
embedded; it must be imported. A namespace must be assigned. DTD
types appear in the {element declarations} property of 2.1.1 The Definitions Component
and may be referenced from the
wsdl:part wsdl:input
only
by , wsdl:output
and wsdl:fault
elements
using the element
attribute information
item </em> ; DTDs do not have a
construct corresponding to the contents of the {type definitions}
property of the <a href= "#Definitions_details"> <b>
2.1.1 The Definitions Component </b> </a>.
.
The prefix, dtd, used throughout the following is mapped to the namespace URI "http://www.example.org/dtd/".
The dtd:import
element information item
references an external Document Type Definition, and has the
following infoset properties:
A [local name] of import.
A [namespace name] of "http://www.example.org/dtd".
One or two attribute information item s, as follows:
A REQUIRED namespace
attribute information
item as described below.
An OPTIONAL location
attribute information
item as described below.
namespace
attribute
information itemThe namespace
attribute information item
sets the namespace to be used with all imported element definitions
described in the DTD. It 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 .
The WSDL author should ensure that a prefix is associated with the namespace at the proper scope (probably document scope).
location
attribute
information itemThe location
attribute information item ,
if present, provides a hint to the processor as to where the DTD
may be located. Caching and cataloging technologies may provide
better information than this hint. The location
attribute information item has the following infoset
properties:
A [local name] of location.
A [namespace name] which has no value.
The type of the location
attribute information
item is xs:anyURI .
The message element
attribute information
item MUST be used when referring to an element definition
(<!ELEMENT>) from a Message Reference; Reference
component; referring to an element definition from a
Interface Fault deleted text: Reference component is similar. The value of the
element definition MUST correspond to the content of the
namespace
attribute information item of the
dtd:import
element information item . The
local name part must correspond to an element defined in the
DTD.
Note that this pattern does not attempt to make DTDs namespace-aware. It applies namespaces externally, in the import phase.
A RELAX NG schema may be used as the schema language for WSDL.
It may be embedded or imported; import is preferred. A namespace
must be specified; if an imported schema specifies one, then the
[actual value] of the namespace
attribute
information item in the import
element
information item must match the specified namespace. RELAX NG
provides both type definitions and
element definitions which appear
declarations, the latter appears in
the deleted text: {type definitions} and {element declarations}
properties property of <a
href="#Definitions_details"> 2.1.1 The Definitions Component
respectively. The following discussion supplies the prefix rng
which is mapped to the URI
"http://www.relaxng.org/ns/structure/1.0".
Importing a RELAX NG schema uses the rng:include mechanism
defined by RNG, with restrictions on its syntax and semantics. A
child element information item of the types
element information item is defined with the Infoset
properties as follows:
A [local name] of include.
A [namespace name] of "http://www.relaxng.org/ns/structure/1.0".
Two attribute information item s as follows:
A REQUIRED ns
attribute information item
as described below.
An OPTIONAL href
attribute information
item as described below.
Additional attribute information item s as defined by the RNG specification.
Note that WSDL restricts the rng:include
element information item to be empty. That is, it cannot
redefine rng:start
and rng:define
element information item s; it may be used solely to
import a schema.
ns
attribute information
itemThe ns
attribute information item defines
the namespace of the type and element definitions imported from the
referenced schema. If the referenced schema contains an
ns
attribute information item on its
grammar
element information item , then the
values of these two attribute information item s must be
identical. If the imported grammar does not have an ns
attribute information item then the namespace specified
here is applied to all components of the schema as if it did
contain such an attribute information item . The
ns
attribute information item contains the
following Infoset properties:
A [local name] of ns.
A [namespace name] which has no value.
The type of the ns
attribute information
item is xs:anyURI .
href
attribute
information itemThe href
attribute information item must
be present, according to the rules of the RNG specification.
However, WSDL allows it to be empty, and considers it only a hint.
Caching and cataloging technologies may provide better information
that this hint. The href
attribute information
item has the following Infoset properties:
A [local name] of href.
A [namespace name] which has no value.
The type of the href
attribute information
item is xs:anyURI .
Embedding an RNG schema uses the existing top-level
rng:grammar
element information item . It may
be viewed as simply cutting and pasting an existing, stand-alone
schema to a location inside the wsdl:types
element
information item . The rng:grammar
element
information item has the following Infoset properties:
A [local name] of grammar.
A [namespace name] of "http://www.relaxng.org/ns/structure/1.0".
A REQUIRED ns
attribute information item s
as described below.
Additional attribute information item s as specified
for the rng:grammar
element information item
in the RNG specification.
Child element information item s as specified for the
rng:grammar
element information item in the
RNG specification.
ns
attribute information
itemThe ns
attribute information item defines
the namespace of the type and element definitions embedded in this
schema. WSDL modifies the RNG definition of the
rng:grammar
element information item to make
this attribute information item required. The
ns
attribute information item has the
following infoset properties:
A [local name] of ns.
A [namespace name] which has no value.
The type of the ns
attribute information
item is xs:anyURI .
Whether embedded or imported, the element definitions present in a schema may be referenced from a Message Reference or Interface Fault deleted text: Reference component.
A named rng:define definition MUST NOT be referenced from the Message Reference or Interface Fault deleted text: Reference components.
A named Relax NG element declaration MAY be referenced from a
Message Reference or Interface Fault
deleted text: Reference component. The QName is constructed
from the namespace ( ns
attribute information
item ) of the schema and the content of the name
attribute information item of the element
element information item An element
attribute information item MUST NOT be used to refer to an
rng:define
element information item .
Date | Author | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
20040323 | JJM | Commented out the (missing) property example. | ||||||||||||
20040322 | RRC | Added definition of wsdli:wsdlLocation attribute. | ||||||||||||
20040322 | JJM | Added faults to properties and features. | ||||||||||||
20040319 | JJM | Use lowercase "should" in notes. | ||||||||||||
20040319 | JJM | Comment out features at service level. Uniformize scope between features and properties. | ||||||||||||
20040318 | JJM | Moved normative notes into the main body of the document. | ||||||||||||
20040318 | JJM | Incorporated the property text from Glen. | ||||||||||||
20040318 | JJM | Addressed comments from Yuxiao Zhao. | ||||||||||||
20040318 | JJM | Updated the feature description, as per Glen and David Booth's suggestions. | ||||||||||||
20040317 | RRC | Removed redundant {styleDefault} property of the interface component. | ||||||||||||
20040317 | JJM | Include comments from Kevin. | ||||||||||||
20040315 | RRC | Added clarification on embedded XML schemas that refer to siblings. | ||||||||||||
20040315 | RRC | Updated RPC signature extension to use #in/#out/#inout/#return tokens. | ||||||||||||
20040315 | RRC | Added explanatory text to types and modularization sections per resolution of issue #102. | ||||||||||||
20040315 | SW | Change binding/{fault,operation}/@name to @ref | ||||||||||||
20040312 | RRC | Fixed appendix D to take the removal of wsdl:message into account. | ||||||||||||
20040312 | RRC | Added definition of wrpc:signature extension attribute. | ||||||||||||
20040311 | SW | Change fault stuff per decision to make faults first class in interfaces. | ||||||||||||
20040308 | SW | Renamed {message} property to {element} and @message to @element | ||||||||||||
20040305 | SW | Added {safety} property | ||||||||||||
20040227 | MJG | Merged in branch Issue143 containing resolution of issue 143 | ||||||||||||
20040227 | SW | Dropped {type definitions} property from definitions; leftover from <message> days. | ||||||||||||
20040226 | SW | Working thru various edtodo items. | ||||||||||||
20040106 | JS | Per 18 Dec 2003 telecon decision, added text re: circular includes. | ||||||||||||
20031204 | JS | Per 4 Dec 2003 telecon decision, removed redundant binding/operation/{infault, outfault}/@messageReference. | ||||||||||||
20031105 | JS | Added point to attributes task force recommendation accepted by the working group. | ||||||||||||
20031104 | JS | Mapping to component model for
{message} of Fault Reference component indicated that
message attribute information item was
optional, but the pseudo syntax and XML representation reprsentation indicated it was required. Made
uniformly optional to allow other type systems as was previously
done for {message} of Message Reference component. |
||||||||||||
20031104 | JS | Renamed interface /operation /{input,output} /@body to ./@message and interface /operation /{infault,outfault} /@details to ./@message per 4 Nov face-to-face decision. | ||||||||||||
20031104 | JS | Made interface /operation /{input,output,infault,outfault} /@messageReference optional per 4 Nov face-to-face decision. | ||||||||||||
20031104 | JS | Removed interface/operation/{input,output}/@header per 4 Nov face-to-face decision. | ||||||||||||
20031102 | SW | Updated fault reference components to indicate that if operation's MEP uses MTF then the fault is in the opposite direction as the referenced message and if it use FRM then its in the same direction. Per 10/30 telecon decision. | ||||||||||||
20031102 | SW | Updated operation styles terminology per message #57 of Oct. and the RPC style rules per message #58 of Oct. per decision on 10/30 telecon to consider those status quo. | ||||||||||||
20031102 | SW | Clarified wording in operation styles discussion to better explain the use of the {style} attribute. | ||||||||||||
20031102 | SW | Clarified wording in XML <-> component model mapping section for message reference components to say that {body} and {headers} may not have a value. | ||||||||||||
20031102 | SW | Made interface/operation/(input|output)/@messageReference REQUIRED per 10/30 telecon decision. | ||||||||||||
20031028 | SW | Renamed to wsdl20.xml and updated contents. | ||||||||||||
20031028 | SW | Updated bindings. | ||||||||||||
20031025 | SW | Updated faults. | ||||||||||||
20031013 | JJM | Moved appendix C to a separate document, as per 24 Sep 2003 meeting in Palo Alto, CA. | ||||||||||||
20031003 | SW | Softened <documentation> wording to allow machine processable documentation. | ||||||||||||
20031002 | SW | Changed binding/operation/@name to QName per edtodo. | ||||||||||||
20030930 | SW | Added placeholders for set-attr/get-attr operation styles. | ||||||||||||
20030929 | SW | Inserted Glen Daniels' feature text. | ||||||||||||
20030919 | RRC | Removed import facility for chameleon schemas and added a description of a workaround. | ||||||||||||
20030918 | JJM | Changed message pattern to message exchange pattern, as per WG resolution on 18 Sep. 2003 | ||||||||||||
20030916 | RRC | Added editorial note for the missing RPC encoding style. | ||||||||||||
20030915 | RRC | Yet more updates for REQUIRED, OPTIONAL; updated section 3 to reflect the removal of "wsdl:message". | ||||||||||||
20030911 | RRC | More updates for REQUIRED, OPTIONAL; removed diff markup; fixed example C.4. | ||||||||||||
20030911 | RRC | Renamed message reference "name" attribute and property to "messageReference"; fixed incorrect reference to "fault" element in the binding operation section. | ||||||||||||
20030910 | SW | Fixed message references and added proper use of REQUIRED etc. for the part I've gone through so far. | ||||||||||||
20030910 | SW | Updating spec; fixed up interface operation component more. | ||||||||||||
20030808 | JCS | Fixed errors found by IBM\Arthur. | ||||||||||||
20030804 | JCS | Removed Message component per 30 July-1 Aug meeting. | ||||||||||||
20030803 | JCS | Replaced substitution groups with xs:any namespace='##other' per 3 July, 17 July, and 24 July telecons. | ||||||||||||
20030801 | JCS | Made binding/@interface optional per 31 July meeting. | ||||||||||||
20030724 | JCS | Remove @targetResource per 17 July 2003 telecon. | ||||||||||||
20030612 | JJM | Incorporate revised targetResource definition, as per 12 June 2003 telcon. | ||||||||||||
20030606 | JJM | Refer to the two graphics by ID. Indicate pseudo-schemas are not normative. | ||||||||||||
20030604 | JJM | Fixed figures so they don't appear as tables. Fixed markup so it validates. | ||||||||||||
20030603 | JCS | Plugged in jmarsh auto-generated schema outlines | ||||||||||||
20030529 | MJG | Fixed various issues with the XmlRep portions of the spec | ||||||||||||
20030527 | MJG | Added text to 2.2.1 The Interface Component and 2.2.3 Mapping Interface's XML Representation to Component Properties indicating that recursive interface extension is not allowed. | ||||||||||||
20030523 | JJM | Added pseudo-syntax to all but Type and Modularizing sections. | ||||||||||||
20030523 | JJM | Added the "interface" and "targetResource" attribute on <service>. | ||||||||||||
20030523 | JJM | Fixed miscellaneous typos (semi-colon instead of colon, space after parenthesis, etc.). | ||||||||||||
20030523 | JJM | Rewrote the service-resource text and merge it with the introduction. | ||||||||||||
20030522 | JCS | s/set of parts/list of parts/. | ||||||||||||
20030514 | JJM | Updated the service-resource figure, and split the diagram into two. | ||||||||||||
20030512 | JJM | Added service-resource drawing and description. | ||||||||||||
20030512 | JJM | Added syntax summary for the Interface component. | ||||||||||||
20030428 | MJG | Various edits to 3. Types , D. E. Examples of Specifications of Extension Elements for Alternative Schema Language Support. to accommodate accomadate other type systems and spell out how extensibility elements/attributes play out in such scenarios. | ||||||||||||
20030428 | MJG | Added text to 1.2 Notational Conventions regarding normative nature of schema and validity of WSDL documents | ||||||||||||
20030411 | JJM | Allowed features and properties at the interface, interface operation, binding and binding operation levels, as agreed at the Boston f2f http://lists.w3.org/Archives/Public/www-ws-desc/2003Mar/0019.html. | ||||||||||||
20030411 | JJM | Incorporate features and properties' text from separate document and merged change logs | ||||||||||||
20030313 | MJG | Changed title to include 'part 1' | ||||||||||||
20030313 | MJG | Changed port to endpoint | ||||||||||||
20030313 | MJG | Changed type to interface in binding | ||||||||||||
20030313 | MJG | Changed mep to pattern and message exchange pattern to message pattern | ||||||||||||
20030313 | MJG | Added text to C.2 D.2 PortTypes | ||||||||||||
20030313 | MJG | Changed portType to interface | ||||||||||||
20030407 | JJM | Refined and corrected the definitions for features and properties. | ||||||||||||
20030304 | JJM | Filled in blank description of Feature and Property component. | ||||||||||||
20030303 | MJG | Skeleton Feature and Property components | ||||||||||||
20030305 | MJG | Merged ComponentModelForMEPs branch
(1.46.2.5) into main branch (1.54). Below is change log from the
branch:
|
||||||||||||
20030228 | MJG | Updated 4.2 Importing Descriptions to be consistent in layout with other XML rep sections. Detailed that documentation and extensibility attributes are allowed, per schema | ||||||||||||
20030228 | MJG | Updated 4.1 Including Descriptions to be consistent in layout with other XML rep sections. Detailed that documentation and extensibility attributes are allowed, per schema | ||||||||||||
20030228 | MJG | Updated 2.8.2 2.9.2 XML Representation of Binding Component to list type attribute | ||||||||||||
20030217 | MJG | Minor edits to wording in 2.3.1 2.4.1 The Interface Operation Component | ||||||||||||
20030213 | MJG | Added xlink nsdecl to spec element | ||||||||||||
20030213 | MJG | Incorporated text from dbooths proposal on semantics, per decision 20021031 | ||||||||||||
20030213 | MJG | Merged operationnames branch (1.37.2.3)
into main branch (1.46). Below is the change log from the branch.
|
||||||||||||
20030213 | MJG | Change name of {message exchange pattern} back to {variety} to consolidate changes due to MEP proposal | ||||||||||||
20030206 | MJG | Updated Appendix A to refer to Appendix C | ||||||||||||
20030204 | MJG | Tidied up appendix C | ||||||||||||
20030203 | MJG | Incorporated resolution to R120 | ||||||||||||
20030124 | MJG | Fixed error in 2.4.2 2.5.2 XML Representation of Message Reference Component which had name attribute information item on input, output and fault element information item being mandatory. Made it optional. | ||||||||||||
20030123 | JJM | Change name of {variety} property to {message exchange pattern} | ||||||||||||
20030130 | MJG | Updated binding section to match changes to port type section WRT operation names | ||||||||||||
20030130 | MJG | Added best practice note on operation names and target namespaces to 2.3.1 2.4.1 The Interface Operation Component | ||||||||||||
20030122 | MJG | Started work on making operations have unique names | ||||||||||||
20030122 | MJG | Added some <emph>, <el>, <att>, &AII;, &EII;, <el> markup | ||||||||||||
20030120 | MJG | Incorporated Relax NG section from Amy's types proposal | ||||||||||||
20030120 | MJG | Incorporated DTD section from Amy's types proposal | ||||||||||||
2003020 | MJG | Incorporated Amy's types proposal except annexes | ||||||||||||
20030118 | MJG | Made some changes related to extensibility | ||||||||||||
20030118 | MJG | Amended content model for operation to disallow fault element children in the input-only and output-only cases | ||||||||||||
20030118 | MJG | Removed {extension} properties from Binding components and Port components. Added text relating to how extension elements are expected to annotate the component model. | ||||||||||||
20030117 | MJG | Made further edits related to extensibility model now using substitution groups | ||||||||||||
20030117 | MJG | Added initial draft of section on QName resolution | ||||||||||||
20030117 | MJG | Reworked section on extensibility | ||||||||||||
20030116 | MJG | Added text regarding multiple operations with the same {name} in a single port type | ||||||||||||
20030116 | MJG | Added section on symbol spaces | ||||||||||||
20030116 | MJG | Removed various ednotes | ||||||||||||
20030116 | MJG | Added section on component equivalence | ||||||||||||
20030116 | MJG | More work on include and import | ||||||||||||
20021201 | MJG | Did some work on wsdl:include | ||||||||||||
20021127 | MJG | Added placeholder for wsdl:include | ||||||||||||
20021127 | MJG | Cleaned up language concerning
targetNamespace attribute information item
2.1.2.1
targetNamespace attribute information item |
||||||||||||
20021127 | MJG | changed the language regarding extensibility elements in 2.1.2 XML Representation of Definitions Component . | ||||||||||||
20021127 | MJG | Moved all issues into issues document ( ../issues/wsd-issues.xml ) | ||||||||||||
20021127 | MJG | Removed name attribute from definitions element | ||||||||||||
20021127 | MJG | Removed 'pseudo-schema' | ||||||||||||
20021121 | JJM | Updated media type draft appendix ednote to match minutes. | ||||||||||||
20021111 | SW | Added appendix to record migration issues. | ||||||||||||
20021107 | JJM | Incorporated and started adapting SOAP's media type draft appendix. | ||||||||||||
20021010 | MJG | Added port type extensions, removed service type. | ||||||||||||
20020910 | MJG | Removed parameterOrder from spec, as decided at September 2002 FTF | ||||||||||||
20020908 | MJG | Updated parameterOrder description, fixed some spelling errors and other types. Added ednote to discussion of message parts | ||||||||||||
20020715 | MJG | AM Rewrite | ||||||||||||
20020627 | JJM | Changed a few remaining <emph> to either <att> or <el>, depending on context. | ||||||||||||
20020627 | SW | Converted portType stuff to be infoset based and improved doc structure more. | ||||||||||||
20020627 | SW | Converted message stuff to be infoset based and improved doc structure more. | ||||||||||||
20020625 | SW | Mods to take into account JJM comments. | ||||||||||||
20020624 | JJM | Fixed spec so markup validates. | ||||||||||||
20020624 | JJM | Upgraded the stylesheet and DTD | ||||||||||||
20020624 | JJM | Added sections for references and change log. | ||||||||||||
20020624 | JJM | Removed Jeffrey from authors :-( Added Gudge :-) | ||||||||||||
20020620 | SW | Started adding abstract model | ||||||||||||
20020406 | SW | Created document from WSDL 1.1 |