Hi All -- As you all know, one of the key parts to making loosely coupled Services work is a well-defined contract that identifies both functional as well as non-functional requirements for Service providers and consumers. By now, you also probably realized that WSDL by itself is not sufficient to provide all the metadata needed for loose coupling and late binding. Other metadata are needed including security, semantics, QoS, SLA, process, etc.
So, what we are looking for are actual examples of real-world contracts, or templates for contracts that you are using in real-world SOA deployments, or at the very least, guidance for how those contracts can be defined. So, help anyone? Thanks in advance! Best, Ron -- _____________________________________________________________ Ronald Schmelzer [EMAIL PROTECTED] Senior Analyst ZapThink LLC Direct: 781-577-2779 / Main: 781-207-0203 ------------------------ 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/
