W3C

DPVCG Meeting Call

06 FEB 2025

Attendees

Present
beatrizEsteves, harshPandit, julianFlake, julioHernandez, markLizar, mayraRusso, mugdhaKhedkar, nihadAtakishiyev, paulRyan
Regrets
delaramGolpayegani, georgKrog
Chair
harsh
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-2025-02-06

v2.1 release

<ghurlbot> Issue 198 DPV v2.1 release management (by ghurlbot)

v2.1 release candidate with open review until FEB-16; see https://lists.w3.org/Archives/Public/public-dpvcg/2025Feb/0002.html and w3c/dpv#235 for hotfixes

AI Training

<ghurlbot> Issue 82 Provide vocabulary to specify purposes and permissions related to AI training (by scottkellum)

continued discussion from last meeting on whether specifying concepts related to AI training should be within the scope of DPVCG

harsh: AI training concepts are currently missing - they are necessary to state e.g. ODRL policies to state whether AI training is permitted or prohibited

beatrizEsteves: we had the AIUP paper with Delaram which had concepts related to training for use with ODRL profile AIUP: an ODRL Profile for Expressing AI Use Policies to Support the EU AI Act https://ceur-ws.org/Vol-3759/paper17.pdf

harsh: Yes, that paper has some concepts related to AI use, and it uses VAIR http://w3id.org/vair to state AI training. But that concept is a broad concept representing training, whereas we should state granular concepts for specific kinds of training e.g. there is fine-tuning which takes an existing trained model and applies more training on it. So the proposal here is to provide such a taxonomy for use with DPV.

beatrizEsteves: +1 to include concepts

iainHenderson: +1 to include concepts

paulRyan: +1 to include concepts

agreed to include it in scope; next step is to create proposed concepts and discuss them

Subjective Locations

<ghurlbot> Issue 209 [Concept]: `AtX` subjective Location concepts (by coolharsh55)

continued discussion from last week on adding subjective locations e.g. home, work, park, school

iainHenderson: +1

paulRyan: +1

markLizar: what is the context? Where does this requirement come from?

harsh: e.g. for GDPR there is a DPIA condition regarding CCTV in public spaces - so how do we model a public space like a park is what these concepts are for

paulRyan: did we model GDPR exemption for personal processing?

harsh: no, we don't have that in DPV as of now

markLizar: we worked on public space CCTV notices where this would be of use

harsh: should we do public/private categorisation as Mark suggested last week?

markLizar: yes but it should be public, private, and personal - so three categories

harsh: okay, we are going for legally relevant categorisations such as publicly accessible areas, but there are nuances e.g. a hotel lobby is a private location that is publicly accessible and is considered as a public area in some contexts - so we should also consider these e.g. as publicly accessible private areas

markLizar: home/office is private, retail is semi-private - so there are useful categories to work with

harsh: agreed, though what should be granularity? How do we decide what concepts to model?

harsh: what about virtual locations? within device exists, so e.g. within app and so more can also be useful here

iainHenderson: +1 I’d be inclined to add virtual locations; e.g. on a specific website, in an app, on a server

agreed to include these concepts as proposed, and to discuss specific location concepts as a proposal

Inverted Locations

<ghurlbot> Issue 208 [Concept]: Add Non-X (X = specific location) to represent locations that are not X (by coolharsh55)

Continued discussion on "inverted location" i.e. non-EU location for locations that are not EU

beatrizEsteves: +1, would be useful for ODRL

iainHenderson: +1, 'not' in option would be good to explicitly indicate not being in a location

Tentatively agreed to consider these locations, next step is to discuss with a concrete proposal

AOB

Data Categories from IAB/Google

harsh: proposal with Iain, Add IAB, Google data taxonomies under PD e.g. pd/iab, and pd/google as they are widely used? (DPVCG would still interpret them with sensitive information, special categories, etc. in addition to whatever is present in them)

iainHenderson: would be better to discuss later with more concrete ideas

EHDS extension

beatrizEsteves: want to EHDS extension for PACSOI project; how does it work with Health Sector extension?

harsh: not fixed yet, but my thoughts are that we have DPV Purpose as core concept, Health Sector extends them for health specific concepts, and then the EHDS extension extends the Health Sector concepts

beatrizEsteves: what is the status of the extension? It needs to be updated, and I am interested in doing that for the PACSOI project

harsh: yes, it needs to be updated. Georg was working on it. Best way to know would be to email Georg, CC me and we can see how to update it.

harsh: btw, does Belgium have a national health regulation aligned with EHDS, similar to how Ireland got the Health Information Bill last year which is aligned with the EHDS regulation - knowing these would allow us to decide how to model national laws for health data spaces in a way that links them to EU EHDS

beatrizEsteves: not sure about the national law here, there are people working on the health projects who might know

Call for User Participation

nihadAtakishiyev: joined recently, conducting a MSc research project at Uni. Paderborn with Mugdha where we are using DPV

mugdhaKhedkar: we are conducting research at uni. paderborn and want to propose concepts from work on android apps where we are exploring automation of DPV generation for android apps. We are conducting a study for this to understand what data is being collected and representing that based on DPV https://www.hni.uni-paderborn.de/sse/lehre/user-study-automating-android-privacy-assessments#c930114

Next Meeting

The next meeting will be on FEB-13 Thursday 13:30WET/14:30CET and will be chaired by Beatriz

Agenda will be continuing discussion on topics started under v2.2

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