W3C

DPVCG Meeting Call

29 JUN 2023

Attendees

Present
beatriz, delaram, georg, mark, paul, ted
Regrets
harsh
Chair
beatriz
Scribe
beatriz

Meeting minutes

Repository: w3c/dpv

Data Breach extension

review of data breach document

see email: https://lists.w3.org/Archives/Public/public-dpvcg/2023Jun/0003.html

see document: https://harshp.com/dpv-x/data-breach/

ghurlbot, get #64

<ghurlbot> Issue 64 Provide concepts for Data Breach (coolharsh55)

review by: georg, paul, julian

georg and paul went through the data breach document.

georg: two issues: (1) include in the document the examples mentioned in EDPB’s guidelines on data breaches and (2) align the labeling of the data breaches notification concepts with the NIS 2 directive

ACTION: Include EDPB examples in the Data Breach document

ACTION: Investigate NIS2 notification concepts for use with Data Breach notifications

paul: agree with these suggestions; is it possible to check a spreadsheet with the data breaches concepts and its definitions

ACTION: Create spreadsheet with Data Breach concepts

ACTION: Finish sections 7 to 9 of data breaches document for people to review it for next week’s meeting

Impact of changes from DGA

paul: ghurlbot, get #62

<ghurlbot> Issue 89 Add DGA/eIDAas entities (coolharsh55)

paul: There was an agreement between the participants that the best course of action would be to change the labels of the terms from personal data to ‘any’ data and do it as soon as possible.

ted: (and mark) how to make a distinction between what is personal or non-personal data, this might change according to the context, might be something that is out of scope for the activities of the group but the general feeling is that it is worth to discuss it

paul: what is going to happen with the personal data handling concept and all the properties that connect it with the other taxonomies – should be model a higher level concept for ‘any’ data handling and a non-personal data handling?

Consensus was that this should be something that we define as soon as possible to move forward with the work on DGA and other regulations

mark: is it in the scope of DPV to model secondary uses of data?

ACTION: Finalise decisions on the impact of proposed changes from DGA modelling

Multilingual Translations

ghurlbot, get #89

<ghurlbot> Issue 89 Multi-lingual labels and descriptions for concepts (coolharsh55)

No updates

Data Governance Act

ghurlbot, get #62

<ghurlbot> Issue 89 Add DGA/eIDAas entities (coolharsh55)

Proposed terms for DGA have been moved to dpv repo under dpv-dga, see PR by beatriz w3c/dpv#97

ghurlbot, get #97

<ghurlbot> Issue 97 add proposed terms from DGA (besteves4)

PR by Ted accepted - it fixes typos and other minor corrections

ghurlbot, get #98

<ghurlbot> Issue 98 Fix various typos and such (TallTed)

Shared spreadsheet with participants to review concepts and their definitions.

There was an agreement on adding the processing operations to the main DPV spec.

Discussions around the usage of altruistic purposes – there was an agreement of separating the ‘data altruism’ concept from the purposes themselves and use both concepts simultaneously to flag an altruistic purpose, i.e., ex:altruisticScientificResearch rdf:type dpv:DataAltruism, dpv:ScientificResearch.

ACTION: Participants will review DGA concepts for discussion next week

Next Meeting

The next meeting will be in 1 week on JUL-06 at 14:00 WEST / 15:00 CEST.

Topics for discussion will include (1) Review sections 7 to 9 of data breaches document; (2) Impact of proposed changes from DGA modelling; (3) Review DGA concepts.

Summary of action items

  1. Include EDPB examples in the Data Breach document
  2. Investigate NIS2 notification concepts for use with Data Breach notifications
  3. Create spreadsheet with Data Breach concepts
  4. Finish sections 7 to 9 of data breaches document for people to review it for next week’s meeting
  5. Finalise decisions on the impact of proposed changes from DGA modelling
  6. Participants will review DGA concepts for discussion next week
Minutes manually created (not a transcript), formatted by scribe.perl version 217 (Fri Apr 7 17:23:01 2023 UTC).