DPVCG Meeting Call

Repository: w3c/dpv

Agenda: https://www.w3.org/events/meetings/ce42ad87-3040-4f82-a341-7cb7c699a1a4/20251119T133000/

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

Persistent ID for current minutes: https://w3id.org/dpv/meetings/meeting-2025-11-19

Previous minutes: https://w3id.org/dpv/meetings/meeting-2025-11-12

Admin

DPVCG Charter

<ghurlbot> Issue 399 Establish DPVCG Charter (by coolharsh55)

HarshPandit: Working document: https://docs.google.com/document/d/1poo7rYNBlkd4Ag0YHB_il2Xe2hwtHWfROgl5WgrNgyc

HarshPandit: do we continue with the simple approach as discussed in the last meeting?

IainHenderson: +1

JulianFlake: +1

agreed on structure of DPVCG charter

ACTION: Circulate draft of DPVCG charter - Harsh

W3C reports

<ghurlbot> Issue 363 Submit DPV v2.1 to w3c cg outputs for normative purls (by coolharsh55)

<ghurlbot> Issue 364 Submit v2.2 to w3c cg repo for normative purls (by coolharsh55)

HarshPandit: WIP (to modify prior versions with red outdated box - checking the procedure)

ACTION: Submit v2.2.1 and v1, v2, v2.1 with changes to w3c - Harsh

ACTION: Fix #406 primer links when submitting to w3c - Harsh

Improve Main Spec

<ghurlbot> Issue 395 Revise DPV main spec page for ease of access (by coolharsh55)

Harsh initial simplification proposal at https://harshp.com/dpv-x/dpv-simplification/dpv.html

HarshPandit: some technical issues with links redirection, to be solved with custom js

ACTION: Implement the revised main spec

Examples, Use-Cases

<ghurlbot> Issue 12 Use-Cases and Examples showing how vocab can be used (by coolharsh55)

HarshPandit: Our previous use-cases page exists at https://w3c.github.io/dpv/use-cases/ Do we do these per (ontological e.g. purpose, and not taxonomical e.g. marketing) concept or do we do these in general for large groups of contexts? (my preference is for coverage as a priority, so high-level that covers all existing concepts and then we can have more use-cases later)

JulianFlake: +1 broad approach is good otherwise we have lots of concepts and overlaps

agreed to continue with examples as currently done, for use-cases to focus on the high-level coverage

ACTION: Add examples and use-cases guidance

Mapping laws

<ghurlbot> Issue 186 Create Mapping between GDPR and DPV (by coolharsh55)

JulianFlake: - HarshPandit: should https://dev.dpvcg.org/2.3-dev/legal/eu/gdpr/#mapping be expanded to article by article analysis?

DelaramGolpayegani: +1 article by article would be helpful, would be nice to know how much of the GDPR articles are covered by DPV

StratisKoulierakius: +1

JulianFlake: is this GDPR → DPV or DPV → GDPR (Harsh its GDPR → DPV).

HarshPandit: We have source references to GDPR

JulianFlake: Source is different, concepts is also mapped to different articles (but +1 to go with article by article) For Art.4 this is definitions so this is an exact match as it exists in DPV but for other concepts this is not clear

HarshPandit: so this would be e.g. Art.35 has DPIA concepts and there is also guidance with links

JulianFlake: having mappings from article to concepts or even to guide / topic documents is good (e.g. for DPIA, ROPA)

DelaramGolpayegani: It would be good to state DPV covers all definitions in articles; we should look at whether there are SHACL shapes and SPARQL queries to represent the mappings

HarshPandit: I am thinking we put this in HTML for people to see for a given article where to look for concepts, if there is somrthing in main DPV, something in EU-GDPR, guidelines or examples. We can add notes for what is not covered as well.

DelaramGolpayegani: How detailed or granular should this be?

HarshPandit: I'm thinking we go for high-level coverage so people can see whether a topic has relevant concepts or not, and there's an infinite number of additional concepts/things that couid be added, but there is sufficient stuff to be useful now

