Categorisation of data subjects based on jurisdiction e.g. citizens or location for GDPR

[coolharsh55]

| Migrated ISSUE-6: Should our taxonomy include a distinction/modeling of data subjects to whom gdpr applies (eu citizens and/or located in eu)

State: RAISED
Opened on: 2018-12-04

Related Emails:

1. +[minutes] 2019-10-15 dpvcg (from bert@w3.org on 2019-10-15)
2. +ISSUE-6: Should our taxonomy include a distinction/modeling of data subjects to whom gdpr applies (eu citizens and/or locatedin eu) (from sysbot+tracker@w3.org on 2018-12-04)

Related notes:

1. in the context of ISSUE-6 is “non-applicable citizens only” a “legal ground”? - Axel Polleres, 4 Dec 2018, 10:07:55
2. related to ACTION-93 - Axel Polleres, 5 Apr 2019, 13:21:00
3. RESOLVED: We leave the further specification of specific subclasses of DataSubjects out of scope of the current CG, the spec provides just one example, dpv:Child that could serve as an illustration for other subclasses affecting certain groups of DataSubjects (e.g. Citizens of certain states to which a particular legislation applies, etc.) with this rationale we postpone ISSUE-6. - Axel Polleres, 15 Oct 2019, 14:47:37

[coolharsh55]

There is a proposal tabled for data subject categories - this issue will be updated based on the progress of that.

[coolharsh55]

Data Subject categories relevant for this issue have been added to DPV v0.6 - see https://w3id.org/dpv#vocab-entities-datasubject These include concepts such as Citizens, Consumers, Clients, etc. which should cover most of applicability criteria. Note that secondary information would still need to be modeled e.g. citizen of what/where, consumer of what, and so on. Currently, such information is not within the scope of the group, with a general suggestion to model it as concepts with description e.g. EUCitizens as a subclass / sub-concept of Citizen. This issue will be kept open for inviting discussion.

[coolharsh55]

Adding a note to the above comment regarding modelling specifics of data subject categories. For those tied to locations or jurisdictions, the DPV-LEGAL concepts can be used. For example, EUCitizens as a subtype/instance of dpv:DataSubject and using dpv:hasLocation legal:EU to indicate the relevance to EU as its location or basis.

[coolharsh55]

If there are no further developments for this, I will mark this as resolved on OCT-15.