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

RE: Requirements WSP02, WSP03 & WSP08 (was Re: Web Service Defini tion)

From: Sadiq, Waqar <waqar.sadiq@eds.com>
Date: Thu, 28 Feb 2002 15:29:09 -0600
Message-ID: <9C79F2D39765D411B18900508BE326A20AC43D1E@USPLM208>
To: "Garg, Sharad" <sharad.garg@intel.com>, "'Hugo Haas'" <hugo@w3.org>, www-ws-arch@w3.org


You just described what self-contained is that the service can fulfill its
responsibility without the need of using other resources.  So does this mean
that if I build a web service that aggregates other web services to present
a more consolidated contract, then it is not a web service?

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: Garg, Sharad [mailto:sharad.garg@intel.com] 
Sent: Thursday, February 28, 2002 3:00 PM
To: 'Hugo Haas'; www-ws-arch@w3.org
Subject: RE: Requirements WSP02, WSP03 & WSP08 (was Re: Web Service Defini

As just discussed, here is a simple general definition of Web Services
independent of any particular protocol.

	Self-contained, self-describing, loosely coupled software
components that can be described, published, discovered and invoked over a
network using standard web protocols.


-----Original Message-----
From: Hugo Haas [mailto:hugo@w3.org]
Sent: Wednesday, February 27, 2002 12:12 PM
To: www-ws-arch@w3.org
Subject: Requirements WSP02, WSP03 & WSP08 (was Re: Web Service

* Joseph Hui <jhui@digisle.net> [2002-02-25 11:43-0800]
>   A web service is a computing entity with the following properties
>   (which incidentally sound like requirements also).

A few comments about your list requirements:

>   WSP02: A web service MUST provide standards-based programmatic
>   interface with well defined input/output parameters.
>   (For the sake of simplicity, RPC returns may be deemed output 
>   parameters in web services.)
>   WSP03: A web service MUST be sufficiently well formulated such
>   such it can be unambiguously described using WSDL.  

I think that WSP02 and WSP03 are not clearly separated.

They both talk about clear description. I would separate them as:

  WSP02: A Web service MUST provide standards-based programmatic

  WSP03: A Web service MUST be sufficiently well formulated such it
  can be unambiguously described using a service description language.

Two changes:
- "with well defined input/output parameters" has been removed from
  WSP02; I believe that WSP03 covers this.
- "WSDL" is replaced by "a service description language"; I am still
  unhappy about this but here is my train of thoughts: which
  specification does the current WSP03 refer to? WSDL 1.0? WSDL 1.1?
  The output of the Web Services Description Working Group? The
  description technology that our group will identify for the Web
  services framework? My modification implies that it is the latter.

>   WSP08: A web service MAY advertise itself in as many public
>   directories as appropriate, such as those operated by the
>   UDDI consortium.  

We should be careful about centralization:

  The Web is by design and philosophy a decentralized system, and its
  vulnerabilities lie wherever a central facility exists.
  -- http://www.w3.org/DesignIssues/Architecture#schemes

I don't think that WSP08 is really necessary, or at least not
formulated as such. What about:

   WSP08: Web services MUST be able to advertize themselves.



Hugo Haas - W3C
mailto:hugo@w3.org - http://www.w3.org/People/Hugo/ - tel:+1-617-452-2092
Received on Thursday, 28 February 2002 16:29:23 UTC

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