docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.html - webservices/webtools.webservices - Git at Google

 <?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 content="text/html; charset=utf-8" http-equiv="Content-Type" />
 <meta name="copyright" content="(C) Copyright 2005" />
 <meta name="DC.rights.owner" content="(C) Copyright 2005" />
 <meta content="public" name="security" />
 <meta content="index,follow" name="Robots" />
 <meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
 <meta content="concept" name="DC.Type" />
 <meta name="DC.Title" content="Web services interoperability (WS-I)" />
 <meta name="abstract" content="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages." />
 <meta name="description" content="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages." />
 <meta scheme="URI" name="DC.Relation" content="../tasks/twsicomply.html" />
 <meta content="XHTML" name="DC.Format" />
 <meta content="cwsiover" name="DC.Identifier" />
 <meta content="en-us" name="DC.Language" />
 <link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" />
 <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>
 <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>
	<?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 content="text/html; charset=utf-8" http-equiv="Content-Type" />
	<meta name="copyright" content="(C) Copyright 2005" />
	<meta name="DC.rights.owner" content="(C) Copyright 2005" />
	<meta content="public" name="security" />
	<meta content="index,follow" name="Robots" />
	<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
	<meta content="concept" name="DC.Type" />
	<meta name="DC.Title" content="Web services interoperability (WS-I)" />
	<meta name="abstract" content="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages." />
	<meta name="description" content="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages." />
	<meta scheme="URI" name="DC.Relation" content="../tasks/twsicomply.html" />
	<meta content="XHTML" name="DC.Format" />
	<meta content="cwsiover" name="DC.Identifier" />
	<meta content="en-us" name="DC.Language" />
	<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" />
	<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>
	<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>