On Mon, Mar 3, 2008 at 5:17 PM, Michael Poulin <[EMAIL PROTECTED]> wrote: > "Why don't we just follow the architectural principles of the web?" asked Nick. > I can ask the same question in opposite direction - why do? To resolve this 'to do or not to do', we have to answer another question: why are we doing or what to do this? What for? To make a standard based open interface for applications? Web Services did it perfectly. What we are still not happy? Why we have OASIS SOA RM and, soon, will have SOA RA( ref. architecture)? > > My answers is because architecture in SOA is not about interfaces only. It is about business behaviour and social context. This is why "just follow the architectural principles of the web" is not enough for SOA now. To some degree, I see it in ebXML. However, even this rich contractual environment has issues with business trust and deal agreements - they require initial business interactions to happen automatically later.
I agree that SOA is not about interfaces only, but that was essentially what the ZapThink piece was focused on -- technical interface issues, eg the use of WS-Addressing for loose coupling. I was simply pointing out that WOA/REST/architectural principles of the Web (whatever you want to call it/them) are a far more proven approach to the technical issues of loose coupling than WS-*/WS-Addressing is. -- Nick
