[regrep-cooperating] Kickoff of federated registries work item for V3

[Farrukh Najmi <Farrukh.Najmi@Sun.COM>]

Folks,

The cooperating registry sub-team is about to begin in earnest on the Federated ebXML Registries proposal for V3. The email discussion on this should be carried out on the regrep-cooperating@lists.oasis-open.org mail alias. I am also copying some folks who have expressed interest in joining this sub-team and collaborating on this work item. I ask that all those that wish to participate join the regrep-cooperating@lists.oasis-open.org mailing list using the following web page:

    http://lists.oasis-open.org/ob/adm.pl

Next I would like to establish some context for the work item we are embarking upon.

Use Cases Being Addressed By Work Item

Quite
some time ago in this team we defined the following use case for federated
registries:

Use Case: Peer-to-Peer Federated Registries

"A group of ebXML Registries wish to project a unified logical registry
to their clients. To the client it appears as if there is one registry
that has the sum total of all the data from all the registries. This
client experience is the same regardless of which specific registry
within the federation receives the client request."

I would like to also add the following use cases as target for federated registries:

Use Case: Hierarchically Federated Registries

"Two registries wish to have a hierarchical parent/child relationship such
that the child registry represents a subset of data  within the larger
parent registry. Changes made to the dataset of the child are eventually
reflected in the parent dataset. Queries made to the child registry return
results that reflect the dataset of both the parent and the child registries
combined."

Use Case: Caching of Registry Data

"A target registry wishes to cache some or or all of  the data of
another another source registry that is willing to share its data. The
shared dataset is copied from the source registry to the target registry
and is visible to queries on the target registry even when the source registry
is not available."

Note that this use case is a primitive use case that may be used to implement the first two use cases (p2p and hierarchical federated registries). We may decide that this use case should be removed as a separate use case.

Relevant Links

The following thread discusses some high level thoughts on the subject.

    http://lists.ebxml.org/archives/ebxml-dev/200204/msg00127.html

Next Steps

I propose the following next steps. We will finalize things as a team.

1. Begin email discussion on use cases with the proposed 3 use cases as starting points
2. Agree to a time for a kickoff meeting where we indulge in some free flowing brainstorming and discussion
3. Determine team rules, milestones, deliverables and action items
4. Meet periodically over phone to sync on deliverables

Proposed Meeting Time

There is no proposed meeting time until we know who is part of the team
and where are they located and what are their preferences. Please send
me this information privately if you wish to be part of the team.

Proposed Team Rules

Here are some suggestions:

• To be a member of the team you must be willing to contribute. Contributions may involve one or more of the following: attending team meetings, authoring spec content, implementing proof-of-concepts (POC), taking action items, taking meeting notes, tracking issues etc.
• No duplication of effort. Every one executes on an agreed plan and action items.

Proposed Milestones / Deliverables

• Team formation - by COB (Close of business, 6pm US Eastern) Wed May 15
• Kickoff meeting - by COB  May 24th
• Agreement on Use Cases - by COB May 24
• First draft of written proposal by COB June 7
• POC implementation begins by COB June 7th (Note that it is the intent of this work item to do a parallel implementation so that the specs are ground firmly in reality and practical experience.)
• POC implementation completed by COB July 26th
• Proposed Final draft to TC by COB August 9th
• Final draft to Editors by COB Aug 30th

Immediate Action Items

• Confirm intent to be a team member privately to me by Monday 6pm US Eastern. Please indicate preferences for meeting day/time.  (All interested)
• Join the regrep-cooperating@lists.oasis-open.org mailing list ASAP (All)
• Share on team alias, any proposals that you may have in the works related to federated registries. This is to avoid duplication of effort. (All)
• Discuss on team alias, the proposed use cases via email, as well as sends any other comments on this email (All)

--
Regards,
Farrukh