2015-07-30 Meeting Notes - Quorate-Read IN

Date

Jul 30, 2015

Attendees

• @Mark Lizar (Unlicensed)

• @John Wunderlich

• @Former user (Deleted)

• @Former user (Deleted)

• @Former user (Deleted)

• @Colin Wallis (Unlicensed)

Agenda

• Administrative
  - minutes approved For
  - June * 2015-06-08 Meeting Notes - Quorate
  : https://kantarainitiative.org/confluence/display/infosharing/2015-06-08+Meeting+Notes+-+Quarate
  - July * 2015-07-13 Meeting Notes - Quorate: https://kantarainitiative.org/confluence/display/infosharing/2015-07-13+Meeting+Minutes%3A+Quorate
  
  
  MVCR Review
  Item 1: Purpose Specification & Sensitive Information - changes - agreed for specification but not for implementation

• check these boxes and add other categories based on your understanding of your jurisdictions sensitive information.

• Item 2: Re-Order & Review : - send to list and agree in quorate call - agreed for specification

• Item 3: Update of Table for Documentation and for the Specification - agreed to clean up and go with current table
  
  Item 4:  Editing the MVCR v0.7 -
  Action Approval to format it with above changes,
  
  

  • terminology iterative dev, 

  • remove stakeholders,

  • Clean up appendix

• Editor Action Add
  
  

  • Under Core Profile - design principles - functional objectives, 5 section over view, updated core profile table

• UUID  - brought up by John, but not recommended by Justin

As this is still new, we are still drilling down into language and specific ways to discuss certain items, in this regard we discussed the current topic list in consent receipt work

• Current Topic List
  
  

  1. Data Model

  2. Specification: Documentation

  3. API

  4. Consent Receipt Generator input fields api.cr.org

  5. Rendered Out Put on api.cr.org

  6. api.cr.org Documentation

  7. Consent Receipt ) JWT

  8. Consent Button on client website using CRG API

  9. Rendered Consent Receipt on client webiste

In order to update/ further dev - api.cr.org, and the data model and the rendered receipt output on api.org, a scope of work for what needs to be done has to take into account how to reference  different components above.

There was suggestion that we do not do any more dev work until v0.9, Mark said that we need to do the dev work for Item 1, right way,

This has left an outstanding action for Item 1.  As far as I can tell in order to  update the Demonstrator and the next implementations to the MVCR v0.7 Alpha, with the new purpose sepcification and the sensitive data categories, it appears that these elements all need to be referenced in a scope of work, a quote needs to be received to do this work, and then this needs to be agreed in a quorate meeting. 

Mark & John have taken action to write this scope of work.

Discussion Items

Action Items