DPVCG Meeting Call

Repository: w3c/dpv

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

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

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

Previous minutes: https://w3id.org/dpv/meetings/meeting-2026-02-04

Admin

Submit to LOV

<ghurlbot> Issue 353 v2.2 LOV submission (by coolharsh55)

HarshPandit: what is the format for this? do we know? E.g. do we give IRI, link to turtle file, title, list of authors (they are there in the RDF)

BeatrizEsteves: Generate CSVs for v2.2 and v2.3. Check for v2.2 with the LOV maintainers if this is okay while v2.3 is in draft mode, then we send the update for v2.3

ACTION: Harsh to produce LOV spreadsheet for v2.2

DPV v2.3 release schedule

(we are waiting for EHDS, GDNG, and IEEE 7012 – see later discussions)

okay to complete the pending items by tomorrow and then have the draft release; ask people to review until the next meeting to make a decision on finalising the publishing the release

w3id updates

<ghurlbot> Issue 425 w3id updates needed for v2.3 (by coolharsh55)

see issue comment

BeatrizEsteves: see PR ; needs review and there's an open question on IEEE 7012 namespace; added redirects for older versions i.e. v2.1 and v2.2 will still go to standards/p7012 and the new one will go to standards/ieee/7012

HarshPandit: what to do with ODRL agreements? Do this in v2.4?

IainHenderson: Yes, okay to do this in v2.4.

ACTION: Harsh to review w3id config

ACTION: Harsh to move folder w3id from master to dev branch

v2.3

ISO mapping

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

HarshPandit: propose we have draft release tomorrow; review and finalise in next week's meeting

JulianFlake: +1

BeatrizEsteves: +1

HarshPandit: +1

TyttiRintamaki: +1

GeorgKrog: +1

BeatrizEsteves: w3id should work here

HarshPandit: HTML and RDF mapping, possible to add more ISO concepts e.g. 27000 series in the future here without new extensions or namespaces

JulianFlake: what is the meaning of a draft release?

BeatrizEsteves: means we are still working it, and there may be breaking changes in the future. Same thing we are doing with the EHDS

JulianFlake: so this is just for the extension (mapping) and not the whole release

agree to publish mapping as draft

GDPR concepts

<ghurlbot> Issue 386 Model Proportionality for GDPR (by coolharsh55)

<ghurlbot> Issue 298 Model Purpose Compatibility statuses for GDPR (by coolharsh55)

has been confirmed in previous meeting

ACTION: Use Stratis's correct name for acknowledgement

ACTION: contributors to check name and provide affiliation and funding acknowledgements if relevant

agree to publish GDPR extension

EU EHDS

<ghurlbot> Issue 238 Update EHDS extension with practical concepts (by coolharsh55)

<ghurlbot> Issue 299 Model Purpose Compatibility statuses for EHDS (by coolharsh55)

BeatrizEsteves: changes discussed in last meeting; concepts are in the spreadsheet for EHDS

BeatrizEsteves: for Health Sector these are new concepts so these should be copied from working spreadsheets to DPVCG spreadsheets

HarshPandit: So we copy concepts, then download and generate RDF and HTML

HarshPandit: Do we add any documentation in HTML?

BeatrizEsteves: Can do this for these changes via a PR

ACTION: Copy concepts for EHDS and SECTOR-HEALTH to DPVCG spreadsheets - Harsh & Beatriz

ACTION: Update EHDS and SECTOR-HEALTH extensions with new concepts - Harsh & Beatriz

ACTION: Add documentation for EHDS and SECTOR-HEALTH - Beatriz

timeline - complete by tomorrow

agree to publish EHDS and SECTOR-HEALTH

AI extension

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

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

<ghurlbot> Issue 197 Model `Agent` and `LegalAgent` (by ghurlbot)

HarshPandit: reviewed with Delaram - accepted

BeatrizEsteves: +1

agree to publish AI

AI Act

<ghurlbot> Issue 300 Model Intended Purpose Compatibility statuses for AI Act (by coolharsh55)

