Web Services Interoperability

The Web Services Interoperability Organization (WS-I) was an industry consortium created in 2002 and chartered to promote interoperability amongst the stack of web services specifications. WS-I did not define standards for web services; rather, it creates guidelines and tests for interoperability. July 2010, WS-I joined the OASIS, standardization consortium as a member section. [1] In December 2017 i was completed after having reached its standardization objectives.[2] The WS-I Standards are now maintained directly by the relevant technical committees within OASIS. [3]

It was 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 (Sun Microsystems and webMethods). When it joined OASIS, other organizations have joined the WS-I technical committee including CA Technologies, JumpSoft and Booz Allen Hamilton.

The organization's deliverables included 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 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"[4]

The activity related to the definition of tools for the compliance tests is continued by the relevant OASIS technical committees in charge of the standard maintenance.[3]

See also

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.