2015-01-22 Meeting Minutes

Owned by Mark Lizar (Unlicensed)
Last updated: Feb 05, 2015 by Former user (Deleted)
2 min read

Minutes approved 5 February 2015

Date

Jan 22, 2015

 

We have quorum

Highlights

  • Motion to Make Heather Cheif Editor was passed
  • Motion to make Ann Racuyna-Robbins an associate edior (once she is on the participant rossitor) 

Simple Objectives: To create/develop CR fields, format requirements, and rules for use

  1.  MVCR spec 
  2.  json model and the 
  3. Use case Document: Consent Recipts for websites

Agreed Plan is to put these three together for development brief

Attendees

Call Notes/Agenda

    1.  Roll Call & AOB
    2. Action Items 
      1. GIT Hub is setup, 
      2. Everyone start to edit via git hub
    3. Editor Nominations: We had some nominations last week for editor positions that we need to  vote on. 
      1. Motion to make Heather cheif editor and this was seconded by Iain and passed
      2. Motion to make Ann  associate editor and this is passed.
    4. Git Hub setup and running, a  v.06 of MVCR is now in Git Hub and a process is started to review and edit this version this week. 
      1. Action: Mark Lizar (Unlicensed)Create Use Case Document
      2. Action:  Mark Lizar (Unlicensed) : Clean up spec
      3. Process - we keep the forks of this to the minimum by discussng the issues on list. Review De-Mystifing the Consent Receipt - Values, Benefits and Claims for background. 
      4. splitting v.06 into multiple and/or sub-documents and schedule review. 
        1. Mark Lizar (Unlicensed) - Action item to sepeate use case
        1. Subcategories
          1. Core Spec
            1. Core Fields and their Format
            2. Contextual Checklist
            3. Consent Legal Framework
            4. Terms of Service
        2. Receipt UI
        3. Case Studies + Implementations
        4. Actions For Next MTG:
          1. Focusing on  data fields
            1. What would be format, what is optional and what is not.  Rule 
          2. 3 items for Developer Brief - Create json Model, Then we take 1. spec and the 2. json model and the 3.use case and give to developer for brief. 
    5. 10 Min Update
        1. IDSEG - Submitting terms and look for how to display the Consent Receipt in this context
        2. Joni- Response about removing barriers to working with MVCR in IDSEG and so it can act as an SDO or, something similar to sponsor MVCR with IDSEG
          1. Joni is working on what is an SDO. Kantara is already using an open standard principles that we can use to illustrate how this work can be placed and used. 

Action: Former user (Deleted) to provide report that is being drafted on standard submission requirement.  2 weeks update that draf


    1. Process for Calls with Git Hub : We will develop these as we go.
      1. We can take comments any and all ways, from Git Hub,  Wiki, mailing list. 
      2. Work on some Git Hub Instructions if possible.

.

 Action Items

Seee Actions above