the web services interoperability organization (ws-i) is an industry consortium chartered to promote interoperability amongst the stack of web services specifications. ws-i does not define standards for web services; rather, it creates guidelines and tests for interoperability. it has recently become part of oasis, another standards body. it is governed by a board of directors consisting of the founding members (ibm, microsoft, bea systems, sap, oracle, fujitsu, hewlett-packard, and intel) and two elected members (currently, sun microsystems and webmethods). since joining oasis, other organizations have joined the ws-i technical committee including ca technologies, jumpsoft and booz allen hamilton. the organization's deliverables include profiles, sample applications that demonstrate the profiles' use, and test tools to help determine profile conformance. == ws-i profiles == according to ws-i, a profile is a set of named web services specifications at specific revision levels, together with a set of implementation and interoperability guidelines recommending how the specifications may be used to develop interoperable web services. * ws-i basic profile * ws-i basic security profile * simple soap binding profile == ws-i profile compliance == the ws-i is not a certifying authority; thus, every vendor can claim to be compliant to a profile. however the use of the test tool is required before a company can claim a product to be compliant. see ws-i trademarks and compliance claims requirements in a 2003 interview, a ws-i spokesman said regarding false claims of compliance: "we expect enforcement of that brand to be market-driven. we suspect no one wants to be the first person to be called on for making a bad claim... as (software vendors) establish the value of the ws-i profiles, hopefully ... vendors will realize that it's in their best interests to make sure they are all truly interoperable"  ==see also== *web services resource framework == external links == * ws-i home page * the microsoft - ws-i controversy, cnet news, may 2002
Interoperability Web_services