Here is an expcert from my book, J2EE Web Services (Page 171, Section 6.2.1) : "6.1.2 The discoveryURL Element The discoveryURL element contains the Web address where the raw businessEntity can be accessed using an HTTP GET message. A discoveryURL can refer to two types of documents: a required businessEntity type and zero or more businessEntityExt types. The data the businessEntity type URL refers to should be in XML format, but it may vary depending on the UDDI product. In most cases it will be an XML document but it might be something else, like a simple text file. The businessEntity�s discoveryURL is generated by the UDDI registry automatically when the businessEntity data is added or modified. The businessEntity�s discoveryURL is useful when perusing a UDDI registry with an HTML browser, which doesn�t normally show the raw XML data. Instead, data is prettied up for HTML viewing. The following snippet shows the discoveryURL from Listing 6�2. Note that you can nest one or more discoveryURL (singular) elements in a discoveryURLs (plural) element. <?xml version='1.0' encoding='UTF-8' ?> <businessEntity businessKey="01B1FA80-2A15-11D6-9B59-000629DC0A53" xmlns="urn:uddi-org:api_v2"> � <discoveryURLs> < <discoveryURL useType="businessEntity"> http://uddi.ibm.com/registry/uddiget?businessKey=01B1FA80�000629DC0A53 </discoveryURL>
</discoveryURLs> When the discoveryURL declares a useType attribute value to be "businessEntity", then it was generated by the UDDI registry and contains the raw businessEntity data. If, however, the discoveryURL�s useType attribute value is "businessEntityExt", then the URL refers to non-UDDI data provided by the publisher. This might include technical specifications, or financial documents, or a Web site, or something else that the publisher feels is important. A publisher may define zero or more businessEntityExt-type discoveryURL elements, but usually there is only one or none. "