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

RE: Back to Requirements (was RE: Web Service Definition [Was "So me T houghts ..."])

From: Cutler, Roger (RogerCutler) <RogerCutler@chevrontexaco.com>
Date: Tue, 5 Mar 2002 23:35:28 -0600
Message-ID: <3B286631A9CFD1118D0700805F6F9F5A066F8695@hou281-msx1.chevron.com>
To: "'Mark Baker'" <distobj@acm.org>, chris.ferris@sun.com
cc: www-ws-arch@w3.org
Why is it critical that a web service have only one interface?  I don't know
of any mechanism by which there could be more than one, but what would be
the problem with that if someone figured out how to do it?

-----Original Message-----
From: Mark Baker [mailto:distobj@acm.org] 
Sent: Tuesday, March 05, 2002 10:23 PM
To: chris.ferris@sun.com
Cc: www-ws-arch@w3.org
Subject: Re: Back to Requirements (was RE: Web Service Definition [Was "Some
T houghts ..."])

Chris, I just noticed something else;

> "A web service is a software application or component identified by a 
> URI, whose interfaces and binding are capable of being described by 
> standard XML vocabularies and that supports direct interactions with 
> other software applications or components through the exchange of 
> information that is expressed in terms of an XML Infoset via 
> internet-based protocols".

Other than the concerns I've already raised about "binding", "direct
interaction", and the necessity for a distinction between component and
application, I just noticed that "interfaces" is plural.  Is there any
particular reason for that?  I believe it's critical that a Web service have
a single interface.  Perhaps it's just a terminology issue, but I'd
appreciate clarification.


Mark Baker, Chief Science Officer, Planetfred, Inc.
Ottawa, Ontario, CANADA.      mbaker@planetfred.com
http://www.markbaker.ca   http://www.planetfred.com
Received on Wednesday, 6 March 2002 00:35:55 UTC

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