|30 min||Roadmap ideas for Kantara CIS WG products||All|
Continuation of the product roadmap discussion...
From the 2018-11-29 call:
- Andrew walked through the mindmap of choices
- After thinking about it and discussing, we will have to do things related to Use cases, Spec updates and 'recommended lists' in coordination with each other
- WG will think about work areas that are critical to support their product directions/plans
- It is essential that individuals take on leadership of work that they have a direct stake in successful completion
- We discussed use of a simple use case format and approach. Andrew pointed to the pages at the DG for ID Proofing Use Cases: Use Case style and instructions
From the 2018-11-22 call:
Let's look at a few appraoches to deciding on what happens next:
- Specification structure changes & fixes
- For example: adding 'object hierarchy' (digi.me), any field data types that turned out to be incorrect, other feedback from implementers
- For example: adding capability for 'system-added' additional data to preserve custom data from specific implementations
- For example: changes needed for signing, encryption, key management, Decentralized Identifiers, Verfiable Credentials,
- Specification 'data dictionary', 'pick lists', 'recommended lists' (is this the 'Lexicon' item?)
- For example: Purpose categories, purpose lists, data categories, taxonomies (Blinding Identity Taxonomy) & ontologies
- For example: Integration/association of the new Blinding Identity Taxonomy into the CR Spec family (to inform implementers of potential data categories of interest)
- Full exploration of one or two use cases - to inform/supply specification changes and additions above
- This should include building prototype, demo or actual software that uses the updated specification material
- For example: think about extra stuff that a well-functioning 'privacy dashboard' would need.
- For example: using the 'receipt' concept for record-keeping the full 'Agreement'
- For example: using the 'receipt' for any/all legal basis for processing, not just 'consent'
- For example: pick any actor in the system and build out all the stuff they require in the overall system (what would an external record-keeper-provider need to have?)
- For example: analysis and enhancement for use of Receipts in court/evidence
- Direct sharing and concept integration between CIS WG and other consortia WGs
- For example: Hyperledger Indy Semantics WG (was Sovrin foundation Schemas & Overlays WG)
- For example: W3C community groups (Credentials CG, Decentralized Identifiers CG, Data Privacy Vocabulary CG)
- For example: IEEE P7102 Machine readable privacy terms; IEEE P7002 Data privacy process (privacy engineering)
- For example: ISO 29184 Privacy Notices and Consent; ISO P317 Privacy by design (consumer products)
- 'Protocols' specifications
- A three party consent-data-exchange - a protocol definition/specification
- What about an API definition?
- What about 'Negotiation' interaction models, protocols, etc
- Other ideas
- Application of the Consent Receipt in IAB "Consent Management Solution" infrastructures
- Integration of 'Consent Receipt' into Hyperledger software proposals (See HIPE - Consent Receipts for Hyperledger Indy)
- Recommendations for User Experience / Customer journey
- Schema Overlays for data presentation transformations (like localization/language translation)
- There needs to be a common design paradigm for data sharing of/for/about an individual - so that systems implementers, designers etc can work together. For example: jlinc.com
- Data/information management guidance - how does the receipt align to the actual data it came from?
Prep material for 2018-11-15 call:
A new flow chart showing a generic 'agreement-oriented' viewpoint:
Andrew's email to prepare for this call:
These are some of the questions that came to my mind, to ask at the flow chart steps:
* At each point in timeline what data is offered or consumed?
* What information and metadata should persist? (to record keeping)
* Under different legal bases what information should be provided to the individual?
* What happens at first use? Does something different happen at subsequent use?
* What information is needed to exercising a data subject right? (and is that information recorded anywhere?)
From 2018-11-15 call:
- Sneha notes that their flow is more party-party-consent manager - so the high level 'agreement' flow chart needs adjustment
- Andrew: Yes. The generic flow chart is intended as a starting point - more specific ones will be developed for different use cases
- Andrew walked through the flow chart
- Q: is the idea of a third party record keeper archivist in play?
- A: yes - not at this level of detail - because this flow chart does not show who is performing the action, just who is responsible for the action
- Discussion ensued
- Analysis of any particular use case using the flow chart as a tool
- The details of what records should be kept are specific to the use case being analysed
- We will build out a taxonomy of use cases that we analyse
- General sense of the room is that this is a good base model from which we can derive specialized flow charts to suit any use case
From 2018-11-08 call:
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-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
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