MCCI R2

MCCI R2 refers to Release 2 of the MCCI domain. The MCCI domain describes the Transmission Wrapper, the Trigger Event, and core CPMs.

Scope of R2

Why do we need R2? What are the major issues we would like to see resolved in R2?

Transmission wrapper split (INM/SOA work item)
Transmission Batch topic
"ControlAct Batching" (although under a different name)
sort out issue of "addressing" in abstract static v3 models. Logical endpoints, system receivers, informationRecipients, etc. Be inspired by established transport frameworks.
de-blue (nice to have, secundary)
Scope down dynamic model assumptions (these have static model consequences, e.g. in terms of use of the Acknowledgement class)
- get MnM to approve motion akin to "drop notion of Receiver Responsibilities, will work on new dynamic model. Current documented RR will be textual constraints."

What are issues that should/can wait for R3?

Orchestration. Dynamic model details. R2 will have to deal with fact that there are major open issues with the current dynamic model, so it needs to cover Receiver responsibilities as well as something akin to CPM.

Aim is to have stable publication for January 2008 (for committee ballot), Normative by Sept 2008.
May2007: editors draft
- Assemble all content
- determine scope for R2. Scope freeze.
- resolve remaining (in scope) issues for R2
Sept2007: first draft with fixed scope (informative ballot)
Jan2008: committee ballot
May2008: membership ballot