<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<!-- /*******************************************************************************
 * Copyright (c) 2000, 2005 IBM Corporation and others.
 * All rights reserved. This program and the accompanying materials
 * are made available under the terms of the Eclipse Public License v1.0
 * which accompanies this distribution, and is available at
 * http://www.eclipse.org/legal/epl-v10.html
 * 
 * Contributors:
 *     IBM Corporation - initial API and implementation
 *******************************************************************************/ -->
<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
<title>Web services interoperability (WS-I)</title>
</head>
<body id="cwsiover"><a name="cwsiover"><!-- --></a>

<h1 class="topictitle1">Web services interoperability (WS-I)</h1>
<div><p>WS-I is an organization designed to promote Web service interoperability
across platforms, operating systems, and programming languages.</p>
<p>For more information on WS-I, refer to their Web site:  <a href="http://www.ws-i.org/" target="_blank">http://www.ws-i.org/</a>.
This site contains resources such as an overview of Web services interoperability,
usage scenarios, and specifications.</p>
<p>WS-I Basic Profile is a outline of requirements to which WSDL and Web service
protocol (SOAP/HTTP) traffic must comply in order to claim WS-I conformance.
The Web services WS-I validation tools currently support WS-I Simple SOAP
Binding Profile 1.0 (WS-I SSBP) which builds on the WS-I Basic Profile, and
the WS-I Attachments Profile 1.0 (WS-I AP). To view the specifications, refer
to the WS-I Web site, and under  <span class="uicontrol">Deliverables</span> select
 <span class="uicontrol">Basic Profile</span>.</p>
<p>Depending on the type of Web service being created, you may or may not
want your Web service to comply with the WS-I profiles. The default level
of compliance is to generate a warning if a non WS-I SSBP complaint Web service
option is selected and to ignore any non WS-I AP compliant selections. You
can set the level of WS-I compliance at the workspace or project level. The
Web services wizards, the WebSphere<sup>®</sup> run-time environments, the WSDL editor,
and other Web services tools provided support and encourage the development
of WS-I compliance services.</p>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="../tasks/twsicomply.html">Setting the level of WS-I compliance</a></strong><br />
The Web services WS-I validation tools support the level of WS-I
compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding
Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You
can choose to make your Web service compliant or non-compliant, depending
on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols,
and secured Web services, are not WS-I compliant.</li>
</ul>

<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div>
</div>

<div class="linklist"><strong>Related Tasks</strong><br />

<div><a href="../tasks/twsicomply.html" title="The Web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You can choose to make your Web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols, and secured Web services, are not WS-I compliant.">Setting the level of WS-I compliance</a></div></div>
</div> 
</body>
</html>