[regrep-infomodel] Kickoff of "Type extensibility in RIM" work itemfor V3

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

Folks,

The infomodel sub-team is about to begin in earnest on the "Type extensibility in RIM" work item for V3. The email discussion on this should be carried out on the regrep-infomodel@lists.oasis-open.org mail alias. Those who wish to participate, please join the regrep-infomodel@lists.oasis-open.org mailing list using the following web page:

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

Use Cases Being Addressed By Work Item

The following use cases are proposed for this work item. Note that this
is just an initial proposal.

Use Case: User Defined Sub-Types of Existing RIM Classes

"A user submits a request to create a new sub-type of an existing RIM class
(e.g. RegistryObject, RegistryEntry). Registry creates metadata defining
the new user-specified type. Once the new type is defined instances of
that type may be submitted to the registry and queries may be submitted
against the new user-defined type."

Relevant Links

The following resources may be useful:

• The Self language tutorial is useful reading. Note that the Self language motivated the use of Slots in RIM as proposed by Nikola in V1. Of specific interest may the the notion of prototypes in Self.

Next Steps

The following next steps are an initial suggestion. We will finalize things
as a team.

1. Begin email discussion on use cases with the proposed 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 involve attending team meetings and one or more of the following: 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 22
• Kickoff meeting - by COB  June 7th
• Agreement on Use Cases - by COB June 7th
• First draft of written proposal by COB June 14
• POC implementation begins by COB June 14 (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 Aug 2
• Proposed Final draft to TC by COB August 16
• Final draft to Editors by COB Sep 6

Immediate Action Items

• Confirm intent to be a team member privately to me by May 17 6pm US Eastern. Please indicate preferences for meeting day/time.  (All interested)
• Join the regrep-infomodel@lists.oasis-open.org mailing list ASAP (All)
• Share on team alias any relevant links, related works etc.
• Share on team alias, any proposals that you may have in the works related to this work item. 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