[
Lists Home |
Date Index |
Thread Index
]
<Excerpt>
UDDI uses UUIDs and those UUIDs are specific to some particular
registry.
</Excerpt>
Absolutely true for UDDI V2, in which key values were expressed using a
URI format that starts with the characters "uuid:" followed by a
formatted UUID. In UDDI V3, keys are of datatype anyURI. V3 also
supports publisher-assigned keys, in which a publisher is permitted to
propose a new key for an entity, and - given the policies of the
registry - that key and the entity associated with that key may be
inserted into the registry.
Joe Chiusano
Booz | Allen | Hamilton
Paul Prescod wrote:
>
> Simon St.Laurent wrote:
> > paul@prescod.net (Paul Prescod) writes:
> >
> >>In the context of Web Services, the two dominant
> >>models are decentralized indexes (Google and Yahoo) or centralized
> >>repositories (UDDI registry-in-the-sky).
> >
> >
> > I think I'm missing something here.
> >
> > Google feels useful to me because it has created a centralized
> > repository of information that's normally distributed (scattered) about.
> > While Google goes out and collects the information (while UDDI has a
> > registration process), I still see it as a centralizing force. Google
> > just kind of pulls the information in while UDDI (like Yahoo of old)
> > requires that users push it in.
> >
> > It's entirely possible that I've missed your point, however.
>
> There are a few issues.
>
> First, Google is not mandated as central by any standards body. There is
> no "uddi.org" that decides who gets into the search engine game or not.
>
> Second, Google has no information about a site (except synthesized data
> like PageRank) that you cannot get from the site itself. Therefore, once
> Google does the introduction, you do not ever need to use them again. If
> you want to tell Google about your site you give it a URI and not much
> else.
>
> Third, as a consequence of the second point, Google has no information
> (except ... PageRank) about a site that is not equally available to
> AltaVista and Inktomi. This means that it is theoretically easy to build
> a repository that has exactly the same information as Google (but much
> harder to build a search engine over that repository!).
>
> Fourth, Google's way of addressing resources is by their URIs. That
> means that once I get an introduction through Google, I can introduce a
> third party without going through Google again. UDDI uses UUIDs and
> those UUIDs are specific to some particular registry.
>
> 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>
begin:vcard
n:Chiusano;Joseph
tel;work:(703) 902-6923
x-mozilla-html:FALSE
url:www.bah.com
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
version:2.1
email;internet:chiusano_joseph@bah.com
title:Senior Consultant
fn:Joseph M. Chiusano
end:vcard
|
