On 1/16/06, Eric Newcomer <[EMAIL PROTECTED]> wrote: > One point that will always give us trouble compared to > the specs for HTTP, SOAP etc. is that SOA is not a > technology like those but a style of design, or > approach to IT that is technology independent. So you > can't nail it down the way you can nail down something > like J2EE using a set of API and protocol specs.
Eric, I'm disappointed to here you say that. We've had a pretty decent framework for rigorously (not "formally") defining architectural styles for many years now, since at least Perry and Wolff's "Foundations" paper and its predecessors, i.e.; http://www.ece.utexas.edu/~perry/work/papers/swa89.pdf FWIW, I took a stab at this a few years ago; http://lists.w3.org/Archives/Public/www-ws-arch/2002Sep/0083.html But that was rejected. A few months later, Dave Orchard made his own attempt; http://lists.w3.org/Archives/Public/www-ws-arch/2003Feb/0055.html Which was also rejected. 8-( Mark. -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca Coactus; Web-inspired integration strategies http://www.coactus.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
