W3C

DPVCG Meeting Call

29 OCT 2024

Attendees

Present
beatrizEsteves, catarinaSilva, delaramGolpayegani, harshPandit, paulRyan, tyttiRintamaki
Regrets
-
Chair
-
Scribe
harsh, harshPandit

Meeting minutes

Repository: w3c/dpv

Meeting minutes: https://w3id.org/dpv/meetings

purl for this meeting: https://w3id.org/dpv/meetings/meeting-2024-10-29

Discrimination concepts

<ghurlbot> Issue 190 [Concept]: Discrimination Concepts in RISK (by coolharsh55)

accept concepts

Rights Impact concepts

<ghurlbot> Issue 184 Add Rights Impact concepts for each Right (by coolharsh55)

harsh: Question continued from last discussion: do we include requirements?

paulRyan: +1 merit in doing this work as it also helps meeting rights requests

beatrizEsteves: +1 agree with paul, it makes sense to model the whole process

paulRyan: its an area where we are weak in, we have worked a lot of DPIA and other processes, but never delved into what the processes actually are

tyttiRintamaki: +1

delaramGolpayegani: +1 might be helpful for fundamental rights impact assessment under the AI Act

catarinaSilva: +1

conclusion: group agreed that we should include requirements for rights and other processes in general. This requires further discussions and exploration of concepts / methodology, so we will do this for DPV 2.2.

Guide for Machine Actionable Rights

<ghurlbot> Issue 191 Create a guide for Machine-Actionable Rights (by coolharsh55)

beatrizEsteves: submitted what I had for materials to DPV dev branch on github. Next steps is to create a sequence diagram for what is involved in exercising a right - what we discussed last time with Georg. It would be good for people to go over it and start a discussion on it.

DPIA concepts

<ghurlbot> Issue 183 Represent activities where DPIA is required in EU-GDPR (by coolharsh55)

tyttiRintamaki: concepts are done - to be reviewed by harsh; will submit on Github for people to review and discuss; there are some issues that require inputs from people

harsh: then we put it on the agenda for next week (tytti: yes)

paulRyan: there are two steps in DPIA where the first one is whether a DPIA is needed e.g. EDPB guidelines on what needs a DPIA

tyttiRintamaki: yes, I have factored in all EDPB and EU/EEA DPA guidelines

Integrating AIRO/VAIR

<ghurlbot> Issue 143 Integrate AIRO/VAIR concepts for AI and AI Act vocabulary (by coolharsh55)

delaramGolpayegani: mapping of AIRO to VAIR - wording is different e.g. risk mitigation and risk control

delaramGolpayegani: we also need to check/map risk controls in DPV

harsh: we have measure to follow the legal meaning of mitigation measure and risk ontology/extension has the generic term control used in risk management

delaramGolpayegani: there is a concept called detectsRiskConcept as it refers to detecting events which in DPV are modelled as risk concepts (so they can take up multiple roles)

harsh: lets call it to detectsEvent?

delaramGolpayegani: not great due to temporal connotation of 'event'

harsh: lets go with what you have for the moment

delaramGolpayegani: for domains - the criticial infrastructures have been modelled as concepts

delaramGolpayegani: if we don't have domain then for some purposes e.g. determining high risk and prohibited AI or technical documentation - DPV won't be sufficient on its own

harsh: we use it with NACE?

delaramGolpayegani: does it have a formal representation?

harsh: yes, in RDF! https://data.europa.eu/data/datasets/nace2-1?locale=en

delaramGolpayegani: specific parts of AIRO/VAIR will be going in to specific extensions

delaramGolpayegani: area of impact - how to model this? As sector? Is it different?

delaramGolpayegani: ai subject - how do we model this? It is not the same as data subject.

harsh: how do we reuse data subject taxonomy as we already have a nice list there?

harsh: option, we define human subject and move concepts there - but that will break existing uses of data and we should ensure minimising any breaking changes. Will need to think about this.

14: 55:35 <harsh> delaramGolpayegani: human involvement concepts are present - but not explicitly for humans only

harsh: these are generalised as entity involvement, but we don't have

Next Meeting

next meeting will be in 1 week on TUESDAY 05 November at 13:30 WEST / 14:40 CEST. Agenda will be discussing AIRO/VAIR integration, selecting the next set of items/issues on GitHub with any updates on github/mailing list and AOB.

Minutes manually created (not a transcript), formatted by scribe.perl version 217 (Fri Apr 7 17:23:01 2023 UTC).