Domain: uddi.org
Stories and comments across the archive that link to uddi.org.
Comments · 11
-
Re:Reinventing the Web Services Wheel?
So this is basically the same as UDDI [wikipedia.org] for WSDL?
Its similar to UDDI or WS-Discovery in that it provides a service discovery mechanism.
Its dissimilar to them in that it also includes a JavaScript API for calling a service.
Its even more dissimilar in its lack of complexity.
Compare:
Web Intents
UDDI
WS-Discovery -
Re:Online Yellow Pages?
I totally agree. At their core, web services are a common protocol (eg. SOAP) that allow disparate systems to communicate. As far as discoverable services, have the lawyers checked out http://www.uddi.org? in addition, servers such as juddi from apache (and many others) already implement this protocol.
Ultimately though, isn't having "discoverable" services very similar to things like jndi, ldap, and even DNS? what, is amazon gonna patent these as well?!
I hope my American counterparts put an end to this silliness. Surely, Amazon wasn't the first to come up with these ideas, so taking credit for it and being rewarded monetarily seems ridiculous. Monetary reward for a good idea is what a patent is for isn't it?
-
WS SecurityWell Microsoft, IBM and somebody else have released the WS Security "spec" (whitepaper) to address some security issues with SOAP, namely message-level digital signature and encryption. It's technically clean, if a little light on detail.
Things to note (strategic):
None of SOAP, WSDL, UDDI, and now WS Security are "Royalty Free".
SOAP isn't a de jure standard -- it's a W3C "note".
UDDI was supposed to move into an open standards body in 2001 but still hasn't.
By publishing WS Security on their websites and through no open standards body we see Microsoft, IBM and that other company abandoning even attempts to appear open.
On the technical side -- if you want to see a little deeper into the security issues left unsolved by SOAP, I recommend you look at the OASIS technical committee specification, ebXML Message Service Specification version 2.0 rev C.
-
Danger! Royalty-Bearing So-Called Standards!
Microsoft is at it again, this time big-blue is right along with them. IBM and Microsoft are trying to erect so-called standard-bodies that would allow them to get-around the World Wide Web Consortium (W3C) requirements for standards to be royalty-free.
Read this article over at ZDNet to get an overview of what is going on.
While they did release the core SOAP and UDDI specifications to the royalty-free process, they are trying to create "piggy-back" protocls that will ensue royalties (i.e. security signing of SOAP messages, file attachments on soap messages and security policy negotiations). They are trying to establish these standards through the UDDI and WS-I organizations. These organizations are perceived to be open and acceptable standard bodies, but they are not. They are heavily controlled by both juggernauts and conform to their interests.
The W3C and the IETF are the only true standard bodies of the Internet! Do not be fooled by IBM and Microsoft and do not be sucked into their grip!
They are trying to ensure that Open-Source, Free implementations of these standards will not be possible! They will be trying to become "toll-boothes" on the Internet. -
Danger! Royalty-Bearing So-Called Standards!
Microsoft is at it again, this time big-blue is right along with them. IBM and Microsoft are trying to erect so-called standard-bodies that would allow them to get-around the World Wide Web Consortium (W3C) requirements for standards to be royalty-free.
Read this article over at ZDNet to get an overview of what is going on.
While they did release the core SOAP and UDDI specifications to the royalty-free process, they are trying to create "piggy-back" protocls that will ensue royalties (i.e. security signing of SOAP messages, file attachments on soap messages and security policy negotiations). They are trying to establish these standards through the UDDI and WS-I organizations. These organizations are perceived to be open and acceptable standard bodies, but they are not. They are heavily controlled by both juggernauts and conform to their interests.
The W3C and the IETF are the only true standard bodies of the Internet! Do not be fooled by IBM and Microsoft and do not be sucked into their grip!
They are trying to ensure that Open-Source, Free implementations of these standards will not be possible! They will be trying to become "toll-boothes" on the Internet. -
ICANN will soon be irrelevant anyways...
As soon as Microsoft roles out UDDI in all of their products, DNS users will be about as relevant as modern day trailer trash. So, who gives a rats ass what ICANN is doing since their going to be obsolete.
Prove me wrong.
-
Re:UDDI - this is why I am sceptical about it.I don't think anyone denies that UDDI is a small step (though the UDDI folks probably dont' favor 'miniscule'). Rather than claiming to be a total solution, the UDDI executive whitepaper says "UDDI is a building block to enable businesses to quickly, easily and dynamically find and transact with one another". (Somehow that got turned into "UDDI is the building block" on the front page of uddi.org - I'm assuming by an over zealous marketing person. What can you build with one block?)
No one expects the first incarnation of UDDI to automate as complex a business transaction as switching 3 inch valve suppliers. The idea is to get everyone on the same platform so we can begin to automate what we can.
I believe the expected first version process is something like: A human queries UDDI for "companies that do X", finds a list of companies that do what they need, and then (returning to exist processes) individually researches each of them, contacts the one that look legit and has the best price, and strikes a deal.
Then hopefully soon people layer on some kind of trust mechanism and some better filtering capability and the query becomes "the cheapest company that does X and has been in business for Y years and offers so-and-so guarantee", cutting down the research part significantly.
And so on until twenty years from now all sorts of redidulous legal contract type stuff has been automated and the CEO just says "make it so".
-
Re:WTF??
I agree with you, the headline sucked. But: note the link to UDDI.org. At least there was something of substance that wasn't
/.ed. -
Re:Uh...
UDDI stands for Universal Description, Discovery and Integration. Basically it's a super-duper yellow pages for business services that is heavily XML (and HTTP?) based.
Read more at the website, www.uddi.org -
Good but...
What about XML-EDI, UDDI, EbXML (nice little article about the 3 initiatives)? Ok, it is not specifically aimed at groupwares but rather at distributed applications. But, on the other hand, are groupwares aimed at staying localized in just one area ? I'm not too sure. I believe groupwares will slowly mutate to an application server-like architecture where different parts will be build by different companies. Well apart from MS I mean...
-
Active Directory --??
Close to the top of the page is this Q: Who "runs" UDDI? A: The UDDI project is not being "run" by any one company. Nor is it a standards body or a new company. Rather, UDDI is currently being guided by a group of industry leaders that are spearheading the early creation and design efforts. Over the next twelve to eighteen months, the UDDI specifications will be turned over to a standards organization, with the continued commitment of the cross industry team that initiated UDDI. We encourage other companies to join the UDDI project.
Kinda strange, the companies they are talking about are Micro$oft IBM and [Ariba ?]. I dont really know what this means.
I also think someone else has implemented something like this.
I bet it won't live up to their Hype.
------------------------
slashDot me :)
------------------------