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

Hi

I am sorry , was just going through the emails, and actually not
formally a part of this group.But,

I dont think a Web Service should have only 1 interface, although it seems
so.
But deep inside a core web service can /should have more than 1 interfaces
if the "core service has a interface", but the multiple interfaces extend
this core service
interface depending on the context of the invoker(s) of this web service.

I am not sure if my reply is relevant,but anyway thats my 2 cents.

-
 Vikram Verma
Senior Systems Analyst @ Infostrands
----------------------------------------------------------------------------
+91 80 2293708/2293843/2331197    Cell :+91 98452 09521
vikram@infostrands.com                     vicky_verm@hotmail.com
----------------------------------------------------------------------------
----- Original Message -----
From: "Cutler, Roger (RogerCutler)" <RogerCutler@chevrontexaco.com>
To: "'Mark Baker'" <distobj@acm.org>; <chris.ferris@sun.com>
Cc: <www-ws-arch@w3.org>
Sent: Wednesday, March 06, 2002 11:05 AM
Subject: RE: Back to Requirements (was RE: Web Service Definition [Was "So
me T houghts ..."])


> 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.
>
> Thanks.
>
> MB
> --
> 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 02:06:07 UTC