-
Notifications
You must be signed in to change notification settings - Fork 28
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
733f360
commit ec80997
Showing
3 changed files
with
168 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,47 @@ | ||
| 20:08:55 <RRSAgent> RRSAgent has joined #dpvcg | ||
| 20:09:03 <harsh> Scribe: harsh | ||
| 20:09:10 <harsh> Meeting: DPVCG Meeting Call | ||
| 20:09:13 <harsh> Chair: harsh | ||
| 20:09:23 <harsh> Present: harsh, tytti, beatriz, paul, delaram, iain | ||
| 20:09:37 <harsh> Date: 14 FEB 2024 | ||
| 20:09:50 <harsh> Agenda: https://www.w3.org/events/meetings/31f00434-f01b-431d-a9d9-4ef690dd7c6d/20240214T150000/ | ||
| 20:09:57 <harsh> Meeting minutes: https://w3id.org/dpv/meetings | ||
| 20:10:04 <harsh> purl for this meeting: https://w3id.org/dpv/meetings/meeting-2024-02-14 | ||
| 20:10:04 <harsh> Topic: Academic Paper | ||
| 20:10:04 <harsh> beatriz: propose to publish DPV as a paper at ISWC 2024 in resource track about the updates to DPV from the previous paper at ODBASE in 2019. Advantages are publications and outreach in ISWC which is the prime sem-web community. Disadvantages are that its not open access, and that the audience may not grasp the way we have done DPV based on legal requirements. Discussing here whether people are interested. | ||
| 20:10:04 <harsh> \ ISWC Resource Track CFP https://iswc2024.semanticweb.org/event/3715c6fc-e2d7-47eb-8c01-5fe4ac589a52/websitePage:453b107c-014c-4170-acce-27e28e83a2a9 | ||
| 20:10:04 <harsh> paul: how/what is a resource paper as compared to a research paper? | ||
| 20:10:04 <harsh> beatriz: it is a description about the resource (i.e. DPV), so its methodology, lessons learned, way it was developed and tested, etc. Deadline is due APR-17 for full paper. Conference is in Maryland, USA. | ||
| 20:10:04 <harsh> paul: what is the scope of this paper? Is it privacy or also include AI etc.? | ||
| 20:10:04 <harsh> beatriz: whatever is there in v2, but also talking about AI stuff e.g. delaram has lots of work on this | ||
| 20:10:04 <harsh> paul: will there be a state of the art on the topic? | ||
| 20:10:04 <harsh> beatriz: there is a journal paper about literature on vocabularies, but not sure if there is a detailed section on literature review for resource paper | ||
| 20:10:04 <harsh> \ The group agreed this would be a good idea. | ||
| 20:10:04 <harsh> Topic: Age Verification Concept | ||
| 20:10:04 <ghurlbot> https://github.com/w3c/dpv/issues/128 -> Issue 128 Add dpv:AgeVerification as a purpose concept (by besteves4) | ||
| 20:10:04 <harsh> harsh: The issue has had a discussion, with a potential agreement and resolution. Please refer to the issue for more details, and to continue discussions. | ||
| 20:10:04 <harsh> Topic: Rights Exercise | ||
| 20:10:04 <ghurlbot> https://github.com/w3c/dpv/issues/63 -> Issue 63 Add Right Non-fulfilment Justifications for GDPR’s rights (by besteves4) | ||
| 20:10:04 <harsh> beatriz: continuing work from earlier - shared the work with Georg and Paul for review. Discussion between Georg and Harsh regarding legal rights and contractual rights as purposes. | ||
| 20:10:04 <harsh> harsh: It has been (potentially) resolved by considering Legal Rights as a distinct concept, with Contractual Rights being covered by the Fulfilment of Contractual Obligations purpose. The descriptions of these concepts should reflect that. | ||
| 20:10:04 <harsh> beatriz: Tasks for next week to continue reviewing and finalise the concepts. | ||
| 20:10:04 <harsh> Topic: AI Act | ||
| 20:10:04 <ghurlbot> https://github.com/w3c/dpv/issues/106 -> Issue 106 Propose concepts from the AI Act (by coolharsh55) | ||
| 20:10:04 <harsh> delaram: the AI Act concepts are around 121 at the moment. Some of these will go to the AI extension, some to the Tech, and some to AI Act extension. What to name the extension for the AI Act? AIA? | ||
| 20:10:04 <harsh> harsh: let's call it "AI Act" as "AIA" may also be confused with "Algorithmic Impact Assessment"? | ||
| 20:10:04 <harsh> delaram: The concepts include entities etc. and different types of AI Systems which are complex. E.g. Emotion Recognition System - emotion recognition is a capability so do we model it as a subtype of AI system or express it as an relation e.g. hasCapability? | ||
| 20:10:04 <harsh> georg: What is the difference between capability and activity? | ||
| 20:10:04 <harsh> harsh: Capability as in feature or the tech is capable of doing this, so the technical purpose which we distinguish from the 'end purpose' | ||
| 20:10:04 <harsh> harsh: If a concept is relevant in law, especially if it occurs as a definition or prominently is the subject of an article, we have to model it as a concept as DPV is foremost a 'vocabulary'. The other relations as the one mentioned can be modelled using OWL but first require all the necessary concepts to have been identified and be 'correct'. So for now - we can make a note e.g. as a comment to the concept about how other concepts and relations are associated with this concept. | ||
| 20:10:04 <harsh> georg: How up to date is this with the latest version of the Act? | ||
| 20:10:04 <harsh> delaram: Its work in progress, but its based on the leaked version - so quite up to date. | ||
| 20:10:04 <harsh> delaram: How to deal with modelling concepts across ISO and AI Act? | ||
| 20:10:04 <harsh> harsh: ISO is a global agreement standard - so we use that as the baseline e.g. in DPV or in Tech extension. In retrospect, the core DPV definitions and terms should have used ISO, but we started with a EU/GDPR specific perspective - so that's to late to be fixed now. If a ISO-defined term is compatible with AI Act, but the term in AI Act has legal relevance (e.g. explicitly defined) then it must be repeated in the AI Act extension. Otherwise if it is trivial and not necessary (i.e. we can rely on the generic term from DPV), then it doesn't need to go in the AI Act extension. If the term is not compatible (e.g. ISO and AI Act differ and are not compatible) - then there will not be any relation between them (maybe as related) but they can share a common parent. | ||
| 20:10:04 <harsh> Topic: AI and Tech extensions | ||
| 20:10:04 <ghurlbot> https://github.com/w3c/dpv/issues/126 -> Issue 126 AI Extension to provide AI-specific concepts (by coolharsh55) | ||
| 20:10:04 <harsh> delaram: potential issues or ambiguity regarding how the concepts should be referenced - do they do in DPV or Tech or AI extension? | ||
| 20:10:04 <harsh> harsh: if they are universal or general to personal data / technology activities - then they go to DPV. If they are specifically about the technical aspects of a technology or system, then they go in Tech. We discussed AI extension based on the assumption that there will be enough AI specific content that it warrants creating an extension for AI from Tech. | ||
| 20:10:04 <harsh> harsh: For now - Lets think about modelling it together as a single extension called "AI & Technology", get all the concepts, and then see how and where the AI extension makes sense | ||
| 20:10:04 <harsh> Topic: Next Meeting | ||
| 20:10:04 <harsh> \ Next meeting will be in 1 week, on WED FEB-21 15:00 WET / 16:00 CET. | ||
| 20:10:04 <harsh> \ Topics for discussion are updates on DPV v2, github repo and issues, rights exercise, discussion on AI Act, and Tech/AI vocabulary. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,120 @@ | ||
| <!DOCTYPE html> | ||
| <html lang=en> | ||
| <head> | ||
| <meta charset=utf-8> | ||
| <title>DPVCG Meeting Call – 14 FEB 2024</title> | ||
| <meta name=viewport content="width=device-width"> | ||
| <link rel="stylesheet" type="text/css" title="2018" href="https://www.w3.org/StyleSheets/scribe2/public.css"> | ||
| <link rel="alternate stylesheet" type="text/css" title="2004" href="https://www.w3.org/StyleSheets/base.css"> | ||
| <link rel="alternate stylesheet" type="text/css" title="2004" href="https://www.w3.org/StyleSheets/public.css"> | ||
| <link rel="alternate stylesheet" type="text/css" title="2004" href="https://www.w3.org/2004/02/minutes-style.css"> | ||
| <link rel="alternate stylesheet" type="text/css" title="Fancy" href="https://www.w3.org/StyleSheets/scribe2/fancy.css"> | ||
| <link rel="alternate stylesheet" type="text/css" title="Typewriter" href="https://www.w3.org/StyleSheets/scribe2/tt-member.css"> | ||
| </head> | ||
|
|
||
| <body> | ||
| <header> | ||
| <p><a href="https://www.w3.org/"><img src="https://www.w3.org/StyleSheets/TR/2016/logos/W3C" alt=W3C border=0 height=48 width=72></a></p> | ||
|
|
||
| <h1>DPVCG Meeting Call</h1> | ||
| <h2>14 FEB 2024</h2> | ||
|
|
||
| <nav id=links> | ||
| <a href="https://www.w3.org/events/meetings/31f00434-f01b-431d-a9d9-4ef690dd7c6d/20240214T150000/"><img alt="Agenda." title="Agenda" src="https://www.w3.org/StyleSheets/scribe2/chronometer.png"></a> | ||
| </nav> | ||
| </header> | ||
|
|
||
| <div id=prelims> | ||
| <div id=attendees> | ||
| <h2>Attendees</h2> | ||
| <dl class=intro> | ||
| <dt>Present</dt><dd>beatriz, delaram, harsh, iain, paul, tytti</dd> | ||
| <dt>Regrets</dt><dd>-</dd> | ||
| <dt>Chair</dt><dd>harsh</dd> | ||
| <dt>Scribe</dt><dd>harsh</dd> | ||
| </dl> | ||
| </div> | ||
|
|
||
| <nav id=toc> | ||
| <h2>Contents</h2> | ||
| <ol> | ||
| <li><a href="#t01">Academic Paper</a></li> | ||
| <li><a href="#t02">Age Verification Concept</a></li> | ||
| <li><a href="#t03">Rights Exercise</a></li> | ||
| <li><a href="#t04">AI Act</a></li> | ||
| <li><a href="#t05">AI and Tech extensions</a></li> | ||
| <li><a href="#t06">Next Meeting</a></li> | ||
| </ol> | ||
| </nav> | ||
| </div> | ||
|
|
||
| <main id=meeting class=meeting> | ||
| <h2>Meeting minutes</h2> | ||
| <section><p id=x007 class=summary>Meeting minutes: <a href="https://w3id.org/dpv/meetings">https://<wbr>w3id.org/<wbr>dpv/<wbr>meetings</a></p> | ||
| <p id=x008 class=summary>purl for this meeting: <a href="https://w3id.org/dpv/meetings/meeting-2024-02-14">https://<wbr>w3id.org/<wbr>dpv/<wbr>meetings/<wbr>meeting-2024-02-14</a></p> | ||
| </section> | ||
|
|
||
| <section> | ||
| <h3 id=t01>Academic Paper</h3> | ||
| <p id=x010 class="phone s01"><cite>beatriz:</cite> propose to publish DPV as a paper at ISWC 2024 in resource track about the updates to DPV from the previous paper at ODBASE in 2019. Advantages are publications and outreach in ISWC which is the prime sem-web community. Disadvantages are that its not open access, and that the audience may not grasp the way we have done DPV based on legal requirements. Discussing here whether people are interested.</p> | ||
| <p id=x011 class=summary> ISWC Resource Track CFP <a href="https://iswc2024.semanticweb.org/event/3715c6fc-e2d7-47eb-8c01-5fe4ac589a52/websitePage:453b107c-014c-4170-acce-27e28e83a2a9">https://<wbr>iswc2024.semanticweb.org/<wbr>event/<wbr>3715c6fc-e2d7-47eb-8c01-5fe4ac589a52/<wbr>websitePage:453b107c-014c-4170-acce-27e28e83a2a9</a></p> | ||
| <p id=x012 class="phone s02"><cite>paul:</cite> how/what is a resource paper as compared to a research paper?</p> | ||
| <p id=x013 class="phone s01"><cite>beatriz:</cite> it is a description about the resource (i.e. DPV), so its methodology, lessons learned, way it was developed and tested, etc. Deadline is due APR-17 for full paper. Conference is in Maryland, USA.</p> | ||
| <p id=x014 class="phone s02"><cite>paul:</cite> what is the scope of this paper? Is it privacy or also include AI etc.?</p> | ||
| <p id=x015 class="phone s01"><cite>beatriz:</cite> whatever is there in v2, but also talking about AI stuff e.g. delaram has lots of work on this</p> | ||
| <p id=x016 class="phone s02"><cite>paul:</cite> will there be a state of the art on the topic?</p> | ||
| <p id=x017 class="phone s01"><cite>beatriz:</cite> there is a journal paper about literature on vocabularies, but not sure if there is a detailed section on literature review for resource paper </p> | ||
| <p id=x018 class=summary> The group agreed this would be a good idea. </p> | ||
| </section> | ||
|
|
||
| <section> | ||
| <h3 id=t02>Age Verification Concept</h3> | ||
| <p id=x020 class=bot><cite><ghurlbot></cite> <strong><a href="https://github.com/w3c/dpv/issues/128">Issue 128</a></strong> Add dpv:AgeVerification as a purpose concept (by besteves4)</p> | ||
| <p id=x021 class="phone s03"><cite>harsh:</cite> The issue has had a discussion, with a potential agreement and resolution. Please refer to the issue for more details, and to continue discussions. </p> | ||
| </section> | ||
|
|
||
| <section> | ||
| <h3 id=t03>Rights Exercise</h3> | ||
| <p id=x023 class=bot><cite><ghurlbot></cite> <strong><a href="https://github.com/w3c/dpv/issues/63">Issue 63</a></strong> Add Right Non-fulfilment Justifications for GDPR’s rights (by besteves4)</p> | ||
| <p id=x024 class="phone s01"><cite>beatriz:</cite> continuing work from earlier - shared the work with Georg and Paul for review. Discussion between Georg and Harsh regarding legal rights and contractual rights as purposes.</p> | ||
| <p id=x025 class="phone s03"><cite>harsh:</cite> It has been (potentially) resolved by considering Legal Rights as a distinct concept, with Contractual Rights being covered by the Fulfilment of Contractual Obligations purpose. The descriptions of these concepts should reflect that.</p> | ||
| <p id=x026 class="phone s01"><cite>beatriz:</cite> Tasks for next week to continue reviewing and finalise the concepts.</p> | ||
| </section> | ||
|
|
||
| <section> | ||
| <h3 id=t04>AI Act</h3> | ||
| <p id=x028 class=bot><cite><ghurlbot></cite> <strong><a href="https://github.com/w3c/dpv/issues/106">Issue 106</a></strong> Propose concepts from the AI Act (by coolharsh55)</p> | ||
| <p id=x029 class="phone s04"><cite>delaram:</cite> the AI Act concepts are around 121 at the moment. Some of these will go to the AI extension, some to the Tech, and some to AI Act extension. What to name the extension for the AI Act? AIA?</p> | ||
| <p id=x030 class="phone s03"><cite>harsh:</cite> let's call it "AI Act" as "AIA" may also be confused with "Algorithmic Impact Assessment"?</p> | ||
| <p id=x031 class="phone s04"><cite>delaram:</cite> The concepts include entities etc. and different types of AI Systems which are complex. E.g. Emotion Recognition System - emotion recognition is a capability so do we model it as a subtype of AI system or express it as an relation e.g. hasCapability?</p> | ||
| <p id=x032 class="phone s05"><cite>georg:</cite> What is the difference between capability and activity?</p> | ||
| <p id=x033 class="phone s03"><cite>harsh:</cite> Capability as in feature or the tech is capable of doing this, so the technical purpose which we distinguish from the 'end purpose'</p> | ||
| <p id=x034 class="phone s03"><cite>harsh:</cite> If a concept is relevant in law, especially if it occurs as a definition or prominently is the subject of an article, we have to model it as a concept as DPV is foremost a 'vocabulary'. The other relations as the one mentioned can be modelled using OWL but first require all the necessary concepts to have been identified and be 'correct'. So for now - we can make a note e.g. as a comment to the concept about how other concepts and relations are associated with this concept.</p> | ||
| <p id=x035 class="phone s05"><cite>georg:</cite> How up to date is this with the latest version of the Act?</p> | ||
| <p id=x036 class="phone s04"><cite>delaram:</cite> Its work in progress, but its based on the leaked version - so quite up to date.</p> | ||
| <p id=x037 class="phone s04"><cite>delaram:</cite> How to deal with modelling concepts across ISO and AI Act?</p> | ||
| <p id=x038 class="phone s03"><cite>harsh:</cite> ISO is a global agreement standard - so we use that as the baseline e.g. in DPV or in Tech extension. In retrospect, the core DPV definitions and terms should have used ISO, but we started with a EU/GDPR specific perspective - so that's to late to be fixed now. If a ISO-defined term is compatible with AI Act, but the term in AI Act has legal relevance (e.g. explicitly defined) then it must be repeated in the AI Act extension. Otherwise if it is trivial and not necessary (i.e. we can rely on the generic term from DPV), then it doesn't need to go in the AI Act extension. If the term is not compatible (e.g. ISO and AI Act differ and are not compatible) - then there will not be any relation between them (maybe as related) but they can share a common parent.</p> | ||
| </section> | ||
|
|
||
| <section> | ||
| <h3 id=t05>AI and Tech extensions</h3> | ||
| <p id=x040 class=bot><cite><ghurlbot></cite> <strong><a href="https://github.com/w3c/dpv/issues/126">Issue 126</a></strong> AI Extension to provide AI-specific concepts (by coolharsh55)</p> | ||
| <p id=x041 class="phone s04"><cite>delaram:</cite> potential issues or ambiguity regarding how the concepts should be referenced - do they do in DPV or Tech or AI extension?</p> | ||
| <p id=x042 class="phone s03"><cite>harsh:</cite> if they are universal or general to personal data / technology activities - then they go to DPV. If they are specifically about the technical aspects of a technology or system, then they go in Tech. We discussed AI extension based on the assumption that there will be enough AI specific content that it warrants creating an extension for AI from Tech.</p> | ||
| <p id=x043 class="phone s03"><cite>harsh:</cite> For now - Lets think about modelling it together as a single extension called "AI & Technology", get all the concepts, and then see how and where the AI extension makes sense</p> | ||
| </section> | ||
|
|
||
| <section> | ||
| <h3 id=t06>Next Meeting</h3> | ||
| <p id=x045 class=summary> Next meeting will be in 1 week, on WED FEB-21 15:00 WET / 16:00 CET.</p> | ||
| <p id=x046 class=summary> Topics for discussion are updates on DPV v2, github repo and issues, rights exercise, discussion on AI Act, and Tech/AI vocabulary.</p> | ||
| </section> | ||
| </main> | ||
|
|
||
|
|
||
| <address>Minutes manually created (not a transcript), formatted by <a | ||
| href="https://w3c.github.io/scribe2/scribedoc.html" | ||
| >scribe.perl</a> version 217 (Fri Apr 7 17:23:01 2023 UTC).</address> | ||
|
|
||
| </body> | ||
| </html> |