W3C

– DRAFT –
DPVCG Meeting Call

10 AUG 2022

Attendees

Present
chang, harsh, julian, mark, paul
Regrets
georg
Chair
harsh
Scribe
harsh

Meeting minutes

Previous minutes

All minutes

Consent Concepts

In the previous meeting, we discussed the concepts related to consent based on this proposal - https://lists.w3.org/Archives/Public/public-dpvcg/2022Jul/0003.html

The two concepts that did not reach an agreement were `Renewed` and `RequestDeferred` related to consent states.

Today's meeting discussed these concepts with agreement reached on the inclusion of both.

For `RequestDeferred`, we accept the concept, with a note that its use will be based on the use-cases' requirements

For `Renewed` as a concept, we discussed the ambiguity between renewal of given consent as well as indicating a prior refusal was "renewed".

The following options were considered for the concept - `RenewGiven` and `RenewRefusal`; `ReaffirmGiven` and `ReaffirmRefusal`.

The accepted terms for consent state are to have the prefix `Consent`, and `Renew` for a state that been renewed or reaffirmed.

This results in the following consent states - `ConsentUnknown`, `ConsentRequested`, `ConsentRefused`, `ConsentGiven`, `ConsentExpired`, `ConsentInvalidated`, `ConsentRevoked`, and `RenewConsentGiven`

The state related to renewal of a prior refusal (i.e. `RenewConsentRefused`) is kept at 'proposed' level and may be discussed in the future sessions when more information is available regarding its usefulness.

The concept `RenewConsentGiven` has been accepted due to its practicality based on mention in several authoritative documents, such as DPA guidelines (e.g. EDPB guidelines on consent) and the DSA's mention of periodic consenting conditions.

julian: Proposing `UpdatedConsent` as something to keep track of, with e.g. https://www.ibm.com/docs/en/watson-care-manager?topic=SSRMV7/com.ibm.iwcm.doc/care/t_cp_update_consent.html

We discussed and agreed to not include this concept as it relates to the management of consent records i.e. updating information within it, rather than to consent itself as its state

With this, we have discussed and agreed on the proposed consent concepts - these will be included in the next version of DPV.

When more information about ISO/IEC TR 27560 is available (e.g. in 1-2 months) an exercise will be undertaken to align DPV with the state of that standard, and provide guidance on using it.

chang: Suggestion to provide links e.g. in the spec or other docs or GitHub for how someone should provide comments, feedbacks, or ask questions/queries. For example, when looking at a certain concept - enquire about it.

harsh: These will be added as hyperlinks in a block/note at the start of the document welcoming comments.

Next Meeting

We will meet again in one week, AUG-17 13:00 WEST / 14:00 CEST.

Topic of discussion will include resolving other proposals, i.e. Rights, Rules, ISO standards, and any other issues on GitHub or added by members.

Minutes manually created (not a transcript), formatted by scribe.perl version 192 (Tue Jun 28 16:55:30 2022 UTC).