W3C home > Mailing lists > Public > www-ws-desc@w3.org > February 2002

RE: WSDL Requirements

From: Sadiq, Waqar <waqar.sadiq@eds.com>
Date: Mon, 18 Feb 2002 09:33:22 -0600
Message-ID: <9C79F2D39765D411B18900508BE326A20A82ED38@USPLM208>
To: Paul Prescod <paul@prescod.net>, www-ws-desc@w3.org
Paul,

I am having a hard time understanding your requirement.  I actually do
understand your requirements but don't think those are requirements on WSDL
itself.  Whether a web service is stateful or stateless is a characteristic
of the web service.  I don't clearly see the role of a description language
in that?  Can you explain?

Thanks,

 
_______________________________________________
Waqar Sadiq
 
EDS EIT EASI - Enterprise Consultant
MS: H3-4C-22
5400 Legacy Drive
Plano, Texas 75024
 
phone: +01-972-797-8408 (8-837)
e-mail: waqar.sadiq@eds.com
fax: +01-972-605-4071
_______________________________________________
 
 

-----Original Message-----
From: Paul Prescod [mailto:paul@prescod.net] 
Sent: Friday, February 15, 2002 4:11 PM
To: www-ws-desc@w3.org
Subject: WSDL Requirements

1. WSDL should be at least as functional as IDL languages (or the
current Web) in its handling of persistent state that is known to both
clients and servers.

It should be possible for a service to return a URI that represents some
state (i.e. data and associated methods). It should be possible for the
resource associated with that URI to be strongly type-checked within
WSDL so that the set of methods applicable to it are predefined.

For example, a programming language should be able to statically type
check something like this:

po = service.createPO(...)
total = po.total()

Garbage collection is not required. The owner of a reference could
define its lifetime (just as with implicit objects managed by UUIDs, or
in the C programming language etc.).

If WSDL does not support this then it seems to me that it will not scale
to solving real-world problems.

2. I should also be able to hand a web service references to objects
created by other services, again by URL. Once again, it should be
possible to strongly type check these. The service should be able to
depend upon the strong type checking to know what methods will be
available on the data objects.

If WSDL does not support this then again it seems to me that it will not
solve real-world problems.

Summary:

WSDL needs a concept of reference with strongly typed-referents. The
reference syntax should be URIs. The referents must be describable
within WSDL as services in and of themselves.

 Paul Prescod
Received on Monday, 18 February 2002 10:33:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:18 GMT