Meeting minutes
Meeting minutes: https://
purl for this meeting: https://
DPV Maintainence
see live version at https://
paul has reviewed purposes (https://
beatriz has reviewed GDPR (https://
Multilingual DPV
<ghurlbot> Issue 89 Multi-lingual labels and descriptions for concepts (by coolharsh55)
Question is how to present these in the HTML documents? Open to suggestions or best practices that we can adopt. Otherwise the 'default' option is to provide some language selector on the page, and to have different versions of the page for languages.
Service new concept
<ghurlbot> Issue 124 Add dpv:Service as a concept (by coolharsh55)
discussed whether to accept this; delaram will discuss implications of the concept and roles for 'AI System as a Service' next week
ISO 22989 AI terms
<ghurlbot> Issue 110 Add concepts from ISO 22989:2022 AI Terminology (by coolharsh55)
okay to look into for comments and how they can support DPV concepts
mark raised the point about using only legal concepts; harsh mentioned sources for concepts in DPV are authoritative sources which includes both law and standards. For specific legal concepts it is suggested to represent them in extensions.
Datasheets/Model cards
<ghurlbot> Issue 94 Represent Dataset Datasheets with DPV (by coolharsh55)
okay to look into how to represent these using DPV
delaram raised the concern that there are several different variations of datasheets and model cards - which one to use; harsh suggested we look at the information within them and whether DPV can support their expression where the information is in scope;
AI Act
<ghurlbot> Issue 106 Propose concepts from the AI Act (by coolharsh55)
delaram has collected the definitions from Art.3 into a spreadsheet for discussion - https://
there are 3 versions from Commission, Council, and Parliament
discussion on definitions - there are potentially conflicting/different definitions from AI Act, ISO standards, and OECD; suggestion that the AI Act specific definition be in the AI Act extension and other definitions can be the general concept in DPV or extension
for Intended Purpose - how to model this? The intended prefix is not present in DPV, and the purpose of using AI system is not covered in the current DPV Purpose description; To resolve this, the dpv:Purpose description should be updated to reflect purpose of using data as well as systems/technology which will cover use of AI. Exercise to check whether other concepts should also be updated for this. For intended, we have this as a context rather than only for purpose i.e. a purpose and data and other information can be intended or unintended.
for Purpose vs Capability/Application - the purpose is the end-purpose or the goal of the activity whereas the capability is the technical objective or action; this is similar to how processing reflects actions on data and puropse reflects why the data is being used.
discussion on whether specific concepts should be modelled, e.g. Biometric Categorisation System; harsh suggested that if such concepts have legal relevance i.e. their existence triggers some obligation or additional processes then it is useful to have them - so we should model them.
delaram discussed whether the information in such concepts should be connected to their contituents e.g. Biometric Categorisation to the System; harsh suggested yes; group agreed
legal roles present in AI Act will go in the extension
data concepts e.g. training data - discussion on where to put these? Main DPV, Tech extension?
AI Extension
<ghurlbot> Issue 126 AI Extension to provide AI-specific concepts (by coolharsh55)
following from discussion of AI Act, delaram proposed creating a new AI extension as there are lots of AI specific concepts; the group agreed
it will be an extension of the Tech concepts specific to AI, the concepts related to AI such as lifecycles and data will be here; to be discussed next week by delaram
georg asked whether people have worked with Tech extension and Processing concepts; harsh mentioned he had used these to model how the processing was implemented by a technology capable of doing different processing actions and had technical measures; georg mentioned difficulty in doing 'supplier diligence' based on technology provided
the topic of 'supplier due diligence' is relevant to NIS2, DORA, and AI Act - this will be a discussion later with georg and delaram discussing what DPV can do to support this
georg mentioned the following as desirable for using DPV - a way to state use of a system, delivered by a provider or supplier, tech is used in product/service, and then the risk assessment
Next Meeting
The next meeting will be in 1 week on WED DEC-06 15:00 WET / 16:00 CET.
Asked about meetings in December. Based on availabilities, there may be no meetings from around 20th December to 3rd January. To be decided in December.
Items on the agenda for next week are - Service led by delaram, AI Act led by delaram, AI Extension led by delaram, dpv documentation led by harsh
georg has an upcoming webinar on their Privacy chatbot - see https://