Interface Detail:

Why Interop?

Unlike traditional programming models,  where functions/methods are likely consumed by your own applications, web services are to be accessed by much wider variety of applications written in different languages, using different toolkits,  even operating on different operating systems. Interoperability thus becomes crucial to the success of SOAP services, and a key criterion for selecting development platforms. 

Interop is, and has been, a community effort with participations from  large companies to small players since the beginning of 2001. Great successes have been achieved through communications, discussions, and interop testing. As an early participant and proponent of SOAP interoperability, we are thankful to all parties in the interop group for their inputs, comments and suggestions; and we strongly encourage all toolkits developers to join the community. 

Related Information:

• iLab: Round 1 interoperability test lab.
• Round 2: Round 2 interoperability test lab.
• Round 3: Round 3 test plan.
• Round 3: Round 3 interop test home page.
• Interop Interface Definitions: Proposed test cases.
• Semon's Interop Registration Feeds (RSS 1.0).
• Interop Endpoint Info: Participating endpoint information. 
• Simon Fell's Interop Registry
• SOAPBuilders Interop Roadmap: We are far from being done yet ! 

Other Interop Results

Related Tools:

• Interop Test Tool
• Generic SOAP Client.
• Interop Registry Search