RE: [emergency] Whatever Happened to the Public UDDI? Web Services Registries Fad e

["Bullard, Claude L (Len)" <clbullar@ingr.com>]

Right.  In industry, the keiretsu phenomenon dominates. 
One needs not just partners, but credible partners. 
And rules are very different given the process, say 
a procurement offer vs a services offer, and so on. 
UDDI doesn't help much here and it can actually make 
it much tougher to negotiate a good deal.

The same can be said of public safety agencies, but one 
questions if that can be maintained in the face of current 
events and requirements.  However, what the public safety 
groups as a whole should be discussing are the services 
that can be exposed more or less across agencies of 
different types because this cannot be based on the 
data they create or share.  As you know, the Internal 
Affairs group cannot expose name or incident information 
to other internal agencies.  Dissemination Management 
is required to ensure redaction of information shared 
to the public given a juvenile, for example, and so 
forth.  So the business rules for standard services 
have to be worked out.  A registry is fairly easy 
given that.

len


From: Aerts, John F. [mailto:jfaerts@lasd.org]

Yvonne L. Lee and David Rubinstein, Software Development Times

A few years ago, when Web services were envisioned as creating
interconnected applications that spanned across businesses, public
Universal Description, Discovery and Integration (UDDI) registries
were seen as a tree on which to find the fruit -- or external Web
services. Now that Web services are used almost exclusively for
internal development and integration, not only has the hype
surrounding the public UDDI registries subsided, but the
information in them hasn't grown either.

<http://sdtimes.com/news/082/special2.htm>



You may leave a Technical Committee at any time by visiting
http://www.oasis-open.org/apps/org/workgroup/emergency/members/leave_workgro
up.php