Status of Minutes
Approved at: <<Insert link to minutes showing approval>>
- Paul Knowles
- Jan Lindquist
- Sneha Ved
- Tom Jones
- Colin Wallis
- Peter Davis
- Julie Maas
- Sal D'Agostino
Meeting was <<<>>> quorate
Participant Roster (2016) - Quorum is 5 of 9 as of 2018-07-12
Iain Henderson, Mary Hodder, Harri Honko, Mark Lizar, Jim Pasquale, John Wunderlich, Andrew Hughes, Oscar Santolalla, Richard Gomer
- presentation from Peter Davis - Airside Mobile on their planned implementation of Consent Receipts
- discuss the road map - are there high priority items?
- discuss ideas for EIC May 2019 demo and other talks
Please review these blogs offline for current status on Kantara and all the DG/WG:
There is a new wiki page that will hold all the known implementations of Consent Receipts - Please update the page or inform Andrew of your implementation.
- CIAM World Amsterdam - Keith Uber presented the demo - 30-40 people
- ISSE Brussels (EEMA) - Oscar Santolalla presented the demo - 20+ people
- TIIME, Vienna, February
- EIC, Munich, May
- Identiverse, Washington, June
|30 min||Roadmap ideas for Kantara CIS WG products||All|
Continuation of the discussion about 'what should interoperate?'
Some food for discussion:
- If we believe that the CR should be adjusted to enable general use for any legal basis for processing, what steps are needed (where are the requirements? what are mandatory/optional features? etc)
- Transformation of the specification into a "Notice Receipt"
- If we believe that 'consent' will become an peer with the other legal bases for processing, then maybe we should leapfrog and look at requirements from ePrivacy Regulation, and take an affirmative position in the marketplace that Kantara Consent Receipts are designed to be fit-for-purpose to address ePrivacy, GDPR and GDPR-similar regulations.
- Document use cases from specific companies - to give us focus
- Realign thinking towards "Consent Sharing & Information Sharing"
- Is there support in this WG to use the "Contract Law" concepts as the scaffolding/framework for future development of the "Kantara receipt" construct?
The use cases described last week (in addition to the ones in the github repo) were:
- Privacy Dashboard
- Evidence of Action
- Agreement Details and Transaction Records
- Standardized Message Data Structure
- Having the concept of "contract" would be helpful
- GDPR pushes to get away from "data as currency" - the purpose for the interaction is paramount and should be the justification for the 'consideration'
- Be very cautious that applying the Contract Law metaphor could overly influence our thinking about how we design and apply consent
- Address the taxonomy of privacy, notice, control
From 2018-11-08 call:
From 2018-11-01 call:
Andrew led the group through a discussion looking at the central 'agreement' between data subject and data controller in light of basic concepts of Contract Law in the Common Law to see what patterns and insights are available
Andrew has uploaded some material to help the discussion: Product Roadmap Ideas
Blog: Kantara Initiative Work Groups on Data Sharing and Consent
Mind map to go with the blog
Kantara consent high level use cases.pdf
|0 min||Interoperable Consent Receipt roadmap ideas||All|
From 2018-10-04 call:
- If the legitimate basis is not 'explicit consent' - but rather legitimate interest, is the concept of 'data receipt' still viable?
- Mark - yes, the current CR was designed to be not confined to 'explicit consent' - so yes, the receipt concept will work for other bases for processing
- in particular - for updates to privacy notices
- Mark Q: would it be interesting to have additional values for the 'consent type' field? A: YES!
- Jim: maybe this should go to the Consent Management WG?
- A lawyer at the Seattle event pointed out that it would be useful to capture the actual privacy notice that was agreed by the user.
- OpenConsent has an alpha product that might suit the purpose
- There is a systemic problem that needs to be addressed - and capturing the privacy notice won't actually help
- If there is a strong need for a high value receipt, then it would be very useful to capture the actual notice text
- So maybe the receipt could have optionality to allow for capture of the notice text.
- WG needs to take some time to discuss the UX - schedule it
- Tom has posted some examples that could be discussed
- Mark - OpenBanking has posted UX guidance
- Schedule specific multiple calls for this to discuss what the user should see, and how this translates into the 'receipt' concept
- Should this WG do a spec or guidance on UX or UI?
- Should this WG talk about what the 'receipt' means and / or represents?
- (YES to both question)
- Andrew: suggests first design call on Thursday October 18, 2019 and then every 4 weeks to be kind to the down-under-ers.
Iain: the highest value work item is the lexicon work
|5 min||Adding feature requests to next version of spec family||All|
- Andrew has set up a github repo for next-version specification backlog items, including use cases:
- Some possible items for next versions:
- Structural changes to the spec including a hierarchy of objects that should improve high transaction volume
- Integration/association of the new Blinding Identity Taxonomy into the CR Spec family
- Recommendations for Customer Journey / UX / UI features
- Library of industry-specific or case-specific Purpose categories and example Purpose statements
- Expansion of Consent Types to allow for more than just Explicit Consent situations
- (idea) Optional receipt metadata to assist privacy dashboards in organizing and processing 'bring forward' items (e.g. "remind me to check this share in 3 months")
- digi.me product and management have identified six areas for development
- consent over period of time (rather than instantaneous consent)
- termination/modification of consent from either side
- high transaction volume & low per-instance cost
- how the 'receipt' fits into accounting systems infrastructures
- receipt as the basis for legal matters and actions
- UX/UI concerns
- for Clinical Trials uses, data holder is required to keep data for 10 years - need to consider longevity of the receipts to go alongside data holdings
|10 min||Product roadmap for the demo||All|
*** Next call 2018-11-15 10:30 am Eastern Standard Time / 15:30 GMT