You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 4
Next »
Date
2019-01-31
Status of Minutes
DRAFT
Approved at: <<Insert link to minutes showing approval>>
Attendees
Voting
Non-Voting
Regrets
Quorum Status
Meeting was <<<>>> quorate
Voting participants
Participant Roster (2016) - Quorum is 6 of 11 as of 2018-11-19
Iain Henderson, Mary Hodder, Harri Honko, Mark Lizar, Jim Pasquale (C), John Wunderlich (VC), Andrew Hughes (VC), Oscar Santolalla, Richard Gomer, Paul Knowles, Samantha Zirkin
Discussion Items
Time | Item | Who | Notes |
---|
4 mins | | | - EIC and Identiverse speaker proposals status
- Status: Wiki refresh work
- Status: Distribution-version of slide deck describing the work here (consent receipt today → personal data processing receipt tomorrow - or whatever we decide)
- Discuss EIC demo and scheduling
|
5 min | | All | Please review these blogs offline for current status on Kantara and all the DG/WG: There is a wiki page that will hold all the known implementations of Consent Receipts - Please update the page or inform Jim, or John, or Andrew of your implementation. - TIIME, Vienna, February
- EIC, Munich, May
- Identiverse, Washington, June
|
40 min | Product roadmap for the demo | All | Here's the project page for the "Demo v2" Andrew's thoughts on what to highlight: - The fact that giving the person tools necessary for them to keep records (the 'receipts') about their data controller & personal data processing interactions is a new thing in the world
- The ability for the person to take action because they have these records in their possession - the Privacy Control Panel
- The fact that interoperability standards allow many products to work in an 'ecosystem' way
- Even if the audience does not believe that the lawful basis of consent will become a mainstream thing, the person-side record keeping idea is a good one that has broad applicability
Decisions needed: - The specific set of user stories we want to showcase
- The roles that each product will cover in the demo
From the project page, the product roles were stated as: Role | Functionality | Product |
---|
PCP Dashboard | Dashboard |
| Receipt generator (API?) |
|
| Data controller application |
|
| Receipt management platform | Communication substrate - e.g. one possible function: when user clicks on button to exercise a data subject right, this calls the platform which sends instructions to the data controller to take action |
| Receipt Viewer app |
|
| Receipt language translator |
|
| Receipt storage facility |
|
|
the PCP dashboard, the data controller functionality to generate receipts, API platform provider, the ‘app’ used by the person, receipt viewer, receipt language translator, and so on. |
Deferred | Specification update approach |
| See a flowchart version of this here: https://share.mindmanager.com/#publish/b-DWOcuKGnVY1PXBKXTpL0-DQOeqmZMGfGUAPiC5 |
| AOB |
| Mark: Health Use case proposal
|
| Next meeting |
| *** Next call 2019-02-07 10:30 am Eastern Standard Time / 15:30 GMT https://global.gotomeeting.com/join/323930725
|