I remember reading about how UDDI was about to change the way business is run in my first .NET book on C# (version 1.0 of course). The story went something like this: a tired developer that sat in his hotel room and wanted to find a place to eat of his preferences. He would pick up his devlopment tool, search the local UDDI (with the correct paramters - that's tModels) after that he would simply order the table online with web services. Though this is an amazing scenario, it was terrible naive and as such almost dumb. I'll not deny that something similar can be done today or in the near future, but not in a general scope and for certain not with UDDI at it's core. UDDI do have other uses and I guess in the intranet senario it does have penetration, wheres the extranet has mainly seen the big players shutting down the DBR. There is some description of how UDDI has evolved and possible use cases in the Oasis paper UDDI Executive Overview: Enabling Service-Oriented Architecture [PDF](October 2004).
As I've put into the title of this post, with a bit of drama, taken that UDDI is up for it the extranet scenario might become real in a foreseeable future. The good folks of CSI in DNITA has annonced the hearing of the Danish OIO UDDI Profile Version 1.1 (In [PDF] or [DOC]). I'll gladly admit that I haven't figured it all out yet, and I'm curious about what happened to version 1.0, that I've never seen, but the closest was Address resolving service, version 0.8 that was published about 1½ year ago.
To get a 10.000 ft overview over where this fits in a larger picture, you can read the timeline in Visioner og milepæle for serviceorienteret infrastruktur [PDF](Danish only, the title is "Visions and milestones for a service-orienteret infrastructure"). Another great source is the Architecture document that's mentioned in the short reference section which you'll probably need to consult. For my own convenience I've add them here with links:
- [OIOSI-ARCH]: The Architecture of the Danish OIO Service Oriented Infrastructure - Draft version 0.8 [PDF] (In English). A very good introduction to what they are trying to achieve.
- [UDDI-3.0]: UDDI Version 3.0.2, UDDI Spec Technical Committee Draft, Dated 20041019 [HTML]. They just reference version 3 from 2002, but I guess the difference is minimal and just a typo.
- [UDDI-WSDL]: Technical Note: Using WSDL in a UDDI Registry, Version 2.0.2 [HTML].
- [RASP]: OIO Reliable Asynchronous Secure Profile 1.0 [PDF] (English). Once again I'm a little confised about the versioning, since in the document it says version 1.1, but I can only find the hearing version of 1.0
And they forgot a reference for:
- OWSA model T version 1.0 [PDF] - OIO Web Service Arkitektur model Transportbaseret sikkerhed (danish only)
The document contains some examples of using the UDDI Inquiry API, that I've fleshed out to XML-documents: