"I know this is not going to set well with a lot of folks but the fact
is, this is the truth about SOA. Yes, SOA is a better way of
architecting the interactions between applications and data resources."
An interesting observation. IF SOA is indeed a better way of
architecting the
interaction between applications and data resources THEN what is it
that we
use to describe the interactions and the data resources in a way that
does not
pre-suppose any one technical architecture and in a way that is
unambiguous
and in a way that does not take a specific services view point?
I seem to come back to this list about this topic all of the time
and I have yet
to receive any answer at all let alone ones that I do not agree with.
For my part this is exactly what WS-CDL provides. So where are the
other solutions
to doing this and why are they any good at doing it?
Cheers
Steve T
On 19 Jan 2007, at 11:10, Gervas Douglas wrote:
There are some comments on SOA and its business value which may
interest you here:
http://tech.groups.yahoo.com/group/business-process-management/
message/270
Gervas
