Meeting minutes
Meeting minutes: https://
purl for this meeting: https://
Justifications
<ghurlbot> Issue 63 Add Right Non-fulfilment Justifications for GDPR’s rights (by coolharsh55)
paulRyan: okay with the outputs
beatrizEsteves: okay with the outputs
harsh: that concludes the discussion with okay from paul, beatriz, and georg and we will add them to v2. For the GDPR rights, we will think about how to express the relation for v2.1
Consent Controls
<ghurlbot> Issue 115 Add Measures for Obtain, Withdraw, etc. for Consent and other Actions (by coolharsh55)
harsh: how do we add controls to obtain/ withdraw consent - there is no exact solution at the moment
harsh: Do we suggest using the existing WithdrawFromActivity or specifically add a term WithdrawConsent? The cons of the second method is that we will need to repeat such actions for all legal basis.
harsh: Proposal: we keep the consent actions to what is necessary i.e. obtaining, providing, and withdrawing and provide terms specifically for these. For others, like demonstrate, validate, etc. we can have generic controls as proposed in the issue
harsh: through this, we will be providing specific consent based relations (straightforward solution for those who wish to model consent)
paulRyan: we should model consent as it has been explicitly mentioned in regulations
beatrizEsteves: Agree with adding specific controls for consent
discussion concluded - No objections for Proposal, to be discussed next week with examples
Technology Purpose
<ghurlbot> Issue 85 Specify 'business process' or 'service goal' in DPV-Tech (by coolharsh55)
harsh: How to model the goal of the technology
harsh: Proposal: 1. What is the technology capable of 2. Reuse DPV “has purpose” to say technology has purpose etc.
steveHickman: leave it as purpose.
beatrizEsteves: confusing to use same term for defining purpose of processing activity or purpose of an AI system.
delaramGolpayegani: agrees with Beatriz
harsh: Ideas on how to represent this information and the multiple meanings behind purpose?
beatrizEsteves: properties for this in tech extension: “intended purpose”
harsh: we will then need to distinguish this as intended purpose and applied purpose - and we have dpv:Purpose already covering both, so this will be confusing
delaramGolpayegani: call it intent, concluded its too vague. Or call it function (use function as capability to model).
Discussion concluded without consensus on solution. Agreed to discuss this with furthe examples and ideas.
Tech concepts
delaramGopayegani: Need terms: market availablity status, deployer, operator, etc. Is there an umbrella term for these?
… We have TechnologyActor in tech extension, but nothing to distinguish the non-subject actors.
delaramGolpayegani: Call user “end user” instead?
harsh: For now, we have already accepted terms market availablity status, deployer, etc - so we will add this to the Tech extension.
harsh: We require a mapping of 22989 terms for actors and other concepts - Victor, Alex, Ana to assist with this
… DPV v2
harsh: we're getting there, all issues have been discussed and will be resolved, so optimistic about making the intended deadline of May end
harsh: only remaining work is documentation - data breach, DGA etc - which will be done from existing papers
Next meeting
The next meeting will be in 1 week on WED 15 May 14:00 WEST / 15:00 CEST. Agenda continued from today's discussions.