W3C

DPVCG Meeting Call

03 JUL 2024

Attendees

Present
beatrizEsteves, delaramGolpayegani, harshPandit, julianFlake, tyttiRintamaki, victorJuarez
Regrets
georgKrog, paulRyan
Chair
harsh
Scribe
harsh, harshPandit

Meeting minutes

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

purl for this meeting: https://w3id.org/dpv/meetings/meeting-2024-07-03

DPV 2.0 Beta release

see https://lists.w3.org/Archives/Public/public-dpvcg/2024Jul/0000.html

Pending Issues

<ghurlbot> Issue 165 CSV/JSON output of DPV v2 and extensions (by coolharsh55)

harsh: will check with georg/Signatu about this for resolving the issue

<ghurlbot> Issue 166 Update diagrams for v2 (by coolharsh55)

harsh: diagrams are updated

julianFlake: some diagrams are still pending?

harsh: added processing context

julianFlake: there are some inconsistencies in the diagram - stray lines which need to be removed

<ghurlbot> Issue 45 Preserving older versions of DPV and other resources (by coolharsh55)

harsh: we have versioned resources, and DPV has been submitted to LOV (awaiting response)

delaramGolpayegani: better to send LOV contact an email about this

Dev work

harsh: for under-development work, we currently utilise the dev branch in the repo, and then to view it live we use the dev.dpvcg.org urls. Other repositories have different styles of managing this workflow. They use the next version number e.g. we would have a 2.1 folder.

harsh: One solution is to use dev as it clearly indicates the work is not final, and also gives flexibility to decide what version number should be used if needed e.g. 2.1 or 3.0

julianFlake: we can have 2.1-dev and 3.0-dev

harsh: The problem with these approaches is that in our editor's draft url in document, we would not have a consistent way to point to it. E.g. in DCAT v2 and DCAT v3 the same url is provided for editor's draft.

harsh: so if we have dev then our url w3id.org/dpv/dev will always go to the next under-development version. Once we have enough material to create a release, we can copy the dev into a versioned folder e.g. 2.1 and continue working without changing any draft urls

group agrees with this approach

identified minor issue in current DPV spec edDraftURI which should point to the versioned iteration i.e. /2.0/dpv

Roadmap

harsh: which items do we prioritise for the next release? The plan is that we will have sufficient materials every 6 months for a release, so we produce 2 releases per year so that DPV is always up to date for recent events.

group is okay with this plan

beatrizEsteves: prioritise EIDAS as it is needed for Solid Lab, Data Act work with visiting legal PhD, and finishing ODRL alignment

harsh: georg had mentioned prioritising AI Act

delaramGolpayegani: AIRO and VAIR to be submitted and mapped to DPV by end of this month – this will be inputs to AI and the EU AI Act extensions

julianFlake: interested in AI and Data Spaces as preference but cannot commit at the moment

tyttiRintamaki: working on DPIA for GDPR, risks, AI Act annex III + FRIA

harsh: working on 29184 machine-readable notice, should be complete end of this month

ODRL CG Meeting

beatrizEsteves: ODRL CG is meeting with W3C TPAC. We can have a joint meeting with them e.g. putting DPVCG on the ODRL CG meeting agenda. Or if there are many people joining and lots to discuss, we can have a separate meeting. Meeting will be in September.

Interested members to let beatriz know about their interest to join by JUL-17 so they can plan accordingly.

Next meeting

The next meeting will be in 1 week on WED 03 JUL 14:00 WEST / 15:00 CEST. Agenda will be DPV v2.0 beta release and future tasks.

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