From WSDL to UDDI

There is some overlap between them in the way they describe services.
The coalition has a document describing the best practices to follow when using a WSDL description to generate a UDDI registration.

Divide the WSDL description into two files.
- One file includes the data types, messages, portTypes, and bindings. It is known as the interface description.
- The other file includes just the service definition. It is known as the implementation description. Use wsdl:import to import the first one.
Register the interface description as a UDDI TModel and mark the TModel as one that represents a WSDL interface description (whose WSDL file must be available in a website).
Specify that the service is an instance of this TModel.
Provide a link to the WSDL implementation description, which must also be available in a website.
Initialize the proxy and call the save_service operation to register the service.

For example, IBM's Emerging Technologies Toolkit allows you to easily find a service with UDDI and invoke it via a dynamically configured WSDL-based proxy.