Often times, it is quite handy to provide a link for your UDDI entry to someone else. "Check out my tModel at http://..." With the new user interface both on the Microsoft public node and on the UDDI Services in Windows Server 2003, this ability has been complicated by the use of frames.
However, one can still achieve this bevahior of providing a link to a graphic rendering of your UDDI entry. The following patterns can be used for the different entities: in UDDI:
Business Key: http://uddi.microsoft.com/details/businessdetail.aspx?key=Provider GUID
Service Key: http://uddi.microsoft.com/details/servicedetail.aspx?key=Service GUID
Binding Key: http://uddi.microsoft.com/details/bindingdetail.aspx?key=Binding GUID
tModel Key: http://uddi.microsoft.com/details/modeldetail.aspx?key=tModel GUID
In UDDI Services, the pattern holds true, but you would use http://[server name]/uddi or http://[server name]/uddipublic as the root, depending on whether you were using Windows authentication or not.
However, users following these links will lose the ability to navigate, as the navigation frames will be lost.
Of course, to provide an XML representation of the entity, you can use the discoveryURL. The pattern for that syntax is as follows:
http://uddi.microsoft.com/discovery.ashx?businessKey=Provider GUID
or for UDDI Services
http://[server name]/uddipublic/discovery.ashx?businessKey=Provider GUID
Remember, discoveryURLs are only for providers (businessEntity) and this type of HTTP-GET of UDDI XML is not available for tModels.
