Table of contents

[Home] [W3C Specs]

1.1 Notational Conventions

2 Component Model

2.1 Definitions

2.1.1 The Definitions Component

2.1.2 XML Representation of Definitions Component

2.1.3 Mapping Definitions' XML Representation to Component Properties

2.2 Message

2.2.1 The Message Component

2.2.2 XML Representation of Message Component

2.2.3 Mapping Message's XML Representation to Component Properties

2.3.1 The Part Component

2.3.2 XML Representation of Part Component

2.3.3 Mapping Part's XML Representation to Component Properties

2.4 Port Type

2.4.1 The Port Type Component

2.4.2 XML Representation of Port Type Component

2.4.3 Mapping Port Type's XML Representation to Component Properties

2.5 Port Type Operation

2.5.1 The Port Type Operation Component

2.5.2 XML Representation of Port Type Operation Component

2.5.3 Mapping Port Type Operation's XML Representation to Component Properties

2.6 Message Reference

2.6.1 The Message Reference Component

2.6.2 XML Representation of Message Reference Component

2.6.3 Mapping Message Reference's XML Representation to Component Properties

2.7 Binding

2.7.1 The Binding Component

2.7.2 XML Representation of Binding Component

2.7.3 Mapping Binding's XML Representation to Component Properties

2.8 Binding Operation

2.8.1 The Binding Operation Component

2.8.2 XML Representation of Binding Operation Component

2.8.3 Mapping Binding Operation's XML Representation to Component Properties

2.9 Binding Message Reference

2.9.1 The Binding Message Reference Component

2.9.2 XML Representation of Binding Message Reference Component

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

2.10 Service

2.10.1 The Service Component

2.10.2 XML Representation of Service Component

2.10.3 Mapping Service's XML Representation to Component Properties

2.11.1 The Port Component

2.11.2 XML Representation of Port Component

2.11.3 Mapping Port's XML Representation to Component Properties

2.12 Equivalence of components

2.13 Symbol Spaces

2.14 QName resolution

3.1 Using W3C XML Schema Description Language

3.1.1 Importing XML Schema

3.1.2 Embedding XML Schema

3.1.3 References to Type and Element Definitions

3.2 Using Other Schema Languages

4 Modularizing WSDL descriptions

4.1 Including Descriptions

4.2 Importing Descriptions

5 Documentation

6 Language Extensibility

6.1 Element based extensibility

6.1.1 Mandatory extensions

6.1.2 required attribute information item

6.2 Attribute based extensibility

7.1 Normative References

7.2 Informative References

Appendices

A The application/wsdl+xml Media Type

A.1 Registration

A.2 Security considerations

B Acknowledgements

C URI References for WSDL constructs

C.1 WSDL URIs

C.2 Fragment Identifiers

C.3 Extension Elements

C.4 Example

C.5 Relation to WSDL 1.1

D Migrating from WSDL 1.1 to WSDL 1.2

D.1 Operation Overloading

D.2 PortType Inheritance

E Examples of Specifications of Extension Elements for Alternative Schema Language Support.

E.1.1 namespace attribute information item

E.1.2 location attribute information item

E.1.3 References to Element Definitions

E.2 RELAX NG

E.2.1 Importing RELAX NG

E.2.2 Embedding RELAX NG

E.2.3 References to Type and Element Definitions

F Part 1 Change Log

F.1 WSDL Specification Changes

1 Introduction

Introduction

Web Services Description Language (WSDL) provides a model and an XML format for describing Web services. WSDL enables one to separate the description of the abstract functionality offered by a service from concrete details of a service description such as "how" and "where" that functionality is offered.

This specification defines a language for describing the abstract functionality of a service as well as a framework for describing the concrete details of a service description. The companion specification, WSDL Version 1.2: Bindings [WSDL-PART2] defines a language for describing such concrete details for SOAP 1.2 [SOAP12-PART1], HTTP [RFC2616] and MIME [RFC2045].

WSDL describes Web services starting with the messages that are exchanged between the service provider and requestor. The messages themselves are described abstractly and then bound to a concrete network protocol and message format. A message consists of a collection of typed data items. An exchange of messages between the service provider and requestor are described as an operation. A collection of operations is called a port type. A service contains a collection of ports, where each port is an implementation of a portType, which includes all the concrete details needed to interact with the service.

[Next Chapter] [Home]