Skip to end of metadata
Go to start of metadata

Date

2018-09-20

Status of Minutes

DRAFT

Approved at: <<Insert link to minutes showing approval>>

Attendees

Voting

  • Andrew Hughes
  • Oscar Santolalla
  • Iain Henderson
  • Jim Pasquale
  • Mark Lizar

Non-Voting

  • Derek Munneke (Meeco)
  • David Turner
  • Marvin van Wingerde
  • Colin Wallis
  • Brent

Regrets

  •  

Quorum Status


Meeting was <<<>>> quorate


Voting participants


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

Discussion Items

Time

Item

Who

Notes

4 mins
  • Roll call
  • Agenda bashing
5 min
  • Organization updates
All

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.

Planning a Member Plenary meeting October 26-ish San Francisco (Friday after IIW)

  • Are there specific cross-group items you'd like to propose to work on?
30 minInteroperable Consent Receipt roadmap ideasAll

See the data flow sketch that Andrew circulated by email

This diagram shows ALL data flows, despite the legitimate basis for processing. The idea is that given this data flow diagram, what are the functions, nouns and verbs for each of the legitimate bases?

Q: How would enforcement work?

Q: What's the difference between 'observe' and 'surveil'? A: Depends on if the user is aware of it or not.

Also see from our archives:

https://kantarainitiative.org/iain-henderson-the-personal-data-eco-system/

The 'my data', 'our data', 'their data' view

Comment Brent: in a social network, what roles do the different actors take? eg if I share an image, what role does the website take, what role do the users who can view my image take? also, how do I represent those rules where I restrict access to my data based on roles or groups I assign to my connections? how do I represent that implicit consent using consent receipts without knowing explicitly who I am granting permission to?

Comment: This picture looks very corporate - must ensure that the individual's perspective is very clear

Comment: The 'interface' for the individual should not be the 'consent receipt' itself - but rather the interaction with the service.

JLINC perspective: Alice grants permission and organization seeks consent. Alice only sees permissions.

Comment: this discussion is oriented towards 'explicit' consent. But all interaction has some level of agreement.

Iain: the highest value work item is the lexicon work


0 min

Permissions v User Consent discussion

notes from From 2018-09-13 call

All

Proposal:

Permission = Authorization to act

Data Permissions = the functional actions that are allowed on information (database: Create, Read, Update, Delete; communications: Copy, Transmit, Store; data flow: Collect, Use, Disclose) or resources.

User Consent = Voluntary agreement by the person to take an action. GDPR includes 'unambiguous'

  • So, a system might be authorized to act on personal data with or without a user's agreement. A person may grant permission or authorize a system to act on personal data.

Questions:

  • Is an OAuth 'consent' / 'authorization' / 'permission' dialog box truly 'user consent'?
    • If it is not 'user consent' then why not?
    • So: the process of obtaining agreement from the user in the OAuth dialog box is "User Consent". What the user has agreed that you can do with their resources is "authorization" in the sense that they give you 'permission' to take actions.
  • How does this apply to Collection, Use and Disclosure of information? (these are the data flow words)
  • To tease out the usable definition of 'authorization': What is the difference between Authorization and Access Control? (data & systems-context)
    • Authorization is the granted right to proceed (a.k.a 'permission')
    • Access control is the functional actions that are allowed

Alternative proposal:

  • Permission is a general authorization to act. Authorization may be granted by actors that are not the data subject.
  • Consent is a specific agreement to act in a limited case.

Note:

  • Permission / authorization as a verb can be granted through an act of user consent.

Another proposal:

  • Should the terms should be Authorization and User consent
5 minW3C workshop on User Consent and Permissions September 26, 2018Andrewhttps://www.w3.org/Privacy/permissions-ws-2018/schedule.html
5 minAdding feature requests to next version of spec familyAll

AOB

Jim: suggests that we formally agree on the 'permissions v user consent' descriptions/explanations and circulate to other interested associations and working groups.

Iain: let's resurface our existing lexicon/terms that have been developed over time and publish


Next meeting

2018-09-27 Same time same number (Andrew not available next 2 weeks)



 


1 Comment

  1. In terms of Explicit Consent or opt-in - this is the agreement that is made at the point of first engagement where personal data is provided and permissions are used in the relationship to maintain the state of explicit consent.