-
Notifications
You must be signed in to change notification settings - Fork 30
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
6f3759d
commit 42cca14
Showing
3 changed files
with
262 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,85 @@ | ||
| 16:15:34 <RRSAgent> RRSAgent has joined #dpvcg | ||
| 16:15:44 <harsh> Scribe: harshPandit | ||
| 16:15:44 <harsh> ScribeNick: harsh | ||
| 16:15:47 <harsh> repo: w3c/dpv | ||
| 16:15:47 <ghurlbot> OK. | ||
| 16:15:55 <harsh> Meeting: DPVCG Meeting Call | ||
| 16:15:57 <harsh> Chair: beatrizEsteves | ||
| 16:16:51 <harsh> Present: harshPandit, georgKrog, paulRyan, julioHernandez, iainHenderson, julianFlake, beatrizEsteves, markLizar | ||
| 16:18:43 <harsh> Regrets: delaramGolpayegani | ||
| 16:17:14 <harsh> Date: 20 FEB 2025 | ||
| 16:17:28 <harsh> Agenda: https://www.w3.org/events/meetings/178d1c71-a92d-4da7-a196-6a89d0fe2277/20250220T133000/ | ||
| 16:17:37 <harsh> \ Meeting minutes: https://w3id.org/dpv/meetings | ||
| 16:17:47 <harsh> \ purl for this meeting: https://w3id.org/dpv/meetings/meeting-2025-02-20 | ||
| 16:17:47 <harsh> Topic: v2.1 release | ||
| 20:10:04 <ghurlbot> https://github.com/w3c/dpv/issues/235 -> Issue 235 DPV v2.1-RC hotfixes and feedback (by coolharsh55) | ||
| 16:17:47 <harsh> harsh: we had put up the v2.1 release candidate with open review until FEB-16; see https://lists.w3.org/Archives/Public/public-dpvcg/2025Feb/0002.html and https://github.com/w3c/dpv/issues/235 for hotfixes. Are we ready to publish this or do we need more time to review? | ||
| 16:15:44 <harsh> iainHenderson: +2 weeks | ||
| 16:15:44 <harsh> julioHernandez: +1 week | ||
| 16:15:44 <harsh> beatrizEsteves: +1 week | ||
| 16:15:44 <harsh> georgKrog: +2 weeks | ||
| 16:15:44 <harsh> \ group agreed to take 2 more weeks to review the release; next meeting we will identify if there are any major concerns, and then the week after that we will aim to finalise and publish | ||
| 16:15:44 <harsh> Topic: Guides | ||
| 20:10:04 <ghurlbot> https://github.com/w3c/dpv/issues/242 -> Issue 242 Provide Guides for Supporting Adoption & Use of DPV (by coolharsh55) | ||
| 16:15:44 <harsh> julianFlake: guides are needed to understand DPV and use it otherwise it is difficult to understand what to use where as there is a large amount of information and no guidance - we should prioritise having guides to help use DPV, but this is not a blocking issue for the v2.1 release (so for v2.2) | ||
| 16:15:44 <harsh> harsh: agree, we have various guides listed but they have not been completed and delivered | ||
| 16:15:44 <harsh> julianFlake: want to help, but not sure of time | ||
| 16:15:44 <harsh> harshPandit: will a structure, time help e.g. to do short tasks? | ||
| 16:15:44 <harsh> julianFlake: would prefer to discuss rather than directly write something if possible, but otherwise okay to help with a paragraph | ||
| 16:15:44 <harsh> georgKrog: guides should be easy to write (in my head) but we need to think about content | ||
| 16:15:44 <harsh> harshPandit: we have papers for several topics which we can use to put something in the document as a draft - ROPA, DPIA, Data Breach, Rights; will use this to populate the documents and then we can discuss with this as a starting point next week with the aim to v2.2 being supported with guides | ||
| 16:15:44 <harsh> paulRyan: what would be present in these guides? | ||
| 16:15:44 <harsh> harsh: see for example the consent guide https://w3id.org/dpv/guides/consent-27560 which states how to represent information for consent records using DPV and how to use it to do specific tasks | ||
| 16:15:44 <harsh> \ group agreed to make this a priority for v2.2 release | ||
| 16:15:44 <harsh> ACTION: establish working plan for implementing guides for v2.2 | ||
| 16:15:44 <harsh> Topic: v2.2 roadmap | ||
| 16:15:44 <harsh> \ see https://github.com/w3c/dpv/milestone/7 | ||
| 16:15:44 <harsh> Subtopic: latest state of consent | ||
| 20:10:04 <ghurlbot> https://github.com/w3c/dpv/issues/114 -> Issue 114 In 27560-records, how to identify the latest consent state? (by coolharsh55) | ||
| 16:15:44 <harsh> beatrizEsteves: latest state of consent, Georg mentioned he has a implementation that is different from DCAT | ||
| 16:15:44 <harsh> georgKrog: no issue with DCAT, I meant we are not doing things with DCAT | ||
| 16:15:44 <harsh> harsh: DCAT v3, pointer to latest state = keep records separately, pointer to immutable consent = record changes separately - we discuss and show how these are implemented | ||
| 16:15:44 <harsh> georgKrog: need for historical status e.g. if an org sends a newsletter based on consent, and then you withdraw the consent, and then later reconsent again | ||
| 16:15:44 <harsh> ACTION: Add note to 27560 guide for above example in intro section | ||
| 16:15:44 <harsh> Subtopic: v2.2 planning | ||
| 16:15:44 <harsh> georgKrog: commonality or priority in v2.2 tasks? | ||
| 16:15:44 <harsh> beatrizEsteves: focus for next months is EHDS | ||
| 16:15:44 <harsh> harshPandit: (on behalf of Delaram) AI Act and risks/impacts associated with AI | ||
| 16:15:44 <harsh> georgKrog: AI Act, Rights from DGA and Data Act, to map all entities in new regulations - we have for DGA, but we don't have for Data Act, DSA, DMA; | ||
| 16:15:44 <harsh> harshPandit: clarify, priority as DSA and DMA are specific and if we have limited bandwidth what do we focus on | ||
| 16:15:44 <harsh> georgKrog: at least the entities and roles as these are useful in lots of use-cases | ||
| 16:15:44 <harsh> julianFlake: preference for privacy and data protection aspects, and how these are covered or affected by additional laws - we can discuss; but not particularly interested in covering new topics | ||
| 16:15:44 <harsh> julioHernandez: extensions, concepts, how to get these to work? | ||
| 16:15:44 <harsh> harsh: guides, purpose of guides …. also tutorials – we also had the idea to do a workshop on how to build things with DPV | ||
| 16:15:44 <harsh> beatriz: agree, would be nice to have it, for the next version we should aim to have a tutorial | ||
| 16:15:44 <harsh> iainHenderson: P7012 work - we should have an update soon, and extended approach to data types and purposes | ||
| 16:15:44 <harsh> harshPandit: last week we had a small chat on Google and IAB data taxonomies and concerns around simply adopting them as is due to their misuse or not being aligned with legal implications | ||
| 16:15:44 <harsh> georgKrog: sectorial things for HR and Marketing | ||
| 16:15:44 <harsh> harshPandit: HR in DPV, marketing in sector - lets take this up when we have concrete ideas | ||
| 16:15:44 <harsh> julioHernandez: would like to see more guidance - the primer is clear, but need more help with how to use classes and properties | ||
| 16:15:44 <harsh> harshPandit: OWL, not interested in maintaining complexity, can do RDFS+SKOS examples as we go along | ||
| 16:15:44 <harsh> julioHernandez: when reading the Primer, it is not clear what can be done or not with expressiveness | ||
| 16:15:44 <harsh> harshPandit: the guide on RDFS/SKOS is supposed to help with this but as we discussed earlier it isn't available - so if we complete that it should help | ||
| 16:17:47 <harsh> Topic: AI Training | ||
| 20:10:04 <ghurlbot> https://github.com/w3c/dpv/issues/82 -> Issue 82 Provide vocabulary to specify purposes and permissions related to AI training (by scottkellum) | ||
| 16:15:44 <harsh> harsh: there was a question raised in the last meeting as to the source of concepts - I used ISO 22989 which has concepts related to training. That standard is currently being revised. There are also other standards which build on top of this for specific aspects, but haven't used them here yet. There are some new standards coming later this year for privacy in/of AI systems which should be of interest to this group. | ||
| 16:15:44 <harsh> \ discussed implication of concepts - what is the focus? | ||
| 16:15:44 <harsh> julianFlake: the focus of this group is on privacy / data protection - so we should be careful about adding things simply because they are about AI | ||
| 16:15:44 <harsh> harsh: agree - can rely on you to be the voice of caution here. We want to explore this concepts to indicate things related to privacy / data protection such as what data is being used, where does training occur, and so on. | ||
| 16:15:44 <harsh> harshsr: the questions raised at the moment are about our concepts - do these new ai + privacy concepts go to DPV or AI extension? Should training be a `Process` or `Processing`? How to note where it occurs? etc. | ||
| 16:15:44 <harsh> \ group discussed the need for use-cases to discuss this work further, harsh will circulate these based on work done so far | ||
| 16:15:44 <harsh> ACTION: harsh to share AI training use-cases on mailing list | ||
| 16:17:47 <harsh> Topic: Subjective Locations | ||
| 20:10:04 <ghurlbot> https://github.com/w3c/dpv/issues/209 -> Issue 209 [Concept]: `AtX` subjective Location concepts (by coolharsh55) | ||
| 16:15:44 <harsh> harsh: similar to AI training, explored concepts (see issue) with three use-cases: home, shop/mall CCTV, and app/device - it seems to work. | ||
| 16:15:44 <harsh> \ group discussed wanting to see use-cases and examples to discuss this work further, harsh will circulate these based on work done so far | ||
| 16:15:44 <harsh> ACTION: harsh to share subjective locations examples on mailing list | ||
| 16:17:47 <harsh> Topic: Inverted Locations | ||
| 20:10:04 <ghurlbot> https://github.com/w3c/dpv/issues/208 -> Issue 208 [Concept]: Add Non-X (X = specific location) to represent locations that are not X (by coolharsh55) | ||
| 16:15:44 <harsh> harsh: identified rationale for why these are needed, most of the time they won't be useful or they can be replace by programmatically checking e.g. location not in EU, but at other times directly specifying the non-EU concept is useful | ||
| 16:15:44 <harsh> georgKrog: this is an important aspect as there are legal procedures which consider such distinctions; so saying this applies to a jurisdiction or things outside the jurisdiction helps (i.e. for this, and for not this but other things) | ||
| 16:15:44 <harsh> \ group discussed this, and agreed to continue the discussion with further use-cases and examples | ||
| 16:15:44 <harsh> ACTION: harsh to share rationale and examples for non-EU concept to mailing list | ||
| 16:17:47 <harsh> Topic: Next Meeting | ||
| 16:17:47 <harsh> \ The next meeting will be on FEB-27 Thursday 13:30WET/14:30CET | ||
| 16:17:47 <harsh> \ Agenda will be reviewing and finalising release of v2.1, and continuing discussion on topics started under v2.2 |
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
Oops, something went wrong.