<?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>Relationship between UDDI and WSIL</title>
</head>
<body id="cwsilud"><a name="cwsilud"><!-- --></a>

<h1 class="topictitle1">Relationship between UDDI and WSIL</h1>
<div><p>The Web Services Inspection Language (WSIL) and the Universal Description,
Discovery, and Integration (UDDI) specification both address issues related
to Web service discovery.  However, each specification takes a different
approach to the discovery of Web services.  The two specifications can
be used separately or jointly; searching with WSIL can result in finding items
in UDDI.</p>
<p>The UDDI specification addresses Web service discovery through the use
of a centralized model.  One or more repositories are created to house
information about businesses and the services they offer.  Requests and
updates pertaining to the service and business related information are issued
directly against the repositories.  In addition, UDDI prescribes a specific
format for a portion of the stored description information and, to facilitate
advanced (focused) searching, assumes that other description information will
be stored and registered within the system as well.</p>
<p>UDDI systems facilitate focused discovery patterns since these systems
are based on organized repositories that provide advanced searching capabilities. 
This helps requestors locate potential communication partners.  In order
to provide advanced functionality, however, UDDI requires the deployment and
maintenance of a certain amount of infrastructure, thus increasing the cost
of operation.  In addition, unless the service descriptions are stored
only within UDDI, there is a cost associated with keeping the different versions
synchronized.</p>
<p>The WSIL specification relies on a completely distributed model for providing
service-related information.  The service descriptions can be stored
at any location, and requests to retrieve the information are generally made
directly to the entities that are offering the services.  The WSIL specification
does not stipulate any particular format for the service information. 
It relies on other standards, including UDDI, to define the description formats. 
The WSIL specification also relies on existing Web technologies and infrastructure
to provide mechanisms for publishing and retrieving its documents.</p>
<p>WSIL provides the ability to disseminate service-related information through
existing protocols directly from the point at which the service is being offered. 
This enables focused discovery to be performed on a single target; however,
because of its decentralized and distributed model, WSIL is not a good mechanism
for executing focused discovery if the communication partner is unknown.</p>
<p>The UDDI and WSIL specifications should be viewed as complementary technologies
to be used either together or separately depending on the situation. 
For example, a UDDI repository could be populated based on the results found
when performing a search for WSIL documents.  Likewise, a UDDI repository
may itself be discovered when a requester retrieves a WSIL document that references
an entry in the repository.  In environments where the advanced functionality
afforded by UDDI is not required and where constraints do not allow for its
deployment, the WSIL mechanism may provide all of the capabilities that are
needed.  In situations where data needs to be centrally managed, a UDDI
solution alone may provide the best fit.  The UDDI and WSIL specifications
should not be viewed as mutually exclusive.</p>
<div class="note"><span class="notetitle">Note:</span> Both UDDI and WSIL contain only references to WSDL - they do not contain
the WSDL documents themselves.</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cwsil.html" title="Web Services Inspection Language (WSIL) is a service discovery mechanism that is an alternative to UDDI as well as complementary to UDDI. When you discover Web services with UDDI, you go to a centralized registry.  WSIL is an alternative approach to Web service discovery.  WSIL allows you to go directly to the service provider and ask for the services it provides.">Web Services Inspection Language (WSIL)</a></div>
</div>

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

<div><a href="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><a href="cwsinwsa.html">Tools for Web services development</a></div>
<div><a href="cwsil.html" title="Web Services Inspection Language (WSIL) is a service discovery mechanism that is an alternative to UDDI as well as complementary to UDDI. When you discover Web services with UDDI, you go to a centralized registry.  WSIL is an alternative approach to Web service discovery.  WSIL allows you to go directly to the service provider and ask for the services it provides.">Web Services Inspection Language (WSIL)</a></div></div>

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

<div><a href="../tasks/toverws.html"> Developing
Web services</a></div></div>
</div>
</body>
</html>