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

RE: Separate concepts for "service" and "targetResource?" (was RE: /service/@targetResource ?)

From: David Orchard <dorchard@bea.com>
Date: Thu, 22 May 2003 08:56:15 -0400
To: "'Walden Mathews'" <waldenm@optonline.net>, "'Assaf Arkin'" <arkin@intalio.com>
Cc: "'Ugo Corda'" <UCorda@SeeBeyond.com>, "'Champion, Mike'" <Mike.Champion@softwareag-usa.com>, <www-ws-arch@w3.org>
Message-ID: <003701c32061$8860aee0$140ba8c0@beasys.com>

> > If I don't care which ATM I'm using then the ATM I use
> today and the ATM
> > you use today may be the same ATM, the same service. But you can't
> > switch the targetResource based on who is accessing the ATM. So my
> > account is not the targetResource, but "the ATM network"
> could be the
> > resource that links all these services together.
> There's a reason why procedural programming was kinda dropped
> a few decades ago in favor of the object model.  I have a feeling we
> are going to see that metamorphosis again soon.  This is like taking
> one object method, promoting it to global scope, and then trying to
> bind it back to only a single instance.

Indeed.  Because Object-orientation is fundamentally broken when it comes to
real world things.  The "subject", ie the object performing the "verb", and
the "object", ie the real world thing, are separate.  In order to talk about
real world things, subjects and objects - objects in the language sense -
need to be first class citizens of the grammar.  You need to have the
subject,verb,object structure to be able to make proper assertions about
things are and who can do what to the things.  WSDL is making some simple
assertions, what services an object exposes.

Now you can argue that O-o can model this by having an o-o object represent
the real-world object.  But then there's all these darned leaky abstraction
problems that we spent 25% of our time in software dealing with.  And in
fact, WSDL also supports this model because you don't have to provide the
resource URI.  WSDL has the classic problem that the assertions about the
resource may be in different structures and owned by different people, and I
think they solve it in a nice way.

Received on Thursday, 22 May 2003 08:54:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:05:52 UTC