HarshPandit: AI Act also has guidelines for prohibited systems which we might want to reference when talking about concepts for AI Act

DelaramGolpayegani: also harmonised standards, would 42005 be in scope or not, for AI Act it would be good to reference links to harmonised standards

HarshPandit: Do we put certifications as separate documents and put the mapping over there? (ref. to Stratis' thesis)

ACTION: Create github issues for mappings associated with AI Act, EHDS, NIS2

Updates

ISO taxonomy

<ghurlbot> Issue 26 DPV-ISO providing concepts from ISO terminology and standards (by coolharsh55)

HarshPandit: propose setting up extension structure and scope as /standards/iso ; and then within it we have iso/core for the main concepts or we have iso/29100 for the main concepts e.g. PII Principal and in /mappings/iso we have the mappings from iso vocabularies to DPV concepts

IainHenderson: +1

JulianFlake: 29100 already has mapping to GDPR, maybe we go ISO to GDPR to DPV? (+1) (I was wrong on that, there is an 29100 → 27000 mapping only in ISO29100)

HarshPandit: for jurisdictions which don't use GDPR this would be complex, so we can directly go DPV to ISO

DelaramGolpayegani: +1

ArthitSuriyawongkul: for the structure in the repo, for the mappings to regulations, it will be in the /dpv/guides?

HarshPandit: it will be in the EU-GDPR html

ArthitSuriyawongkul: mappings between DPV and ontologies (they are in /mappings) and the other is the HTML spec

HarshPandit: maybe we change what we call 'mappings' in HTML to "coverage of GDPR terms in DPV" or something similar

ArthitSuriyawongkul: guides are for people using the DPV e.g. consent records is in guides for ISO 27560, and there is also something in the GDPR about it

JulianFlake: also what I was referring to in relation to the GDPR mapping. Having mappings from articles to concepts and guides is a good thing.

ArthitSuriyawongkul: If I have a guide about NIS2 where do I put it?

HarshPandit: if its only about NIS2, then it goes in NIS2 legal namespaces. If its also helpful for others but takes requirements from NIS2 then it goes to guides.

AI Act

<ghurlbot> Issue 229 Update EU-AIAct extension with practical concepts (by coolharsh55)

DelaramGolpayegani: working on mapping AI Act articles to DPv, and the outcome will be a list of proposed concepts; there is already work on high-risk and prohibited systems

DE-GDNG

<ghurlbot> Issue 387 Extension for the German GDNG (by chhdraeger)

JulianFlake: Met Christian, no updates to report back now. We have ongoing work on use-case where Christian is applying this to the real use and we are identifying minimal concepts from the synthetic + real use-case ; we are also working on English labels

JulianFlake: Working with german labels so there might be a need for English labels

HarshPandit: okay for me if the German system allows only german labels; if no one outside Germany context is using this then there isn't a need for English labels; in any case, there will be concepts extended from core DPV concepts so there is a contextual understanding of what the concept in German law is

JulianFlake: Some links between GDNG and GDPR e.g. personal data which would be good to highlight

CRDM/EIT AI Concepts

<ghurlbot> Issue 385 Align DPV with CRDM AI concepts (by coolharsh55)

<ghurlbot> Issue 390 Adding the taxonomy of AI capablities from EIT report (by DelaramGlp)

HarshPandit: The CRDM concept links were broken, the publications office has provided the correct link and the IRIs currently giving 404s will be resolved soon; see github issue

HarshPandit: Delaram has been working on mapping, we will have a proposal next week.

AOB

HarshPandit: EU Commission has published omnibus simplification proposals formally for GDPR and AI Act today; don't know changes from leaked version yet

ArthitSuriyawongkul: When will be the last meeting of 2025? When will be the first meeting of 2026?

HarshPandit: Last meeting this year on DEC-17 (last WED before christmas break) and first meeting in new year on JAN-07. Will also add this to the agenda for next meeting.

Next Meeting

The next meeting will be on NOV-26 Wednesday 13:30WET/14:30CET