W3C home > Mailing lists > Public > www-ws-arch@w3.org > July 2002


From: Christopher B Ferris <chrisfer@us.ibm.com>
Date: Mon, 22 Jul 2002 22:34:40 -0400
To: www-ws-arch@w3.org
Message-ID: <OFB2323EAD.9BAD6363-ON85256BFF.000DE7A4@rchland.ibm.com>

True, but you can <import> any aspect of the WSDL, hence the separation of
concerns is
not really addressed. It is only by convention that the interface and
aspects MAY be separated.


Christopher Ferris
Architect, Emerging e-business Industry Architecture
email: chrisfer@us.ibm.com
phone: +1 508 234 3624

                      Ugo Corda                                                                                                   
                      <UCorda@SeeBeyond        To:       "'Hao He'" <Hao.He@thomson.com.au>, www-ws-arch@w3.org                   
                      .com>                    cc:                                                                                
                      Sent by:                 Subject:  RE: [HST] WSDL                                                           
                      07/22/2002 01:28                                                                                            

>2. Both interface and implementation is defined in one WSDL.

Not entirely correct. WSDL's "import" mechanism effectively allows the
separation of interface aspects and implementation aspects in two separate
WSDL documents if so desired.


-----Original Message-----
From: Hao He [mailto:Hao.He@thomson.com.au]
Sent: Sunday, July 21, 2002 11:20 PM
To: 'Mark Baker'; Newcomer, Eric
Cc: www-ws-arch@w3.org
Subject: [HST] WSDL


Here is another take of "harvesting" WSDL.  Please add anything I might be


<harvest name="WSDL">

WSDL plays a descriptor role in the overall Web Services
architecture.  WSDL is static as it does not define dynamic interactions
Web Services.


WSDL defines
 1. abstract functionality of a service
 2. concrete binding details for SOAP 1.2, HTTP, and MIME


wsdl   "http://www.w3.org/2002/07/wsdl" A normative XML Schema [XML Schema:
Structures], [XML Schema: Datatypes] document for the
"http://www.w3.org/2002/07/wsdl" namespace can be found at
soap12 "http://www.w3.org/2002/07/wsdl/soap12" Defined by WSDL 1.2:
[WSDL 1.2 Bindings].
http   "http://www.w3.org/2002/07/wsdl/http" Defined by WSDL 1.2: Bindings
[WSDL 1.2 Bindings]. mime "http://www.w3.org/2002/07/wsdl/mime" Defined by
WSDL 1.2: Bindings [WSDL 1.2 Bindings].

WSDL has dependencies on XML schema.

Web Services model by WSDL

Summary: http://www.w3.org/TR/2002/WD-wsdl12-20020709/#intro

"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
format. A message consists of a collection of typed data items. An exchange
messages between the service provider and requestor are described as an
operation. A collection of operations is called a portType. Collections of
portTypes are grouped and called a serviceType. A service represents an
implementation of a serviceType and contains a collection of ports, where
port is an implementation of a portType, which includes all the concrete
details needed to interact with the service."

Components: requestor and provider
Connector: ports.
Data element: typed data item, messages

Architectural concept:

1. Messages are abstract and then bound to a concrete network protocol and
message format;
2. Operation is an exchange of message and there are only four types of
operations  (Input-Output,Output-Input, Input only, and Output only)

Architectural decisions:
1. Data types are described by XML schema.
2. Both interface and implementation is defined in one WSDL.

WSDL bindings
"A binding defines message format and protocol details for operations and
messages defined by a particular portType. There may be any number of
for a given portType."

WSDL SOAP 1.1 bindings

"1. An indication that a binding is bound to the SOAP 1.2 protocol.
 2. A way of specifying an address for a SOAP endpoint.
 3. The URI for the SOAPAction HTTP header for the HTTP binding of SOAP.
 4. A list of definitions for Headers that are transmitted as part of the
SOAP Envelope"

WSDL HTTP bindings


"1. An indication that a binding uses HTTP GET or POST
 2. An address for the port
 3. A relative address for each operation (relative to the base address
defined by the port) "

WSDL MIME bindings
"1. 'multipart/related', defined in [IETF RFC 2387].
 2. 'text/xml', defined in [IETF RFC 3023].
 3. 'application/x-www-form-urlencoded', defined in Form content types
([HTML 4.01], section 17.13.4).
 4. Others (by specifying the MIME type string) "

WSDL extensibility


"WSDL has an open content model: every element in the
'http://www.w3.org/2002/07/wsdl' namespace allows arbitrary extension
attributes and extension elements as long as their names are fully
and they are defined in a namespace other than

WSDL issues:

1. Link handling

2. Does not support description of dynamic interactions.

Received on Monday, 22 July 2002 22:52:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:40:57 UTC