Slashdot Mirror
Why UDDI Will Work
Tim Smith of The Stencil Group pointed out a white paper that The Stencil Group put together concerning UDDI [?] . With UDDI's six month birtday, they say that it's building momentum, and postulate about why it will work in the end. Check out UDDI.org for other information as well.
The post is a troll.
While IBM sold machines to Germany that they used to perform the deportations, IBM had no idea about the Final Solution. Even the scholar who released the book about IBM and Germany acknowleged this (I read about it in Newsweek a couple of months ago).
IBM stopped dealing with Germany after the invasion of Poland. This was well before the U.S. entered the war, and before the SS even planned their elimination methods. The plan was drawn up by the #2 SS man in 1941 (I think 1941...), we just covered this in my Genocide course.
I don't know why the post was moderated up. The poster's UDDI "Nazi" connection is crap. "their missions were allied on the mighty Axis of powers" hahaha
As a developer working on a Web Services Development Platform, it is very important to me that UDDI and the web services revolution succeed. I think they certainly have that capability; Web Services are here to stay, and UDDI will probably become pretty useful in a year or two. However, there is no doubt that there are significant problems with UDDI as it now stands. Here are a couple, and you can email me if you're interested in more.
1) No fact-checking mechanism:
As it now stands, any business can go to one of the main UDDI providers (Ariba, Microsoft, and IBM), and register their company. This company could be legitimate, could be pornographic, or could be entirely false and fraudulent. Moderation and arbitration is always a tricky subject, as demonstrated by the last couple hundred WIPO cases, and this case is no exception. If I register in IBM's UDDI directory as "Microsoft Corporation," who decides that I'm not actually Bill Gates? If I register a fraudulent service, charge for it, and then screw my customers, who is liable? With a rotating management (executives from each of the three administration companies take turns being in charge), how are UDDI placement rules defined and enforced?
At the last UDDI advisory board meeting, the proposed answer was "self-administration." The administrators believe that as UDDI grows in popularity, there will be service providers offering background checks and ratings, similar to the Gomez reviews for B-to-C providers. I can almost accept this explanation, but it is certainly not in place yet.
2) No standardization of entries:
At its heart, the point of UDDI is to find services. These standards-based services are supposed to be available for use and integration by consumers, businesses, etc. Not only are the service descriptions buried beneath several levels of marketing, company information, and other useless junk, but there is also currently no standardization of entries. The standards are there, the services are there, but they aren't being referenced correctly....and that defeats the purpose. At the lowest level (the green pages referenced in the article), each Web Service should have a service description file, written in WSDL (Web Services Description Language), that specifies available methods, inputs, and outputs. Currently, the lowest level is a hodgepodge of text, Word documents, phone numbers, and a very few WSDL files.
Even if the services were available, the UDDI administrators have not released their web-based search interface yet. Visit http://www-3.ibm.com/services/uddi/find.htm to see an example....the "Find Services" button is unavailable, six months after UDDI's adoption.
We need some form of standardization, and it's not coming any time soon. At the UDDI advisory meeting, this question was pretty much blown off. There is nothing planned for the next two UDDI iterations that will fix this situation, and that means a couple of years at least. If the idea is to have our machines access and execute the services without user intervention, UDDI is a far cry from done.
----
As it stands now, UDDI is relatively unusable. I have high hopes for its future, but I think smaller directories and private service repositories will be quite a bit more useful until UDDI gets past its toddler stage. In-fighting between the administrator companies will probably delay this process, especially since UDDI won't cause money to flow directly back into their pockets any time soon.