RE: [uddi-spec] TN idea: link tags for UDDI

["Von Riegen, Claus" <claus.von.riegen@sap.com>]

Paul,

The problem is still there. When you want to get the necessary information from "a homepage", you have to know this homepage. I believe that the registration of UDDI registries in the UDDI Business Registry meets the same requirement (late binding of Web services, including UDDI services) while it
is completely based on existing technology.

Claus

-----Original Message-----
From: Paul Denning [mailto:pauld@mitre.org] 
Sent: Montag, 12. Mai 2003 18:49
To: uddi-spec@lists.oasis-open.org
Subject: Re: [uddi-spec] TN idea: link tags for UDDI


At 02:55 AM 2003-05-10, Max Voskob wrote:
>Sorry, I still can't who and why would use this technology?
>Is there a real life use case for this?
>
>Cheers,
>Max

Any consumer (application) of web services that uses a UDDI registry at 
runtime to discover the accessPoint URI of a service given only a tModelBag 
for the fingerprint of the services it wants to use.  This app will use 
UDDI to find the services, but how would it find the UDDI service?

The idea is to do late binding of a service to its accessPoint.  That way I 
don't need to know the accessPoint at development-time or even at 
deployment-time.

We need a way to do late binding to the UDDI service itself.  I am 
suggesting that the <link> tag in a homepage would be a place to find the 
accessPoint (or associated businessEntity) for one or more UDDI servers 
(SOAP inquiry API).

For example, a number of autonomous wireless sensors may be dropped via 
parachute into an area.  The sensors gather information and may want to 
report it somewhere using web services.  Perhaps the sensors provide a SOAP 
interface, and would publish to a private UDDI registry (once they find a 
UDDI registry).  Other devices that come within range of the area may want 
to discover the set of sensors (web services) in that area.  The whole IP 
infrastructure may be brought into this area on mobile or transportable 
platforms.

Call it zero administration UDDI.

If you don't automate discovery of UDDI, then someone has to do it 
manually.  I may be able to do that easily for the UBR accessPoints, but 
when I want to use private UDDI servers, then manual configuration gets 
more difficult.

Hope that helped.

Paul