|
SOAP, FTP, SMTP, etc, can be used as
Transports. I have included a link to a reference document, which if we
are tackling WSDL, should include as a reference and the definition
below:
Here is the Abstract and
Introductory definition for discussion:
"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. The operations and messages
are described abstractly, and then bound to a concrete network protocol and
message format to define an endpoint. Related concrete endpoints are combined
into abstract endpoints (services). WSDL is extensible to allow description of
endpoints and their messages regardless of what message formats or network
protocols are used to communicate, however, the only bindings described in this
document describe how to use WSDL in conjunction with SOAP 1.1, HTTP GET/POST,
and MIME."
"A WSDL document defines services as
collections of network endpoints, or ports. 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: messages, which are abstract descriptions of the data being
exchanged, and port types which are abstract collections of
operations. The concrete protocol and data format specifications for a
particular port type constitutes a reusable binding. A port is defined by
associating a network address with a reusable binding, and a collection of ports
define a service. Hence, a WSDL document uses the following elements in the
definition of network services:
- Types a container for data type definitions using some type system
(such as XSD).
- Message an abstract, typed definition of the data being
communicated.
- Operation an abstract description of an action supported by the
service.
- Port Typean abstract set of operations supported by one or more
endpoints.
- Binding a concrete protocol and data format specification for a
particular port type.
- Port a single endpoint defined as a combination of a binding and a
network address.
- Service a collection of related endpoints.
In addition, WSDL defines a common binding mechanism. This is used to
attach a specific protocol or data format or structure to an abstract message,
operation, or endpoint. It allows the reuse of abstract definitions.
In addition to the core service definition framework, this specification
introduces specific binding extensions for the following protocols and
message formats:
- SOAP 1.1
- HTTP GET / POST
- MIME "
-Gavenraj
----- Original Message -----
Sent: Thursday, October 18, 2001 7:06
AM
Subject: RE: [provision-comment] Re: FW:
Introductory Document
My understanding is
that PSTC may choose to provide a WSDL outline for the eventual finished
service, but that WSDL itself would serve no purpose as a transport. Let’s discuss the WSDL thing on the
conference call today.
Otherwise, I have
updated the document with supplied comments and attach copy
here.
-----Original
Message-----
From: Emo, Kelly
[mailto:kemo@jamcracker.com]
Sent:
Tuesday, October 16, 2001 6:40 PM
To: john.aisien@thortech.com;
Darran
Rolls
Subject: RE: [provision-comment] Re: FW:
Introductory Document
I
reviewed the document and John's comments. The document looks very
solid, a great effort. Regarding the addition of WSDL, I can assume
relevance, but I don't think I know enough about WSDL to be able to envision
how it would be used in a PSTC specification, perhaps it's one of the protocol
bindings that will be relevant to a PSTC interaction for
P2R?
-----Original
Message-----
From: John
Aisien [mailto:john.aisien@thortech.com]
Sent: Tuesday, October 16, 2001 2:53
PM
To: Darran Rolls;
provision-comment@lists.oasis-open.org
Subject: [provision-comment] Re: FW:
Introductory Document
Just had a chance to review - many
thanks, Darran.
Attached a slightly reworded version - e.g. replaced
'ADPR' with 'ADPr' throughout the document, etc.
One comment: Re: provisioning system-to-resource
(P2R) standards, would be a thought to include WSDL in the 'Possible Use Of
Existing Standards Within This Effort' diagram (Figure 2), between the
provisioning systems & the resources, because:-
- there is
precedence re: its technical viability;
- it's a means of significantly
increasing the scope of parties (technology vendor & end customer alike)
who have reason to be interested in PSTC...
...just a thought.
JA
Darran Rolls wrote:
For
some reason this bounced on me.Try again....
Darran
Rolls
Waveset
Technologies
MSIM drolls_waveset@hotmail.com
AIM drollswaveset
YIM
drolls_waveset
http://www.waveset.com/
drolls@waveset.com
Subject:
Introductory Document
Date: Tue, 16 Oct 2001 12:41:07
-0500
From:
"Darran Rolls" <Darran.Rolls@waveset.com>
To:
<adrian.viego@businesslayers.com>,
<kemo@jamcracker.com>,
<WBUMPUS@novell.com>,
<jhodges@oblix.com>,
<sanderson@opennetwork.com>,
<fset@pobox.com>,
<john.aisien@thortech.com>,
<casilva@verisign.com>,
<gsodhi1@home.com>
I have
a couple of things for everyone. I have received several requests for
a high level introduction to the PSTC from individuals outside OASIS and
form some new members wishing to participate. As promised, I have
pulled together such a document and have attached a draft.The purpose of
the document is to give people new to the space an introduction, and get
then ready and able to enter the debate.Please take a few moments to
review it.On the basis that this particular document is intended to prime
people new to the initiative (and therefore will likely not form any part
of the formal standard documentation process) it will be beneficial to get
this reviewed and available asap.
The
PSTC site was looking a little empty. I have added some
verbiage.Please review and comment back to this list.You will note that I
have not sent this message to the provision-comment list.I though it
prudent to get agreement from the proposing members before sending the
"overview" document out to the wider list.
Darran
Rolls
Waveset
Technologies
MSIM drolls_waveset@hotmail.com
AIM drollswaveset
YIM
drolls_waveset
http://www.waveset.com/
drolls@waveset.com
|