OSLO Consent should map on DPV rather than on GConsent

Informatievlaanderen / OSLOthema-consent

GitHub repository for the OSLO trajectory "consent"

0 stars 0 forks source link

OSLO Consent should map on DPV rather than on GConsent #46

Open GeertThijs opened 1 year ago

GeertThijs commented 1 year ago

Reasons for this:

DPV is in version 0.8 (sept 2022) and close to version 1.0, as opposed to GConsent which is in version 0.5 since 2018.
GConsent only covers Consent as a LegalBasis, DPV covers all kinds.
At the same time Consent is covered in an exhaustive way in DPV, GConsent not really adds something.
DPV has PersonalDataHandling as the central class, in stead of treating one aspect of it as central (namely the Consent).

GeertThijs commented 1 year ago

We tried remapping the current OSLO-Consent model to DPV with the following result: OSLO-Consent-remapped2DPV Read more about that in the modelling report (explains what changed compared to current OSLO-Consent and why). As an illustration, a simple example implementing the remapped model is available.