＋设为首页 ＋添加到收藏夹
uddi has been around for almost three years now. it has gone from an initial proposal by three companies (ariba, ibm, and microsoft), to a consortium effort (www.uddi.org) with a community of hundreds, and finally into the hands of the oasis standards body. along the way, the original specification has gone through two additional revisions. perhaps more important, with each new revision the business value of uddi has shifted from being a registry of public services to a central fixture in private eai and partner-integration efforts.
the most recent version of uddi, v3, continues this trend by making uddi more usable as a common service registry inside an extended enterprise and between partners. thus this technology, originally designed for publishing and discovering web services, can today be leveraged by enterprises to provide a complete solution for managing access to web services including subscription control and endpoint indirection.
is uddi only for the public internet?
along with soap and wsdl, uddi is considered one of the three "pillars" of web services technologies. unfortunately, it is probably the least understood, at least initially. at the root of the various misconceptions about uddi is the schizophrenic nature of the specification. the uddi idea initially (and to this day) encompasses two very distinct concepts. the first one is the concept of a universal, online business registry, the universal business registry (ubr), maintained and operated by a set of impartial operators along the lines of the dns infrastructure. it is hoped that this ubr will act as some form of universal, multilayered "phone book" for registering businesses and the services they provide across the world, (for good or bad, this "universality" is baked into the uddi name). this is the concept most people know abo... 下一页