Home > Articles > Mobile Application Development & Programming > HTML5 & Web Standards

  • Print
  • + Share This
From the author of

Inquiry APIs

Like the publish APIs, the inquiry APIs use a dedicated uniform resource locator (URL) at a registry. This inquiry URL can be used to retrieve information about registered entities such as businesses, services, and tModels. The inquiry URL accepts XML messages that perform tasks, such as the following (all but the last of which also include getting registration details):

  • Business entity discovery

  • Service discovery

  • Service binding discovery

  • Taxonomy discovery

  • Interaction specification discovery

  • Business relationships discovery

For a complete list, refer to the latest UDDI API specification document.

Figure 1 depicts the role of the inquiry URL in a UDDI registry. The inquiry URLs for the Universal Business Registry (UBR), a global pool of UDDI registries, would normally take the following form:

http://uddi.tasmanAve.com/inquiry

Unlike the publish URL, the inquiry URL doesn't use a secure mode of communication, because inquiry APIs don't need sensitive data such as usernames and passwords. The information being retrieved is also considered public domain; therefore, the publisher should be careful about the kind of data that's published at a UDDI registry. Any user with access to the registry—whether or not the user is registered with the registry—can access the information published by the publisher. (However, a private UDDI registry with greater access control can implement more restrictive policies. An invitation-only or more elaborate registration process can control access to the registry.)

Figure 1Figure 1 UDDI interactions supported on inquiry URL.

  • + Share This
  • 🔖 Save To Your Account