Meeting minutes
Repository: w3c/dpv
Agenda: https://
Meeting minutes: https://
Persistent ID for current minutes: https://
Previous minutes: https://
Nominating Chair
<ghurlbot> Issue 389 DPVCG chair nomination (discussion) (by coolharsh55)
HarshPandit: Call for nominating DPVCG chair https://
It is necessary to have a publicly visible nomination process and therefore any expressions of interest must also come on the public mailing list.
Service Maintainence
<ghurlbot> Issue 287 [NEW]: Add Maintenance as a `dpv:Purpose` (by besteves4)
BeatrizEsteves: agree with this but concerns regarding reliance on the structure
GeorgKrog: agree with change, will help map the service and supply chain where the type of service provision can be specified
IainHenderson: also helpful for MyTerms
ACTION: Provide rationale for change in ServiceProvision concepts and its legal implications
Purpose Compatibility for GDPR
<ghurlbot> Issue 298 Model Purpose Compatibility statuses for GDPR (by coolharsh55)
HarshPandit: Should PurposeCompatibilityAssessment also exist as a concept?
BeatrizEsteves: Colleagues in Belgium are interested in implementing this algorithmically, so this would be beneficial.
ACTION: add concepts (GDPR Purpose Compatibility)
Proportionality for GDPR
<ghurlbot> Issue 386 Model Proportionality for GDPR (by coolharsh55)
ACTION: Accepted unless there are pressing issues (okay from Stratis and Georg)
CRDM AI taxonomy
<ghurlbot> Issue 385 Align DPV with CRDM AI concepts (by coolharsh55)
<ghurlbot> Issue 390 Adding the taxonomy of AI capablities from EIT report (by DelaramGlp)
HarshPandit: Also relevant to the EIT taxonomy proposed by Delaram
DelaramGolpayegani: Don't have definitions for the EIT taxonomy, but its a list of capabilities and types of agents, etc.
<ghurlbot> Issue 197 Model `Agent` and `LegalAgent` (by ghurlbot)
ArthitSuriyawongkul: Would it also involve Agents?
DelaramGolpayegani: Yes, there are Agents and types of Agents mentioned there.
AI Agent
<ghurlbot> Issue 197 Model `Agent` and `LegalAgent` (by ghurlbot)
ACTION: To review the Agent taxonomy for issues distinguishing between Legal and Machine agents, and accept it otherwise.
GeorgKrog: Do we also think of "agency" as a concept?
HarshPandit: No, because we have representative and legal agent, and then this would be confusing for also using with AI agent, so its better we stick to clear terms and avoid confusion/mixing things.
LEGAL DE-GDNG
<ghurlbot> Issue 387 Extension for the German GDNG (by chhdraeger)
JulianFlake: We met and discussed this (with Christian). Challenging to identify concepts in German as we have based work on English before. For now, we are using German labels but these will need to be in English if we decide to have them in both. The term would also have to be in English then.
HarshPandit: If the jurisdiction benefits from using terms in the native language because this is what will be used by implementers, then that is fine. We can still have English labels and the concepts will be extended from DPV so that others will have context for what the concept is about (e.g. its a security measure)
ArthitSuriyawongkul: The IRIs should be kep simple and in ASCII and not have special characters when possible. In German, there is a way to transform special characters to ASCII
JulianFlake: yes, e.g. ß = ss, ä = ae
Improving EU law extensions
BeatrizEsteves: Planning to work on EHDS on October based on work in PACSOI
GeorgKrog: Have work on EHDS, will collaborate with Beatriz on this. On the AI Act also have work. For NIS2, there is few work. For DORA also there is work, but not sure whether that is in scope.
HarshPandit: We haven't discussed whether DORA is in scope of DPV, so we should discuss this in context of issue 282 regarding incident and data breach
GeorgKrog: Also describing categories of organisation
DelaramGolpayegani: Work on AI Act, and also work in context of the RECITALS project. For NIS2 and others, impact assessments would be part of it, risk management, incident reporting, and other documentation requirements.
DelaramGolpayegani: Other thing to consider is the guidelines coming from the Commission on prohibited practices and GenAI and the Code of Conduct. There is also the template for GenAI. So there is a lot to cover.
For each regulation, there will be a dedicated working plan with interested participants and the outcomes will be reported back to the group. Interested members should contact the group to be involved.
ACTION: Organise working groups for improving EU law extensions
EHDS
<ghurlbot> Issue 238 Update EHDS extension with practical concepts (by coolharsh55)
participants: Harsh, Georg, Beatriz, Julian, Christian
NIS2
<ghurlbot> Issue 222 Update NIS2 extension with practical concepts (by coolharsh55)
participants: Harsh, Georg, Art, Delaram, Julio
GeorgKrog: There is work done by Jenny (UCD student) that was submitted to DPV. We should also look at DORA and the cybersec requirements within that.
HarshPandit: Let's do NIS2 first, and then DORA deciding whether its in scope and adding basic concepts for now
AI Act
<ghurlbot> Issue 229 Update EU-AIAct extension with practical concepts (by coolharsh55)
participants: Harsh, Delaram, Julio, Georg, Art
AOB
P7012
<ghurlbot> Issue 258 Consolidate Purposes into Groups for Simplifying Adoption with P7012 (by coolharsh55)
IainHenderson: IEEE P7012 (nickname: MyTerms) -- needs work done on the DPV extension
BeatrizEsteves: Then we should have a meeting. There is work to be done e.g. on the ODRL parts and on the naming. There are updates for the SolidSymposium next year, which will be around 30th May. I'm involved in organising. This will be helpful to showcase there.
IainHenderson: Yes, talking to Jesse about this.
IETF AI Pref Vocab
<ghurlbot> Issue 295 Concepts to represent AI training is Permitted/Prohibited (by coolharsh55)
BeatrizEsteves: Found this work https://
ArthitSuriyawongkul: There is related work as the IETF wants to target this for web crawlers, another one is from Creative Commons called CC Signals. Another one is RSL - Really Simple Licensing from the RSS people https://
ArthitSuriyawongkul: The difference is that CC Signals will attach to the work while IETF work will be communicated by the host/servers.
HarshPandit: We should think about modelling such "privacy terms" and currently we do that in P7012 extension to say third party data sharing is prohibited or AI training is prohibited, but we might want to further expand this taxonomy or include it in more prominently.
Next Meeting
The next meeting will be on OCT-08 Thursday 13:30WEST/14:30CEST
Agenda will be continuation of today's discussion regarding finalising service maintainence, purpose compatibility, and proportionality/necessity, and additional items from v2.3 milestone which have updates. The meeting will be chaired by Beatriz as Harsh will be away at ENDORSE conference.