Approved Version 2.0 TC specifications for the OASIS ebXML Registry Information Model (RIM) and Registry Services Specification (RS) have been published by the OASIS ebXML Registry Technical Committee, together with XML Schemas and UML model diagrams. Implementations of the ebXML Registry's RIM and RS specifications have been reported by several companies. The Registry Information Model document "provides a blueprint or high-level schema for the ebXML Registry. The Registry itself 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 Registry Services Specification defines the interface to the ebXML Registry Services as well as interaction protocols, message definitions and XML schema."

From the initial sections of the Registry Information Model (RIM) specification:

This document specifies the information model for the ebXML Registry. A separate document, ebXML Registry Services Specification, describes how to build Registry Services that provide access to the information content in the ebXML Registry. The goals of this version of the specification are to: (1) Communicate what information is in the Registry and how that information is organized; (2) Leverage as much as possible the work done in the OASIS and the ISO 11179 Registry models; (3) Align with relevant works within other ebXML working groups; (4) Be able to evolve to support future ebXML Registry requirements; (5) Be compatible with other ebXML specifications.

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.

A set of Registry Services that provide access to Registry content to clients of the Registry is defined in the ebXML Registry Services Specification. This document does not provide details on these services but may occasionally refer to them. 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: (1) Defines what types of objects are stored in the Registry; (2) Defines how stored objects are organized in the Registry.

The term "repository item" is used to refer to an object that has resides in a repository for storage and safekeeping (e.g., an XML document or a DTD). Every repository item is described in the Registry by a RegistryObject instance. The term "RegistryEntry" is used to refer to an object that provides metadata about a repository item. The information model does not deal with the actual content of the repository. All Elements of the information model represent metadata about the content and not the content itself.

Implementers of the ebXML Registry may use the information model to determine which Classes to include in their Registry Implementation and what attributes and methods these Classes may have. They may also use it to determine what sort of database schema their Registry Implementation may need. 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.

From the OASIS/ebXML Registry Services Specification:

This document defines the interface to the ebXML Registry Services as well as interaction protocols, message definitions and XML schema. A separate document, ebXML Registry Information Model, provides information on the types of metadata that are stored in the Registry as well as the relationships among the various metadata classes.

The goals of this version of the specification are to: (1) Communicate functionality of Registry services to software developers; (2) Specify the interface for Registry clients and the Registry; (3) Provide a basis for future support of more complete ebXML Registry requirements; (4) Be compatible with other ebXML specifications.

The ebXML Registry provides a set of services that enable sharing of information between interested parties for the purpose of enabling business process integration between such parties based on the ebXML specifications. The shared information is maintained as objects in a repository and managed by the ebXML Registry Services defined in this document. [The document describes scenarios] at a high level some use cases illustrating how Registry clients may make use of Registry Services to conduct B2B exchanges. It is meant to be illustrative and not prescriptive... The Registry Services may be implemented in several ways including, as a public web site, as a private web site, hosted by an ASP or hosted by a VPN provider...

ebXML Registry RIM and RS implementations have been reported by David RR Webber of XML Global Technologies, Lisa J. Carnahan of the National Institute of Standards and Technology, Suresh Damodaran of Sterling Commerce, Inc, and Chaemee Kim of KTNET [GXMLHub project].

[Added note of 2001-12-21] Farrukh Najmi also announced on 2001-12-21 that the JAXR RI 1.0 EA is immediately downloadable as part of the Java XML Pack Winter 01, including tutorial and examples. This version of the JAXR RI provides access to UDDI V1.0 registries. OASIS ebXML V2 Registry support is being added to JAXR RI in a future release. That work is dependent upon there being a specification compliant OASIS ebXML V2.0 registry, as being developed at the open source project at http://sourceforge.net/projects/ebxmlrr. Despite the temporary lack of ebXML Registry support, you will find the JAXR RI interesting because the JAXR API uses an information model that is very similar to ebRIM V2.0."

From the TC Charter: "The OASIS ebXML Registry TC develops specifications to achieve interoperable registries and repositories, with an interface that enables submission, query and retrieval on the contents of the registry and repository. Further, the Registry TC seeks to develop specifications that serve a wide range of uses, covering the spectrum from general purpose document registries to real-time business-to-business registries. Additionally, as part of its specification development work, this TC explores and promotes various emerging models for distributed and cooperating registries."