You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is indeed overlap. Moreover, PersonalDataType seems more like broad categories and subcategories wat is called PersonalDataCategory is clearly more specific.
In the remapped model (see issue #46) we kept one attribute Personaldata.type and propose to fuse both codelists.
Only one of the 2 broad categories used in OSLO-Consent:PersonalDataType (namely SensitivePersonalData) can be found in the DPV model:
Moreover, the DPV classification does not specify the subject of the data (eg medical, salary etc), it rather focusses on subclassing the broader classes PersonalData and NonPersonalData (the latter being eg anonymised data) altough there are some additional vategories like SyntheticData. So if there ia need for a thematic classification an extra attribute and codelist should indeed be added.
In the GDPR (and in the opnions and recommendations of the EDPB and Data Protection Authorities) the term 'categories' is used as a thematic classification: ex. Identity data, location data, data concerning health, ...
The above list seems different from that. Data 'type' is not used in the GDPR and could be used for this classification.
No description provided.
The text was updated successfully, but these errors were encountered: