Meeting minutes
Repository: w3c/dpv
Agenda: https://
Meeting minutes: https://
Persistent ID for current minutes: https://
v2.2
<ghurlbot> Issue 301 dpv 2.2 draft review (by coolharsh55)
milestone https://
release candidate published https://
changelog https://
comment period until SEP-15
JulianFlake: 4 persons agree to release v2.2 (no objections or issues noted)
ACTION: Release v2.2
<ghurlbot> Issue 365 README: move past version links to Wiki page, keep only the latest version links (by coolharsh55)
ACTION: update readme for release
<ghurlbot> Issue 366 Create changelog for v2.2 (by coolharsh55)
ACTION: update changelogs for release
<ghurlbot> Issue 339 w3id updates for v2.2 (by coolharsh55)
ACTION: update w3id for v2.2 release
Generic Places
<ghurlbot> Issue 384 Modelling Generic Locations/Places (e.g. Airport, School) (by coolharsh55)
JulianFlake: any news on this topic?
ArthitSuriyawongkul: Summarizes subjective locations and categories of non-subjective locations and distinguishes them from physical locations.
JulianFlake: AtHome, AtWork could/should become part of PD extension, some other concepts (school, train, airport) could/should become part of a specific sector extension
ArthitSuriyawongkul: School, airport, hospital are "abstract" (or logical). School and hospital could be subjective ("my school" and "my hospital", for a regular patient), but airport is not so subjective. Implications of expressing logical locations should be taken into considerations since they can reveal personal data. For example, the fact that a person visit a particular clinic chain/brand (not necessarily a physical location) may reveal the person's religion or association with a trade union in a country that the primary healthcare service or health insurance tend to offered by religious-organization or trade-union.
JulianFlake: First thing is to decide, whether we want to include such concepts now or if we can find a betterfoundation for / existing source of concepts to base on or to connect with.
ChristianDraeger: intuitively I'd think, there exists some vocabulary, somewhere.
AOB - LEGAL DE-GDNG
<ghurlbot> Issue 387 Extension for the German GDNG (by chhdraeger)
ChristianDraeger: ChristianDraeger introduces himself and GNDG.
JulianFlake: Challenging: German regulation without translation.
ChristianDraeger: We should not expect an English translation in a timely manner. Therefore, the German GDNG should serve as basis. Where do we start? Do we have a Excel file or create a new one?
ArthitSuriyawongkul: Technically, source of truth is typically a Google Sheet. XLSX is extracted, CSV is generated from XLSX, etc. (by python scripts in the repo).
JulianFlake: First step is to pupulate one table
ChristianDraeger: Still not sure, who will work on this.
ArthitSuriyawongkul: A good idea is to create a GitHub issue first, so others can participate voluntarily.
TyttiRintamäki: I work on Impact Assessments in context of DPIA and had to work on different legal texts and the EU's "eTranslation service" (NN trained on legal texts) is of great help. Link: https://
ChristianDraeger: A template of a Google Sheet would be helpful.
JulianFlake: We could setup a meeting for the discussion on this German regulation. I'll try to setup a sheet until then (or ask Harsh).
ChristianDraeger: time estimation for the whole extraction process?
TyttiRintamäki: A month could be sufficient.
ChristianDraeger: Can we have a preview on EHDS concepts?
JulianFlake: I'll ask Beatriz.
Agenda items not discussed
<ghurlbot> Issue 287 [NEW]: Add Maintenance as a `dpv:Purpose` (by besteves4)
<ghurlbot> Issue 298 Model Purpose Compatibility statuses for GDPR (by coolharsh55)
<ghurlbot> Issue 386 Model Proportionality for GDPR (by coolharsh55)
<ghurlbot> Issue 385 Align DPV with CRDM AI concepts (by coolharsh55)
Next Meeting
The next meeting will be on SEP-24 Thursday 13:30WEST/14:30CEST
Agenda will be continuation of today's discussion regarding generic places, service maintainence, purpose compatibility, and proportionality/necessity.