DPVCG Meeting Call

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

purl for this meeting: https://w3id.org/dpv/meetings/meeting-2024-06-12

DPV v2 reviewing

harsh: examples added - see spreadsheet for index https://docs.google.com/spreadsheets/d/1__STWvOEZRc1u2J-8teOYjLpnTPlZ80_ebTytrUlWgQ/edit?gid=528144990#gid=528144990 and the contents are from files in the repo. The examples have an ID, which is used to automatically insert the example in documents. So if the content or description is updated, it gets updated in all places the example is used.

discussed reviewing specs

versioned IRIs

agreed to have two folder v1 as w3id.org/dpv/v1 and v2 as w3id.org/dpv/v2 and that w3id.org/dpv will always point to latest version i.e. v2 now

beatrizEsteves: for w3id, there are some tips/tricks e.g. turtle redirect should be first (will help with w3id)

risk consequence taxonomy

<ghurlbot> Issue 163 [Review] EU AI Act Concepts (by DelaramGlp)

delaram pointed out that 'Misuse' can be a risk or risk source but is currently indicated as a consequence

currently, we have consequence and impact taxonomy which is opinionated. However, the same 'consequence' can be a risk or risk source. So how to enable this flexibility? Suggestion: 1) Event as top concept and then adopter chooses events to be expressed as risk sources or risks or impacts etc; 2) Risk as top concept and adopter chooses the risk (event) and expresses it as source or impact etc.

discussed that having 'risk' as the top concept might be a better solution and then let the use-case specify whether the risk is a risk source or a consequence or an impact

we can categorise risks as 'risk of consequence' and 'risk of impact' to help with the taxonomy

Next meeting

The next meeting will be in 1 week on WED 19 JUN 14:00 WEST / 15:00 CEST. Agenda will focus on DPV v2 planning and release.