Date
2017-04-20
...
Time | Item | Who | Notes |
---|
4 mins | | Former user (Deleted) | |
1 min | | All | Please review these blogs offline for current status on Kantara and all the DG/WG: |
1 min | - Status of Consent Receipt Specification v1
| Former user (Deleted) | - All Member Ballot is now open - closes on Monday, April 24, 2017
|
15 min | - Discuss myData team comments
| Harri Honko | Note from prior meeting: myData EU-based lawyer commented that the CR v1.0 draft has elements that are based on UK/US Common Law, rather than civil codes (GDPR) |
10 min | - Recap the Discussion of approach
| All | - FROM 2017-03-23 MEETING NOTES:
- - discuss approach and schedule for next round of specification enhancements
- a contributions period - a period of consolidation and combination of the contributions - a period of WG Editor work - Public review etc - confirmation of change request tracking tool (GitHub Issues unless strong objection)
Harri
Their EU-based lawyer commented that the CR v1.0 draft has elements that are based on UK/US Common Law, rather than civil codes (GDPR)- e.g. Consents have to be better atomized - so that over time, is there an accumulation of receipts? or accumulation of consents?
- The implementation detail might be: is there a concept of dynamic evaluation of consented purposes? Or is it static at transaction time? e.g. if a purpose or consent is changed at a later date, are the original receipts canceled and re-issued? is the original updated? is there a 'diff' receipt that only covers the different scope?
- Mary
- The caution about "Purposes lists" and "Sensitive data types" needs to be resolved - must be very cautious about how these are displayed to the user, especially if it's sensitive data - need to create recommendations
- Mark
- Need to set up a backlog - and define a work plan and schedule
- Set a date for CR v1.1
- Need to write guidance on spec usage
- Need consensus on
- Prioritization of backlog
- Need to consider any issues that are used for GDPR implementation
- The original agreement was to do 6-month epics
- Andrew to try to get the comments from the public review into github
|
40 30 min | Discuss work backlog priorities for CR v1.1 | All | Consent Receipt v1.1 Work Backlog - Discussed items 1-11 on the CR v1.1 backlog list
|
Parked notes about v1.1 approach from previous meetings:
- Mary
- The caution about "Purposes lists" and "Sensitive data types" needs to be resolved - must be very cautious about how these are displayed to the user, especially if it's sensitive data - need to create recommendations
- Mark
- Need to set up a backlog - and define a work plan and schedule
- Set a date for CR v1.1
- Need to write guidance on spec usage
- Need consensus on
- Prioritization of backlog
- Need to consider any issues that are used for GDPR implementation
- The original agreement was to do 6-month epics
|
|