<ghurlbot> Issue 294 AI Model Development Phases (by coolharsh55)

HarshPandit: reviewed with Delaram - accepted (show mapping to DPV – propose we do something similar for GDPR and other laws in the next release)

HarshPandit: three new major changes 1) mapping from AI Act to DPV 2) AI system concepts represent high-risk and prohibited systems 3) instances representing high-risk systems in Annex I and III and prohibited systems in Art.5

ACTION: FIX Art.6-2 definition refers to 6-1

agree to publish AI Act

DE-GDNG

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

JulianFlake: have provided an update with the HTML and updated diagrams etc. as the PR ; ready to be merged

JulianFlake: we saw in the AI act that there are refereneces to articles in the IRI, should this be done?

HarshPandit: we only do these for important concepts that are tied to the legal identifiers or clause numbers e.g. legal basis in GDPR

BeatrizEsteves: also for the rights and justifications in GDPR

JulianFlake: We concluded it is necessary to add some numbers in IRI

HarshPandit: okay to do this and change in future version as this is a draft

JulianFlake: need further work on parent types e.g. needs a review to suggest correct parent types

HarshPandit: (commend on quality of concepts and documentation -- good to follow for future extensions even if they are draft)

ACTION: Merge GDNG PR as draft extension

IEEE 7012 / MyTerms

<ghurlbot> Issue 413 Ensure P7012 concepts extend core DPV concepts (by coolharsh55)

<ghurlbot> Issue 423 Change `P7012` to `IEEE 7012` (by coolharsh55)

HarshPandit: should this be kept as release considering things are still being finalised from Iain's side (see today's email). ODRL concepts and agreements are also pending.

+1 from Harsh and Beatriz to finalise this in v2.4

IainHenderson: event at the end of January for the launch of MyTerms went well ; event was recorded if anyone wants to see it. Now we are focusing on practical aspects, which involves setting up "MyTerms alliance", which includes IEEE, Customer Commons, MyData Global. Also interested is Inrupt (Solid). So we're forming this alliance as Phase 1 and we'll know more of what it means in practice.

IainHenderson: We're working with IEEE to develop accredition, training, and trust maps for support in implementing the standard. MyData will have a meeting in Brussels in April likely. Also talking to Solid community and Jessie/ODI.

agree to provide more concrete ODRL agreements, concepts, and guidance in v2.4

Usability

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

HarshPandit: Show refine index in main DPV spec – list is only shown on demand. Is this acceptable?

JulianFlake: looks good, my idea was that we have a list of modules and under that the list of concepts in that module which is expanded when a concept is selected

DelaramGolpayegani: looks good, we should also ask people to take a look -- especially new people

BeatrizEsteves: +1

agree to continue with this layout

ACTION: Fix module links (broken in some cases) - Harsh

Locations

<ghurlbot> Issue 341 Add Location concepts to PD extension e.g. Home, Work (by coolharsh55)

<ghurlbot> Issue 342 Add Location concepts to TECH extension e.g. Device, App (by coolharsh55)

HarshPandit: Based on discussions on location concepts, have added concepts for Home, Work, and Current Location to PD, and marked all location concepts as instances of dpv:Location. Same for TECH extension - marked existing data storage and processing as locations. We agreed to this after length discussions the last time around, and we pushed these concepts from 2.0 to 2.1 then to 2.2.

GeorgKrog: this is good to have for developing technologies; this needs to be expanded case by case

JulianFlake: need to review this as a device as a location is not accurate

HarshPandit: a device as a location means its a virtual location, so its a concept in the same sense that you say data is being stored on a server in EU, or its stored on your phone. So the phone is a location for storing data locally. This is the common use reflected in the concept.

HarshPandit: for TECH, the concepts are also marked as ProcessingLocation and StorageLocation for making this clear.

ACTION: Julian (and others) to review this

v2.4

HarshPandit: proposed work program https://github.com/w3c/dpv/milestone/10 -- review and indicate interest to be involved in the work

Next Meeting

The next meeting will be on FEB-18 Wednesday 13:30WET/14:30CET