WR220070525telcon
Wrappers R2 project telcon
Friday 25th May 11am ET Phone Number: 702-894-2444 Participant Passcode: 984125 https://www.gotomeeting.com/join/369287397 gotomeeting Meeting ID: 369-287-397
Contents
Agenda
Admin
- Approve notes of previous meeting WR220070518telcon
- Agree scribe
- Introductions and roll call
Balloting Admin
- Intent to ballot submitted
- Review Project Scope Statement
- Do we need a publishing facilitator for the project?
Editors for documents
We need to agree who will take a lead on making changes to the documents
- MCCI Message Control Infrastructure
- Dale Nelson
- ...
- CACT - MCAI Message Control Act Infrastructure
- Charlie McCay
- ...
- CACT - MFMI Master File / Registry
- CACT - QUQI Query Infrastructure
Project objectives
- Are we going for DSTU or committee ballot in Jan -- if DSTU then when do we expect to do a membership ballot?
- Project page - MCCI/CACT R2 Project
Notes from call
Present: Mark Tucker, Dale Nelson, Charlie McCay, Vassil Peytchev
Noted that because we do not have an INM co-chair this cannot be a formal committee meeting - therefore any decison needs approval on a formal INM call. We will continue to seek co-chair engagement.
Dale agreed to be publishing facilitator. To be approved by INM
Mark Tucker agreed to be Query editor, and Vassil agreed to be listed as Master files editor.
At this stage we do not believe that there are any Master file specific changes that are required in R2, but that changes to the control act wrapper approach will need to be carried across into the master file specifications.
Dale to confirm tooling requirement for next week. Editors will need to establish whether they can edit material from R1, or would be better to start from scratch with new Visio diagrams and databases.
What goes in conversationId? Could be a DSTU question – capture requirements from implementation Action CM to start thread on INM and implementation to ask for requirements and use cases, so that some description can be provided.
Agreed to use “trigger event grouper” approach for the behavioural wrapper.
RecordTarget (and other control act wrapper material) -- is this conducted (ie can it be made optional in the payload ) action CM – start thread.
Action CM – send scope statement to the list – for onwards submission to HQ.
Agreed that “Scope of Wrappers R2” would be the page that keeps the full list of all the changes that are part of wrappers R2, and that “MCCI R2” and “CACT R2” pages will be rolled into that, or split into specific issues that are linked to from it.
CM will not be on the call next week.
