Meeting minutes
Repository: w3c/dpv
Agenda: https://
Meeting minutes: https://
Persistent ID for current minutes: https://
Previous minutes: https://
Nominating DPVCG chair
See https://
<ghurlbot> Issue 389 DPVCG chair nomination (discussion) (by coolharsh55)
ArthitSuriyawongkul: I would like to nominate myself for the role of maintainer (not chair/co-chair).
BeatrizEsteves: A good idea would be to reply to the email Harsh sent on the chair/maintainer tasks (https://
ArthitSuriyawongkul: Should the process of selecting maintainers be a separate process from the chair nomination?
BeatrizEsteves: +1 on deciding for both roles during the same window (after the waiting period until OCT-31)
Fixes to DPV 2.2 (as DPV 2.2.1)
broken links in search page, missing info on deprecated concepts, potentially missing OWL files; tentative date OCT-31
DPV 2.2 post-release tasks
https://
some tasks will not be completed now ( see LOV issue below)
Add a red box warning for older DPV versions
<ghurlbot> Issue 396 Add a red box warning for older DPV versions (by coolharsh55)
This will point people to the latest version and tell this this version is outdated. See example https://
BeatrizEsteves: +1
ArthitSuriyawongkul: +1
JulianFlake: +1
PaulRyan: +1
Revise DPV main spec page for ease of access
<ghurlbot> Issue 395 Revise DPV main spec page for ease of access (by coolharsh55)
Harsh initial simplification proposal at https://
BeatrizEsteves: +1
ArthitSuriyawongkul: +1
JulianFlake: +1
PaulRyan: +1
v2.2 LOV submission
<ghurlbot> Issue 353 v2.2 LOV submission (by coolharsh55)
BeatrizEsteves: This is a good practice for ontology evaluation, e.g., FOOPS etc.
BeatrizEsteves: DPV 2.2 core is already in LOV, however there is not an easy solution to submit all the extensions that we have, without haing to do it all manually. So we are thinking together with the LOV maintainers how to automate this process, also for the sake of doing it for future versions.
BeatrizEsteves: I will discuss this with one of the LOV maintainers in the first week of December
JulianFlake: is there an alternative to LOV that we can/should publish to? and in a more automated way?
ArthitSuriyawongkul: I actually want to make a submission to LOV for another project: spdx/
Roadmap for Guides
<ghurlbot> Issue 242 Provide Guides for Supporting Adoption & Use of DPV (by coolharsh55)
BeatrizEsteves: Priority is to finish off some of the currently proposed guides by the release of 2.3
see current issues for guides: https://
DPIA - A paper can be adapted - "A Semantic Specification for Data Protection Impact Assessments (DPIA)" https://
PaulRyan: Perhaps Delaram and Tytti will have interest in collaborating for this one.
ROPA - Paul's PhD work can be adapted here, DPCat specification using DCAT should be discussed separately. The guide will focus on showing which concepts from DPV are useful for which ROPA field. This will be aligned with implementation of the ISO/IEC 27560 revision (which as PII Processing Records and Privacy Receipts instead of just for consent)
29184 Privacy Notices - Harsh has a working draft https://
BeatrizEsteves: +1 to add it on the next release
JulianFlake: Is there documentation on how it relates to ISO 27560 on consent records?
Data Breach - A paper can be adapted - "Towards a Semantic Specification for GDPR Data Breach Reporting" https://
Rights Exercise - A paper can be adapted - "How to Manage My Data? With Machine--Interpretable GDPR Rights!" https://
BeatrizEsteves: I would like to improve the current draft guide by DEC
Risk Assessment - needs to be written from scratch, Harsh can do this quickly as he has written most of the RISK extension content
ODRL - https://
BeatrizEsteves: seems doable by 2.3, I have already shared the current state with ODRL CG and have feedback to improve it.
Next Meeting
The next meeting will be on OCT-29 Wednesday 13:30WEST/14:30CEST
Agenda for next meeting will be continuing discussion on topics started for v2.3 and any other updates/new proposed topics.