W3C home > Mailing lists > Public > public-ws-addressing@w3.org > December 2004

RE: i0001: EPRs as identifiers - alternative proposal

From: David Orchard <dorchard@bea.com>
Date: Thu, 2 Dec 2004 13:06:48 -0800
Message-ID: <32D5845A745BFB429CBDBADA57CD41AF0C1DEA09@ussjex01.amer.bea.com>
To: "Savas Parastatidis" <Savas.Parastatidis@newcastle.ac.uk>, "Francisco Curbera" <curbera@us.ibm.com>, <public-ws-addressing@w3.org>

I don't know what the difference between a bank account and a banking
service is.  What is the difference between the 2 from a software
perspective?  

I'll note that WSDL 2.0 service elements can describe most, if not all
of the Web resources.  

We do Web services so that we can have interactions that are typically
characterized by sending SOAP messages and has WSDL descriptions, but
there is no clear technical distinctions between Web services and non
Web services (such as Web or Semantic Web) technologies.  There are
marketing differences definitely.  

I think that if you look at the heart of your differentiation, you'll
find that they are circular or illogical.  Resources are things that are
identified by "universal resource identifiers".  Services are things
that are interacted with in service oriented manner.  Etc.  

So, I suggest not trying to differentiate between "services" and
"resources" for the purpose of EPRs as identifiers issue.

Dave

> -----Original Message-----
> From: Savas Parastatidis [mailto:Savas.Parastatidis@newcastle.ac.uk]
> Sent: Thursday, December 02, 2004 12:18 PM
> To: David Orchard; Francisco Curbera; public-ws-addressing@w3.org
> Subject: RE: i0001: EPRs as identifiers - alternative proposal
> 
> >
> > I don't see any difference between a resource oriented and a service
> > oriented architecture in your terms.  I think that if any
> > differentiation needs to be made, it is
> > - whether the resource is accessed via a uniform interface or a
custom
> > interface,
> > - whether the resource is stateful or stateless
> >
> > Dave
> 
> I agree about the differences you identify but I also see a difference
> between a "bank account" and a "banking service". The first is a
> resource while the second is a service. Calling the first a "service"
or
> the latter a "resource" just doesn't feel natural to me. Why do we
> bother with Web _Services_ if everything is a resource?
> 
> If you live in a resource-only world like the Web, then I can see how
> everything is seen as a resource. To some folks with object-oriented
> background everything looks like an object. I wear service-only
> "goggles" :-)))
> 
> Regards,
> .savas.
Received on Thursday, 2 December 2004 21:06:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:00 GMT