What is the difference between Binding Template and a tModel?
A tModel represents a service type -- an abstract representation of a service. A bindingTemplate represents a specific instance of a service. For example, a UDDI registry is a type of Web service, exposing two APIs -- the Inquiry and the Publication APIs. There's a tModel for each of these APIs: uddi-org:Inquiry and uddi-org:Publication. These tModels describe the APIs, but they don't provide access information. IBM, Microsoft, HP, SAP, Systinet, and other companies offer instances of the UDDI services. The UDDI entry for each of these companies includes a businessService entry for the UDDI services, and these businessService entries have a bindingTemplate that associates the service implementation with the service type tModel. The bindingTemplates also provide specific service information, such as the accesspoint.
For example, look at the Systinet registration in the public UDDI: Systinet DiscoveryURL
Dig Deeper on Service-oriented architecture (SOA)
Related Q&A from Anne Thomas Manes
Anne Thomas Manes explains the differences between open source clients and open source implementations. Continue Reading
Anne Thomas Manes discusses the best way to go about creating an enterprise data dictionary and why the systems works well. Continue Reading
Anne Thomas Manes explains the difference between 'hard' real time and 'live' real time systems. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.