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
Term: dpv:Tracking
Label: Tracking
Definition: collecting and/or using data to track an individual or an individual's activities across multiple distinct contexts
Parent term: dpv:Collect, dpv:Use
Source: DPVCG
Usage note: Tracking is a widely used (and abused) concept and therefore carries several distinct interpretations, for example see Do Not Track which defines tracking in the context of the web, and where other forms of tracking such as location tracking or physical biometric tracking may exist which are defined differently. For this concept, DPVCG defines Tracking in the broadest possible sense and strongly recommends adopters to provide their specific definition or interpretation by either extending this concept, through a usage note, or by contributing the specific term back to DPVCG for inclusion in DPV or an extension. This concept may change in the future based on developments in privacy and legal spaces. In DPV, Tracking is defined as a type of processing operation that may collect and/or may use data - which covers both initial collection and usage as well as subsequent use of existing data to track an individual. The classification of Tracking as a processing operation also implies that it is not sufficient as a Purpose on its own and therefore a suitable purpose from the DPV taxonomy should be used to justify it.
TrackingByFirstParty and TrackingByThirdParty should be extended with a note that these concepts do not strictly only specify the processing operation, but also the relation of the data subject with the implementing entity. These concepts may change in the future based on discussions around how to express First and Third Party.
Changed Concept(s)
Existing Term: e.g., dpv:NewConcept or risk:NewConcept
Change: e.g., change label from X to Y, or add usage note stating "xyz"
Justification: optional comment giving reasons why the change should be made
The text was updated successfully, but these errors were encountered:
- Adds `dpv:Tracking` to DPV
- Adds `dpv:TrackingByFirstParty` and `dpv:TrackingByThirdParty` to DPV
- Adds a note explaining modelling of Tracking and Profiling in HTML
- Contains RDF and HTML outputs
- NOTE: This requires a corresponding eu-gdpr:Profiling concept to
distinguish DPV's concept from GDPR's concept - that will be in a
separate commit that also addresses #186 mapping GDPR to DPV
Specs
DPV
New Concept(s)
Term: dpv:Tracking
Label: Tracking
Definition: collecting and/or using data to track an individual or an individual's activities across multiple distinct contexts
Parent term: dpv:Collect, dpv:Use
Source: DPVCG
Usage note: Tracking is a widely used (and abused) concept and therefore carries several distinct interpretations, for example see Do Not Track which defines tracking in the context of the web, and where other forms of tracking such as location tracking or physical biometric tracking may exist which are defined differently. For this concept, DPVCG defines Tracking in the broadest possible sense and strongly recommends adopters to provide their specific definition or interpretation by either extending this concept, through a usage note, or by contributing the specific term back to DPVCG for inclusion in DPV or an extension. This concept may change in the future based on developments in privacy and legal spaces. In DPV, Tracking is defined as a type of processing operation that may collect and/or may use data - which covers both initial collection and usage as well as subsequent use of existing data to track an individual. The classification of Tracking as a processing operation also implies that it is not sufficient as a Purpose on its own and therefore a suitable purpose from the DPV taxonomy should be used to justify it.
TrackingByFirstParty
andTrackingByThirdParty
should be extended with a note that these concepts do not strictly only specify the processing operation, but also the relation of the data subject with the implementing entity. These concepts may change in the future based on discussions around how to express First and Third Party.Changed Concept(s)
Existing Term: e.g., dpv:NewConcept or risk:NewConcept
Change: e.g., change label from X to Y, or add usage note stating "xyz"
Justification: optional comment giving reasons why the change should be made
The text was updated successfully, but these errors were encountered: