Meeting minutes
Repository: w3c/dpv
Data Breach extension
harsh shared the current draft, see email https://
This is to be reviewed by the group before inclusion in the formal repository. The review will be undertaken by georg, paul, julian, and will be an item on next week's agenda.
ghurlbot, get #64
<ghurlbot> Issue 64 Provide concepts for Data Breach (coolharsh55)
TedThibodeauJr: as best practice, it is better to add the draft to the group's repository and continue the work there
harsh: agreed, the process is that this is the first draft as a proposal - once the group agrees it is in scope and there are no issues, it is then added to the github repo and then is developed there
Multilingual Translations
tobiasEichinger: for the TRAPEZE project which uses the DPV for consent management, we are generating automated translation using DeepL for the DPV concepts. Currently, it has some errors that need human intervention to fix and refine.
georg: What is the scope for translations? Will you translate everything? All concepts and documentation?
tobiasEichinger: ideal would be everything, but for now it is concepts and descriptions
georg: we can use GDPR multilingual lexicon api.digitalgrammars.com/gdpr for the translation glossary
… tobias and georg will work on the glossary and then they will refine them with translations and review them for quality; if they work then produce the RDF / SKOS translations to use with the TRAPEZE tool
ghurlbot, get #89
<ghurlbot> Issue 89 Multi-lingual labels and descriptions for concepts (coolharsh55)
georg: The current way of translating works for concepts but not for descriptions (which are sentences)
tobiasEichinger: DeepL will also work with the descriptions with the help of glossary to help with correctness
As per email conversations earlier, the proposal by tobias is to have a glossary of manually curated terms so that DeepL can refer to those to generate the correct translations.
tobiasEichinger: (demo of TRAPEZE dashboard) the concepts and descriptions from DPV are displayed as part of the dashboard, so the user can choose the language and the translations will be used here
Data Governance Act
beatriz: (presenting) concept analysis of DGA with a focus on the various entities involved
georg: where is data requestor?
discussion on data requestor as a concept - it is not mentioned or defined in the DGA. Conclusion that we do not define non-normative terms at the moment, and wait for guidance or common usage before adding it to the vocabulary
beatriz: changes to DPV top concepts and properties required to model data instead of personal data
harsh: question to the group - whether we discuss this now (as in the coming weeks) or do we take this up later?
georg: can we do this ASAP?
harsh: okay, then it is prioritised
conclusion - beatriz and harsh will write up the proposed changes and major impact to dpv and georg will review, and an item will be added to next week's agenda
ghurlbot, get #62
<ghurlbot> Issue 89 Add DGA/eIDAas entities (coolharsh55)
has assessment relation
harsh: as in the earlier meetings, a proposal has been put forth to create a relation called hasAssessment with variations as needed for risk assessment and impact assessment. Corresponding concepts will also be needed for Assessment with specialisations Impact Assessment and Risk Assessment (these exist), with further specialisations for DPIA, PIA, Rights Impact Assessment, Fundamental Rights Impact Assessment, Data Breach Impact Assessment
agreement in the group to add proposed concepts
harsh: ghurlbot, get #96
<ghurlbot> Issue 96 Add assessment relations and concepts (coolharsh55)
Next Meeting
The next meeting will be in 1 week on JUN-29 at 14:00 WEST / 15:00 CEST.
Topics for discussion will include (1) review of data breach document; (2) impact of proposed changes from DGA modelling; (3) updates to multilingual translations