A registry is a mechanism whereby relevant documents and metadata about them can be registered such that a pointer to their location, and all metadata, can be retrieved as the result of a query. A registry is required to allow process owners to submit, classify, register and update mapping templates, business process specifications, and data interchange specifications. This registry should have an Application Program Interface (API) expressed in XML which would also support human interfaces through manual HyperText Transfer Protocol (HTTP). registry should support an agreed upon security protocol.

A repository is a location or a set of distributed locations where documents pointed at by the registry reside and from which they can be retrieved by conventional (http / ftp) means, perhaps with additional authentication/permission layers. A repository is required for storage and retrieval of various items that support performing business electronically. There are two distinct sets of business requirements on the repository:

a set dealing with managing the workflow of developing standard components that are stored in the repository

a set dealing with application usage of the repository

Additionally, the repository should support the information needs of the ebXML work group and project teams, as well as ebXML technical specification users with respect to glossaries and products.

The ebXML Registry and Repository will support the concept of a network of registries and repositories that can intercommunicate via the interfaces specified by the ebXML Registry and Repository Project Team. A registry can be established by an industry group or standards organization and can be intercommunicate with any number of repositories. In addition, context with a repository can reference content within another repository. The concept of a single repository is not scalable, nor does it promote the idea of a global web.

Deliverables

• Business Domain Model
• Overall workflow and interaction of registry and repository
• e-Business Requirements Document
• detailed use cases, activity diagrams -> workflow
• Analysis
• object models, sequence diagrams, state machines
• Design
• component diagrams, class diagrams for interfaces, XML generated interfaces off UML class diagrams

Concerns

• So far, we only produced the first of four documents. Although it's probably the easiest one, it took about 6 months to write it. I'm afraid it's going to take more than 2 years to finish everything.
• We haven't yet started the discussion about API, which I believe the most important matter and the goal of this team. We often spend quite a little time to discuss about things irerevant to the ebXML registry and repository, such as transformation services.
• We have only four regular members. In each meeting, we have new faces and have to repeat the same discussions several times. - Probably we need a little more detailed description about what this group is doing, history, what we are trying to accomplish, in the ebXML web page. It helps people to come to the meeting with a knowledge.