Home page > The ebXML Technology> The ebXML Technical Infrastructure > Registry                                     

Registry

The Registry provides a stable store where information submitted by a Submitting Organization is made persistent. Such information is used to facilitate ebXML-based Business to Business (B2B) partnerships and transactions. Submitted content may be XML schema and documents, process descriptions, ebXML Core Components, context descriptions, UML models, information about parties and even software components.

The ebXML Registry architecture consists of an ebXML Registry Service and ebXML Registry Clients. The ebXML Registry Service provides the methods for managing a repository. An ebXML Registry Client is an application used to access the Registry.

The Registry and Repository within ebXML are currently defined using two specifications. These are:

• The OASIS/ebXML Registry Services Specification v2.1

http://www.oasis-open.org/committees/regrep/documents/2.1/specs/.

• The OASIS/ebXML Registry Information Model v2.1

http://www.oasis-open.org/committees/regrep/documents/2.1/specs/.

Each of the specifications has a specific use.

The OASIS/ebXML Registry Services Specification v2.1
The ebXML Registry Service is comprised of a robust set of interfaces designed to fundamentally manage the objects and inquiries associated with the ebXML Registry. The two primary interfaces for the Registry Service consist of:

• A Life Cycle Management interface that provides a collection of methods for managing objects within the Registry.
• A Query Management Interface that controls the discovery and retrieval of information from the Registry.

A registry client program utilizes the services of the registry by invoking methods on one of the above interfaces defined by the Registry Service. This specification defines the interfaces exposed by the Registry Service as well as the interface for the Registry Client.

The OASIS/ebXML Registry Information Model v2.1
The Registry Information Model provides a blueprint or high-level schema for the ebXML Registry. Its primary value is for implementers of ebXML Registries. It provides these implementers with information on the type of metadata that is stored in the Registry as well as the relationships among metadata Classes. The Registry information model:

• Defines what types of objects are stored in the Registry.
• Defines how stored objects are organized in the Registry.

The Registry Information Model may be implemented within an ebXML Registry in the form of a relational database schema, object database schema or some other physical schema. It may also be implemented as interfaces and classes within a Registry Implementation.

Developed by CEN/ISSS W/S eBES - ©1999-2003 All Rights reserved. Terms of use       

This page last modified on 2009-03-02