Hi, I have been following this thread with interest, and have relied on Google for finding the most popular background material on the subject.
It seems that 3 layers have come in for attention: WS layer This has existed for some time but needs extending (or restricting!) properly to absorb SOA impacts. SOA layer This brings to the party a bus or a contract repository for holding whatever cannot properly be held in a WS discovery service. This layer is charged with supplying semantics-based discovery, orchestration, and choreography. This layer's difficult birth/non- birth is the raison d'etre of this group. Application layer This layer is burdened with whatever cannot be migrated down to the SOA layer. The zero option being to give up on the SOA layer and go with this layer plus the WS layer. Is this analysis fair? If so, maybe I can help find the SOA layer a job! Nic ------------------------ Yahoo! Groups Sponsor --------------------~--> Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life. http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/NhFolB/TM --------------------------------------------------------------------~-> 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/
