OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] ANN: Distributed Registry for Web Services

[ Lists Home | Date Index | Thread Index ]

Roger L. Costello wrote:

>Hi Folks,
>You are invited to participate in the collaborative development of a
>distributed registry technology.
>We have created a list (distributed-registry) for discussion of this
>topic.  To subscribe to the list send an empty email to:
>    distributed-registry-subscribe@yahoogroups.com
>Here is a description of the purpose of a distributed registry:
>A Web service registry provides information about what services do, and
>how they are used. Today's Web service registries (e.g., UDDI and ebXML)
>are implemented as centralized repositories. That is, all services store
>their service descriptions within a single, or a small number of
>registries. The purpose of this effort is to develop a concrete,
>implementable architecture for a highly distributed registry. The notion
>is that each Web service defines their own registry - comprised of the
>collection of documents that describes the service. 
Hi Roger,

The ebXML Registry V3 is defined as an open standard by the OASIS ebXMl 
Registry TC [1]. It supports a loosely couple distributed model where 
registries are peers and do not require any prior contract. The 
following distributed registry features are supported:

-Inter-registry object references

-Registry federations

-Federated queries using SQL 92 and XML filter query syntax

-Inter-registry object relocation

In addition features the following features make the registry attractive 
as a general purpose content management solution:

-Handles arbitrary content (Any type of Service description and anything 
else is supported)

-Automatically validates and catalogs arbitrary content upon submission 
in a content specific manner

-Allows discovery of content using ad hoc queries in SQL 92 and XML 
Filter query syntax

The registry has a long list of additional features. Details are 
available from the specifications [2] and also from a recent slide 
presentation [3] in html form. Finally, an open source implementation 
named ebxmlrr [4] is available with a active and healthy user community. 
This includes a standard Java API for XML Registries called JAXR [5].

ebXML Registry is being used for a variety of purposes in a variety of 
verticals including healthcare, eGov, Automotive, Travel etc. Version 3 
is adding distributed capabilities as well as Content-based Event 
notification and a pure HTTP interface that strives towards REST.

We would like to invite you and your project to consider ebXML Registry 
and help identify limitations it may have in meeting your use case. We 
could work together in the ebXMl Registry TC [1] to address any such 
limitations with the next version of the OASIS ebXML Registry Standard.

[1] OASIS ebXML Registry TC

[2] Latest versions of ebXML Registry V3 specs directly from CVS:
Registry Services spec: 
Registry Information Model spec: 

[3]  Slide Presentation on ebXML Registry V3

[4] Open Source Implementation of ebXML Registry and JAXR API

[5] Java API for XML Registry 1.0 (JAXR)



News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS