W3C home > Mailing lists > Public > www-ws-arch@w3.org > April 2003

RE: Nailing down the definition of "Web services" and the scope o f WS A for the document

From: Anne Thomas Manes <anne@manes.net>
Date: Wed, 16 Apr 2003 21:27:53 -0400
To: "Walden Mathews" <waldenm@optonline.net>, "Champion, Mike" <Mike.Champion@SoftwareAG-USA.com>, <www-ws-arch@w3.org>
Message-ID: <ECEDLFLFGIEENIPIEJJPOEFAEAAA.anne@manes.net>

I describe it as a service with a Web API.
(an interface may be a UI)

> -----Original Message-----
> From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On
> Behalf Of Walden Mathews
> Sent: Wednesday, April 16, 2003 9:19 PM
> To: Champion, Mike; www-ws-arch@w3.org
> Subject: Re: Nailing down the definition of "Web services" and the scope
> o f WS A for the document
>
>
>
> Maybe a Web service is a service with a Web interface.  Plus
> some other stuff?
>
> I think I got caught thinking "interface" in the most abstact
> sense, sorry.
>
> WM
>
> ----- Original Message -----
> From: "Champion, Mike" <Mike.Champion@SoftwareAG-USA.com>
> To: <www-ws-arch@w3.org>
> Sent: Wednesday, April 16, 2003 8:26 PM
> Subject: RE: Nailing down the definition of "Web services" and
> the scope o f
> WS A for the document
>
>
> >
> >
> >
> > > -----Original Message-----
> > > From: Walden Mathews [mailto:waldenm@optonline.net]
> > > Sent: Wednesday, April 16, 2003 5:37 PM
> > > To: Champion, Mike; www-ws-arch@w3.org
> > > Subject: Re: Nailing down the definition of "Web services"
> > > and the scope
> > > of WS A for the document
> > >
> > >
> >
> > > I would resist the temptation to define a service as an interface,
> > > because I think the default understanding is that services *have*
> > > interfaces, not that they *are* interfaces.
> >
> > Hmmm ... I think the way we (actually Eric) have recently defined it is
> > clearer.  The code that does something in the real world might be a
> > "service" (and for that matter, the humans that put the book in
> the box or
> > load the truck, etc. might be the ones who perform the "service"), but I
> > think it's useful to think of the *Web* service as the standard XML/URI
> > interface to the service.  That way the Web service can be neutral with
> > respect to whether the "service" involves bits, atoms, humans,
> or whatever
> > ... it's all just about XML and URIs.
> >
> > Maybe Eric could remind us  of the rest of his reasoning ....
> > >
> >
>
Received on Wednesday, 16 April 2003 21:26:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:17 GMT