P. 1
Web Services Description Language

Web Services Description Language

Ratings: (0)|Views: 72|Likes:
Published by Prasanna Kumar.G
WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information.
WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information.

More info:

Published by: Prasanna Kumar.G on Apr 08, 2010
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOCX, PDF, TXT or read online from Scribd
See more
See less





Web Services Description Language (WSDL) 1.1
WSDL is an XML format for describing network services as a set of endpoints operating onmessages containing either document-oriented or procedure-oriented information. The operationsand messages are described abstractly, and then bound to a concrete network protocol andmessage format to define an endpoint. Related concrete endpoints are combined into abstractendpoints (services). WSDL is extensible to allow description of endpoints and their messagesregardless of what message formats or network protocols are used to communicate, however, theonly bindings described in this document describe how to use WSDL in conjunction with SOAP1.1, HTTP GET/POST, and MIME.
This document is a submission to theWorld Wide Web Consortium(seeSubmission Request, W3C Staff Comment) as a suggestion for describing services for theW3C XML Activity onXML Protocols. For a full list of all acknowledged Submissions, please seeAcknowledgedSubmissions to W3C.This draft represents the current thinking with regard to descriptions of services within Ariba,IBM and Microsoft. It consolidates concepts found in NASSL, SCL, and SDL (earlier proposalsin this space).This document is a NOTE made available by the W3C for discussion only. Publication of this Note by W3C indicates no endorsement by W3C or the W3C Team, or any W3C Members.W3C has had no editorial control over the preparation of this Note. This document is a work in progress and may be updated, replaced, or rendered obsolete by other documents at any time.A list of current W3C technical documents can be found at theTechnical Reportspage.
Table of Contents
1 Introduction. 1.1 WSDL Document Example 1.2 Notational Conventions 2 Service Definition 2.1 Document Structure 2.1.1 Document Naming and Linking 2.1.2 Authoring Style 2.1.3 Language Extensibility and Binding 2.1.4 Documentation 
2.2 Types 2.3 Messages 2.3.1 Message Parts 2.3.2 Abstract vs. Concrete Messages 2.4 Port Types 2.4.1 One-way Operation 2.4.2 Request-response Operation. 2.4.3 Solicit-response Operation 2.4.4 Notification Operation 2.4.5 Names of Elements within an Operation 2.4.6 Parameter Order within an Operation 2.5 Bindings 2.6 Ports 2.7 Services 3 SOAP Binding 3.1 SOAP Examples 3.2 How the SOAP Binding Extends WSDL 3.3 soap:binding 3.4 soap:operation 3.5 soap:body 3.6 soap:fault 3.7 soap:header and soap:headerfault 3.8 soap:address 4 HTTP GET & POST Binding 4.1 HTTP GET/POST Examples 4.2 How the HTTP GET/POST Binding Extends WSDL 4.3 http:address 4.4 http:binding 4.5 http:operation 4.6 http:urlEncoded 4.7 http:urlReplacement 5 MIME Binding 5.1 MIME Binding example 5.2 How the MIME Binding extends WSDL 5.3 mime:content 5.4 mime:multipartRelated 5.5 soap:body 5.6 mime:mimeXml 6 References A 1 Notes on URIs A 1.1 XML namespaces & schema locations A 1.2 Relative URIs A 1.3 Generating URIs A 2 Wire format for WSDL examples A 2.1 Example 1 A 3 Location of Extensibility Elements
A 4 SchemasA 4.1 WSDL SchemaA 4.2 SOAP Binding SchemaA 4.3 HTTP Binding SchemaA 4.4 MIME Binding Schema
1. Introduction
As communications protocols and message formats are standardized in the web community, it becomes increasingly possible and important to be able to describe the communications in somestructured way. WSDL addresses this need by defining an XML grammar for describing network services as collections of communication endpoints capable of exchanging messages. WSDLservice definitions provide documentation for distributed systems and serve as a recipe for automating the details involved in applications communication.A WSDL document defines
as collections of network endpoints, or 
. In WSDL,the abstract definition of endpoints and messages is separated from their concrete network deployment or data format bindings. This allows the reuse of abstract definitions:
,which are abstract descriptions of the data being exchanged, and
port types
which are abstractcollections of 
. The concrete protocol and data format specifications for a particular  port type constitutes a reusable
. A port is defined by associating a network address witha reusable binding, and a collection of ports define a service. Hence, a WSDL document uses thefollowing elements in the definition of network services:
a container for data type definitions using some type system (such as XSD).
an abstract, typed definition of the data being communicated.
an abstract description of an action supported by the service.
ort Type
an abstract set of operations supported by one or more endpoints.
a concrete protocol and data format specification for a particular port type.
a single endpoint defined as a combination of a binding and a network address.
a collection of related endpoints.These elements are described in detail in Section 2. It is important to observe that WSDL doesnot introduce a new type definition language. WSDL recognizes the need for rich type systemsfor describing message formats, and supports the XML Schemas specification (XSD)[11]as itscanonical type system. However, since it is unreasonable to expect a single type system grammar to be used to describe all message formats present and future, WSDL allows using other typedefinition languages via extensibility.In addition, WSDL defines a common
mechanism. This is used to attach a specific protocol or data format or structure to an abstract message, operation, or endpoint. It allows thereuse of abstract definitions.In addition to the core service definition framework, this specification introduces specific
binding extensions
for the following protocols and message formats:

Activity (7)

You've already reviewed this. Edit your review.
1 hundred reads
enoch_praveen liked this
Leonardo liked this
shulin2010 liked this
LMarino66 liked this
nagesh6257427 liked this
LMarino66 liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->