Lists Home |
Date Index |
"Q: Who runs the UDDI Business Registry?
A: The UDDI Business Registry is operated as a distributed service.
Currently, IBM, Microsoft and SAP operate registry nodes. NTT
Communications will bring another registry node online in the near
future. An Operator's Council sets policy and quality of service
guidelines for the operators."
In other words, they decide who will be let in and who will not.
The UDDI v3 spec  introduces the concept of multi-registry
topologies, in which involve the notions of "root" and "affiliate"
registries. The UDDI Business Registry (UBR) can serve as a root
registry, thereby allowing an affiliate registry to establish
inter-registry communication policies and procedures with both the UBR
and any other registry which is an affiliate of the UBR.
Booz | Allen | Hamilton
Not a Member of the OASIS UDDI Technical Committee
Paul Prescod wrote:
> Bullard, Claude L (Len) wrote:
> > That's interesting, Paul. A crank?
> > It is easy to game google so he must
> > be an incredibly incompetent crank.
> Just so.
> > The comparison to Microsoft and IBM is
> > really specious and I am surprised you
> > are making it.
> Not specious at all. In the context of Web Services, the two dominant
> models are decentralized indexes (Google and Yahoo) or centralized
> repositories (UDDI registry-in-the-sky). If I've ever said anything good
> about Google in a Web Services context it is that the decentralized
> model makes more sense for all of the usual reasons that
> decentralization scales better than centralization...including the eased
> of overthrowing monopolies.
> > ... Individuals choose to buy
> > these products, companies choose to buy
> > these products and so on. Same game.
> "Q: Who runs the UDDI Business Registry?
> A: The UDDI Business Registry is operated as a distributed service.
> Currently, IBM, Microsoft and SAP operate registry nodes. NTT
> Communications will bring another registry node online in the near
> future. An Operator's Council sets policy and quality of service
> guidelines for the operators."
> In other words, they decide who will be let in and who will not.
> > Google is free to use and uses the
> > information they get freely. Some
> > joker puts out a spybot that takes
> > a hour or so to get off my machine,
> > and multiplied by all the machines they
> > put it on, is an incredibly costly game.
> I have no idea what you're talking about. You can tell Google not to use
> any of your machine resources and not to index any of your information.
> You have complete control of whether Google's robot (not spybot) indexes
> your information or not. Next you'll say that the xml-dev archiver is a
> > Should they be prosecuted for malicious
> > mischief, or is that just the way the
> > web works?
> I think the answer is pretty clear.
> Paul Prescod
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
fn:Joseph M. Chiusano