Source: http://www.w3.org/ns/dpv
Timestamp: 2020-02-17 06:07:28
Document Index: 263055121

Matched Legal Cases: ['art_4', 'art_4', 'art_4', 'art_4', 'Art. 9', 'art_9', 'Art. 9', 'art_4', 'art_4', 'art_4', 'art 35', 'art_4', 'art_4', 'art_4']

Data Privacy Vocabulary v0.1
Draft Community Group Report 28 November 2019
https://w3.org/ns/dpv
Harshvardhan J. Pandit (Trinity College Dublin)
Bert Bos (W3C/ERCIM)
Rob Brennan (Dublin City University)
Bud Bruegger (Unabhängige Landeszentrum für Datenschutz Schleswig-Holstein)
Fajar J. Ekaputra (Vienna University of Technology)
Javier D. Fernández (Vienna University of Economics and Business)
Ramisa Gachpaz Hamed (Trinity College Dublin)
Elmar Kiesling (Vienna University of Technology)
Mark Lizar (OpenConsent/Kantara Initiative)
Eva Schlehahn (Unabhängige Landeszentrum für Datenschutz Schleswig-Holstein)
Simon Steyskal (Siemens)
Copyright © 2019 the Contributors to the Data Privacy Vocabulary v0.1 Specification, published by the Data Privacy Vocabularies and Controls Community Group under the W3C Community Contributor License Agreement (CLA). A human-readable summary is available.
The Data Privacy Vocabulary (DPV) provides terms (classes and properties) to annotate and categorize instances of legally compliant personal data handling according to the EU General Data Protection Regulation. This scope could be extended by later versions to other data and privacy protection regulations. The vocabulary provides terms to describe which personal data Categories are undergoing a specified kind of processing by a specific data controller and/or transferred to some recipient for a particular purpose, based on a specific legal ground (e.g., consent, or other legal grounds such as legitimate interest, etc.), with specified technical and organisational measures and restrictions (e.g., storage locations and storage durations) in place.
The namespace for DPV terms is http://www.w3.org/ns/dpv#
The suggested prefix for the DPV namespace is dpv
The DPV ontology is available here.
The Github repository for DPV is here.
This specification was published by the Data Privacy Vocabularies and Controls Community Group. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the W3C Community Contributor License Agreement (CLA) there is a limited opt-out and other conditions apply. Learn more about W3C Community and Business Groups.
This document was published by the Data Privacy Vocabularies and Controls Community Group (DPVCG) as a first public working draft.
If you wish to make comments regarding this document, please send them to public-dpvcg@w3.org (subscribe, archives).
The DPVCG requests participation regarding open issues and welcomes suggestions on their resolution or mitigation. The list of open issues and their discussions to date can be found at https://www.w3.org/community/dpvcg/track/issues/open. Specifically, the DPVCG kindly requests proposals to extend its initial taxonomies by additional terms, where these are missing or need refinements in order to describe specific use cases of personal data handling. A list of issues at the time of creating this document can be found here. Other forms of participation such as comments and feedback are also welcome.
While we welcome participation via any and all mediums - e.g., via Github pull requests or issues, emails, papers, or reports - the formal resolution of contributions will be done via the DPVCG meeting calls and mailing lists. We therefore would suggest submitting suggestions there for discussion of formal approval.
In order to propose/approve new terms, please include the following:
term - suggested URI/identifier
class/property - is the suggested term a class or a property?
description - a natural language description of the term as to be included in the vocabulary to describe the term in an unambiguous manner.
domain/range - for properties include information about domain and range
superclasses/subclasses - for classes include (if applicable) information about known sub/super-classes.
superproperties/subproperties - for properties include (if applicable) information about known sub/super-properties.
related terms - include if applicable otherwise related terms from other vocabularies and explain how they are related (e.g., skos:broader/skos:narrower, rdfs:seeAlso).
source - mention where the new term originates from (e.g., from a legal regulation or from an existing ontology, if possible with a link confirming the reference.
3. Base Vocabulary
3.1.1 Data Controller
3.1.2 Data Subject
3.1.4 Personal Data Category
3.1.5 Personal Data Handling
3.1.6 Processing
3.1.7 Purpose
3.1.8 Recipient
3.1.9 Technical Organisational Measure
3.2.1 has Data Controller
3.2.2 has Data Subject
3.2.3 has Legal Basis
3.2.4 has Personal Data Category
3.2.5 has Processing
3.2.6 has Purpose
3.2.7 has Recipient
3.2.8 has Technical Organisational Measure
4.1.1 Accent
4.1.2 Account Identifier
4.1.3 Acquantaince
4.1.5 Apartment Owned
4.1.6 Association
4.1.7 Attitude
4.1.8 Authenticating
4.1.9 Bank Account
4.1.10 Behavioral
4.1.11 Biometric
4.1.12 Blood Type
4.1.13 Browser Fingerprint
4.1.14 Browsing Behavior
4.1.15 Call Log
4.1.16 Car Owned
4.1.17 Certification
4.1.18 Character
4.1.19 Communication
4.1.20 Communications Metadata
4.1.21 Connection
4.1.22 Contact
4.1.23 Country
4.1.24 Credit
4.1.25 Credit
4.1.26 Credit Capacity
4.1.27 Credit Card Number
4.1.28 Credit Record
4.1.29 Credit Score
4.1.30 Credit Standing
4.1.31 Credit Worthiness
4.1.32 Criminal
4.1.33 Criminal Charge
4.1.34 Criminal Conviction
4.1.35 Criminal Pardon
4.1.36 DNACode
4.1.37 Demeanor
4.1.38 Demographic
4.1.39 Derived Personal Data
4.1.40 Device Based
4.1.41 Dialect
4.1.42 Disability
4.1.43 Disciplinary Action
4.1.44 Dislike
4.1.45 Divorce
4.1.46 Drug Test Result
4.1.47 Email Address
4.1.48 Email Content
4.1.49 Employment History
4.1.50 Ethnic Origin
4.1.51 Ethnicity
4.1.52 External
4.1.53 Family
4.1.54 Family Health History
4.1.55 Family Structure
4.1.56 Favorite
4.1.57 Favorite Color
4.1.58 Favorite Food
4.1.59 Favorite Music
4.1.60 Fetish
4.1.61 Financial
4.1.62 Financial Account
4.1.63 Financial Account Number
4.1.64 Fingerprint
4.1.65 Friend
4.1.66 GPSCoordinate
4.1.67 Gender
4.1.68 General Reputation
4.1.69 Geographic
4.1.70 Group Membership
4.1.71 Hair Color
4.1.72 Health
4.1.73 Health History
4.1.74 Health Record
4.1.75 Height
4.1.76 Historical
4.1.77 House Owned
4.1.78 IPAddress
4.1.79 Identifying
4.1.80 Income
4.1.81 Income Bracket
4.1.82 Individual Health History
4.1.83 Intention
4.1.84 Interaction
4.1.85 Interest
4.1.86 Internal
4.1.87 Job
4.1.88 Knowledge Belief
4.1.89 Language
4.1.90 Life History
4.1.91 Like
4.1.92 Link Clicked
4.1.93 Loan Record
4.1.94 Location
4.1.95 MACAddress
4.1.96 Marital Status
4.1.97 Marriage
4.1.98 Medical Health
4.1.99 Mental Health
4.1.100 Name
4.1.101 Official ID
4.1.102 Offspring
4.1.103 Opinion
4.1.104 Ownership
4.1.105 PINCode
4.1.106 Parent
4.1.107 Password
4.1.108 Personal Possession
4.1.109 Personality
4.1.110 Philosophical Belief
4.1.111 Physical Address
4.1.112 Physical Characteristic
4.1.113 Physical Health
4.1.114 Physical Trait
4.1.115 Picture
4.1.116 Piercing
4.1.117 Political Affiliation
4.1.118 Preference
4.1.119 Prescription
4.1.120 Privacy Preference
4.1.121 Proclivitie
4.1.122 Professional
4.1.123 Professional Evaluation
4.1.124 Professional Interview
4.1.125 Public Life
4.1.126 Purchase
4.1.127 Purchases And Spending Habit
4.1.128 Race
4.1.129 Reference
4.1.130 Relationship
4.1.131 Religion
4.1.132 Religious Belief
4.1.133 Retina
4.1.134 Room Number
4.1.135 Salary
4.1.136 Sale
4.1.137 School
4.1.138 Secret Text
4.1.139 ServiceConsumptionBehavior
4.1.140 Sexual
4.1.141 Sexual History
4.1.142 Sexual Preference
4.1.143 Sibling
4.1.144 Skin Tone
4.1.145 Social
4.1.146 Social Media Communication
4.1.147 Social Network
4.1.148 Social Status
4.1.149 Special Category Personal Data
4.1.150 Tattoo
4.1.151 Tax
4.1.152 Telephone Number
4.1.153 Thought
4.1.154 Tracking
4.1.155 Transaction
4.1.156 Transactional
4.1.157 TV Viewing Behavior
4.1.158 UID
4.1.159 Username
4.1.160 Voice Communication Recording
4.1.161 Voice Mail
4.1.162 Weight
4.1.163 Work History
5.1.3 Beneficiary
5.1.4 Commercial Interest
5.1.5 Commercial Research
5.1.6 Context
5.1.7 Create Event Recommendations
5.1.8 Create Personalized Recommendations
5.1.9 Create Product Recommendations
5.1.10 Customer Care
5.1.11 Delivery Of Goods
5.1.12 Fraud Prevention And Detection
5.1.13 Identity Verification
5.1.14 Improve Existing Products And Services
5.1.15 Improve Internal CRMProcesses
5.1.16 Increase Service Robustness
5.1.17 Internal Resource Optimisation
5.1.18 Non Commercial Research
5.1.19 Optimisation For Consumer
5.1.20 Optimisation For Controller
5.1.21 Optimise User Interface
5.1.22 Personalised Benefits
5.1.23 Research And Development
5.1.24 Sector
5.1.25 Security
5.1.26 Sell Data To Third Parties
5.1.27 Sell Insights From Data
5.1.28 Sell Products To Data Subject
5.1.29 Sell Targetted Advertisements
5.1.30 Service Optimization
5.1.31 Service Personalization
5.1.32 Service Provision
5.1.33 User Interface Personalisation
5.2.1 has Beneficiary
5.2.2 has Context
5.2.3 has Sector
6. Processing Categories
6.1.1 Acquire
6.1.2 Adapt
6.1.3 Align
6.1.4 Alter
6.1.5 Analyse
6.1.6 Anonymise
6.1.7 Collect
6.1.8 Combine
6.1.9 Consult
6.1.10 Copy
6.1.11 Derive
6.1.12 Destruct
6.1.13 Disclose
6.1.14 Disclose By Transmission
6.1.15 Disseminate
6.1.16 Erase
6.1.17 Make Available
6.1.18 Move
6.1.19 Obtain
6.1.20 Organise
6.1.21 Profiling
6.1.22 Pseudo Anonymise
6.1.23 Record
6.1.24 Remove
6.1.25 Restrict
6.1.26 Retrieve
6.1.27 Share
6.1.28 Store
6.1.29 Structure
6.1.30 Transfer
6.1.31 Transform
6.1.32 Transmit
6.1.33 Use
6.2.1 innovative Use Of New Solutions
6.2.2 is Automated Decision Making
6.2.3 is Evaluation Scoring
6.2.4 is Large Scale
6.2.5 is Matching Combining
6.2.6 is Systematic Monitoring
7.1.1 Access Control Method
7.1.2 Anonymization
7.1.3 Authentication Protocols
7.1.4 Authorisation Procedure
7.1.5 Certification
7.1.6 Certification Seal
7.1.7 Code Of Conduct
7.1.8 Contract
7.1.9 De Identification
7.1.10 Design Standard
7.1.11 Encryption In Rest
7.1.12 Encryption In Transfer
7.1.13 Guidelines Principle
7.1.14 Legal Agreement
7.1.15 NDA
7.1.16 Organisational Measure
7.1.17 Privacy By Default
7.1.18 Privacy By Design
7.1.19 Pseudo Anonymization
7.1.20 Pseudonymisation Encryption
7.1.21 Regularity Of Recertification
7.1.22 Risk Management Procedure
7.1.23 Seal
7.1.24 Staff Training
7.1.25 Storage Deletion
7.1.26 Storage Duration
7.1.27 Storage Location
7.1.28 Storage Restoration
7.1.29 Storage Restriction
7.1.30 Technical Measure
7.2.1 duration
7.2.3 measure Implemented By
7.2.4 storage
8.1.2 Legal Entity
8.2.1 consent Notice
8.2.2 expiry
8.2.3 expiry Condition
8.2.4 expiry Time
8.2.5 is Explicit
8.2.6 provision By
8.2.7 provision By Justification
8.2.8 provision Method
8.2.9 provision Time
8.2.10 withdrawal By
8.2.11 withdrawal By Justification
8.2.12 withdrawal Method
8.2.13 withdrawal Time
9. Recipients, Data Controllers, and Data Subjects
9.1.1 Child
9.1.2 Data Processor
The Data Privacy Vocabulary provides terms (classes and properties) to annotate and categorize instances of legally compliant personal data handling. In particular, the vocabulary provides extensible taxonomies of terms to describe the following components:
Recipients, Data Controllers, Data Subjects
These terms are intended to annotate Legal Personal Data Handling in a machine-readable fashion, by specifying which personal data categories are undergoing a specific kind of processing, by a specific data controller and/or shared with some recipient for a particular purpose, based on a specific legal ground (e.g., consent or legitimate interest), with specific technical and organisational measures and restrictions (e.g., storage location and storage duration) in place.
As the Legal Bases are dependant on legal jurisdictions, we provide the GDPR legal bases (based on Article 6 and Article 9) under a separate aligned vocabulary here.
Descriptions and respective annotations of Legal Personal Data Handling could be used for example to:
declare personal data handling policies,
declare consent for a personal data handling policy (by a specific consent action),
transparently log/document specific personal data handling actions by a data controller, and finally
to support automated checking of legal compliances of data handling ex ante (before data handling is actually performed), or ex-post (i.e. check compliance to a certain policy and/or consent)
The namespace for DPV vocabulary is http://www.w3.org/ns/dpv#. The table below indicates the full list of namespaces and prefixes used in this document.
dpv http://www.w3.org/ns/dpv#
dpv-gdpr http://www.w3.org/ns/dpv-gdpr#
dpv-nace http://www.w3.org/ns/dpv-nace#
spl http://www.specialprivacy.eu/langs/usage-policy#
svd http://www.specialprivacy.eu/vocabs/data#
svdu http://www.specialprivacy.eu/vocabs/duration#
svl http://www.specialprivacy.eu/vocabs/locations#
svpu http://www.specialprivacy.eu/vocabs/purposes#
svpr http://www.specialprivacy.eu/vocabs/processing#
svr http://www.specialprivacy.eu/vocabs/recipients
The ‘Base Vocabulary’ describes the top-level classes defining a policy for legal personal data handling. Classes and properties for each top-level class are further elaborated using sub-vocabularies, e.g., the Personal Data taxonomy. While all concepts within the vocabulary share a single namespace, the modular approach makes it possible to use the sub-vocabularies without the :PersonalDataHandling class, for example to refer only to purposes. Exceptions to this are the NACE purpose taxonomy extending the :Sector concept in the Purposes vocabulary, and the GDPR legal bases taxonomy extending the top-level :LegalBasis class, which are provided under a separate namespace to indicate their specialisation.
Figure 1 Base Vocabulary
An instance of PersonalDataHandling is associated with one or more instances of Personal Data Category, Purpose, Processing, Recipient, Technical and Organisation Measures, Legal Basis, and Data Controller. The vocabulary provides relevant properties for associating each top-level concept with the PersonalDataHandling class, such as hasPurpose and hasDataSubject to associate with Purpose and Data Subject respectively.
Currently, the DPV vocabulary does not provide any constraints on the inclusion or exclusion of concepts used to define an instance of PersonalDataHandling. Possibilities for this include use of OWL2 semantics and SHACL to define concepts mandatory in an instance of PersonalDataHandling. For example, one could define that every instance of PersonalDataHandling *MUST* have at least one Personal Data Category, Controller, Purpose, and Legal Basis.
The DPV base ontology is available as an individual module here.
:DataController | :DataSubject | :LegalBasis | :PersonalDataCategory | :PersonalDataHandling | :Processing | :Purpose | :Recipient | :TechnicalOrganisationalMeasure
dpv:DataController
Description: The class of Data Controllers that control this particular data handling, any legal entity that is defined by article 4.7 of GDPR.
Source: https://eur-lex.europa.eu/eli/reg/2016/679/art_4/par_7/pnt_g/oj
Date Created: 2019-04-04
Date Approved: 2019-04-05
Approval Resolution: https://www.w3.org/2019/04/05-dpvcg-minutes.html
Contributor: Axel Polleres, Javier Ferenandez
dpv:DataSubject
Description: The class of Data Subject that this particular data handling applies to, any legal entity that is defined by article 4.1 of GDPR.
in Range of: dpv:hasDataSubject
Source: https://eur-lex.europa.eu/eli/reg/2016/679/art_4/par_1/pnt_g/oj
Notes: The alternative to bind a user or role of users to a policy could be to have a special property "hasPersonalDataHandling"
dpv:LegalBasis
Description: A particular legal Basis, which permits personal Data handling (e.g., Consent, etc.)
in Range of: dpv:hasLegalBasis
Source: DPVCG
dpv:PersonalDataCategory
Description: A category of personal data (as defined by GDPR article 4.1) from the personal data categories taxonomy, i.e. for instance denoting the category of an object/field or data item that is used for processing
Comments: Harsh: Change name to PersonalDataCategory since DataCategory can be non-personal data. Axel: Agreed
in Range of: dpv:hasPersonalDataCategory
Source: DPVCG, SPECIAL Usage Policy Language, https://eur-lex.europa.eu/eli/reg/2016/679/art_4/par_1/pnt_g/oj
Contributor: Harshvardhan Pandit, Axel Polleres
Notes: Decide whether we define relation as a super or subclass of SPL, proposal: owl:equivalentClass
Related Terms: rdfs:seeAlso spl:AnyData
dpv:PersonalDataHandling
Description: Top Class to describe a concrete instance of legal personal Data Handling of a defined class of Data Subjects, meaning that a personal Data Category is undergoing specified processing by a specific data controller and/or transferred to some recipient for a particular purpose, based on a specific legal ground, with specified security measures and restrictions (e.g., storage locations and storage durations).
in Domain of: dpv:hasDataController, dpv:hasDataSubject, dpv:hasLegalBasis, dpv:hasPersonalDataCategory, dpv:hasProcessing, dpv:hasPurpose, dpv:hasRecipient, dpv:hasTechnicalOrganisationalMeasure
dpv:Processing
Description: A type of processing from one of the processing categories in the processing Taxonomy
is Parent Class of: odrl:Action
in Range of: dpv:hasProcessing
Source: DPVCG, SPECIAL Usage Policy Language
Related Terms: rdfs:seeAlso spl:AnyProcessing
dpv:Purpose
Description: The purpose of Data Handling, from the purposes Taxonomy
in Range of: dpv:hasPurpose
Related Terms: rdfs:seeAlso spl:AnyPurpose
dpv:Recipient
Description: The entities that can access the result of a data handling action/processing, any legal entity that is defined by article 4.9 of GDPR, which states - 'recipient' means a natural or legal person, public authority, agency or another body, to which the personal data are disclosed, whether a third party or not.
in Range of: dpv:hasRecipient
Source: DPVCG, SPECIAL Usage Policy Language, https://eur-lex.europa.eu/eli/reg/2016/679/art_4/par_9/pnt_g/oj
Related Terms: rdfs:seeAlso spl:AnyRecipient
dpv:TechnicalOrganisationalMeasure
Description: Technical and organisational measures, for instance security measure, storage restrictions etc. required/followed when processing data of the declared category
Comments: Bud: rename according to GDPR: Technical/Organisational measures
Contributor: Bud Bruegger
:hasDataController | :hasDataSubject | :hasLegalBasis | :hasPersonalDataCategory | :hasProcessing | :hasPurpose | :hasRecipient | :hasTechnicalOrganisationalMeasure
dpv:hasDataController
Description: This property associates a data controller with an instance of legal data handling or consent
Comments: We replicate all the properties except legal basis of personal data handling for consent, to declare what kinds of personal data handling are consented to
Domain: dpv:PersonalDataHandling ∪ dpv:Consent
Range: dpv:DataController
Contributor: Axel Polleres, Javier Ferenandez, Harshvardhan J. Pandit, Mark Lizar, Bud Bruegger
dpv:hasDataSubject
Description: This property associates a data subject with an instance of legal data handling or consent
Range: dpv:DataSubject
dpv:hasLegalBasis
Description: This property associates an instance of legal data handling with its underlying legal basis
Domain: dpv:PersonalDataHandling
Range: dpv:LegalBasis
dpv:hasPersonalDataCategory
Description: This property associates a personal data category with an instance of legal data handling or consent
Range: dpv:PersonalDataCategory
dpv:hasProcessing
Description: This property associates a data processing category with an instance of legal data handling or consent
Range: dpv:Processing
dpv:hasPurpose
Description: This property associates a purpose with an instance of legal data handling or consent
Range: dpv:Purpose
dpv:hasRecipient
Description: This property associates a recipient with an instance of legal data handling or consent
Range: dpv:Recipient
dpv:hasTechnicalOrganisationalMeasure
Description: This property associates a technical/organisational measure with an instance of legal data handling or consent
Range: dpv:TechnicalOrganisationalMeasure
DPVCG provides broad top-level personal data categories adapted from the taxonomy provided by EnterPrivacy. The top-level concepts in this taxonomy refer to the nature of information (financial, social, tracking) and to its inherent source (internal, external). Each top-level concept is represented in the DPVCG vocabulary as a Class, and is further elaborated by subclasses for referring to specific categories of information - such as preferences or demographics.
Regulations such as the GDPR allow information about personal data used in processing to be provided either as specific instances of persona data (e.g., “John Doe”) or as categories (e.g., name). Additionally, the class SpecialCategoryPersonalData represents categories that are ‘special’ or ‘sensitive’ and require additional conditions as per GDPR’s Article 9.
The categories defined in the personal data taxonomy can be used directly or further extended to refer to the scope of personal data used in processing. The taxonomy can be extended by subclassing the respective classes to depict specialised concepts, such as “likes regarding movies” or combined with classes to indicate specific contexts. The class DerivedPersonalData one such context where information has been derived from existing information, e.g., inference of opinions from social media. Additional classes can be defined to specify contexts such as use of machine learning, accuracy, and source.
While the taxonomy is by no means exhaustive, the aim is to provide a sufficient coverage of abstract categories of personal data which can be extended using the subclass mechanism to represent concepts used in the real-world.
The property :hasPersonalDataCategory has the range :PersonalDataCategory, therefore, the object of any triple using this property would be inferred as an instance of :PersonalDataCategory. It is an open question for how to refer to a personal data category (class) using this property, as it would infer that class to be an instance as well as a subclass of :PersonalDataCategory. The question is if this is intended and whether it would be semantically correct to specify dpv:hasPersonalDataCategory dpv:EmailAddress .? Other alternative is to scope it within a blank node as: dpv:hasPersonalDataCategory [ a dpv:EmailAddress] ., which this would conflate it with instances of email address e.g., < me@example.com > a dpv:EmailAddress.
The DPV Personal Data Categories ontology is available as an individual module here.
:Accent | :AccountIdentifier | :Acquantaince | :Age | :ApartmentOwned | :Association | :Attitude | :Authenticating | :BankAccount | :Behavioral | :Biometric | :BloodType | :BrowserFingerprint | :BrowsingBehavior | :CallLog | :CarOwned | :Certification | :Character | :Communication | :CommunicationsMetadata | :Connection | :Contact | :Country | :Credit | :Credit | :CreditCapacity | :CreditCardNumber | :CreditRecord | :CreditScore | :CreditStanding | :CreditWorthiness | :Criminal | :CriminalCharge | :CriminalConviction | :CriminalPardon | :DNACode | :Demeanor | :Demographic | :DerivedPersonalData | :DeviceBased | :Dialect | :Disability | :DisciplinaryAction | :Dislike | :Divorce | :DrugTestResult | :EmailAddress | :EmailContent | :EmploymentHistory | :EthnicOrigin | :Ethnicity | :External | :Family | :FamilyHealthHistory | :FamilyStructure | :Favorite | :FavoriteColor | :FavoriteFood | :FavoriteMusic | :Fetish | :Financial | :FinancialAccount | :FinancialAccountNumber | :Fingerprint | :Friend | :GPSCoordinate | :Gender | :GeneralReputation | :Geographic | :GroupMembership | :HairColor | :Health | :HealthHistory | :HealthRecord | :Height | :Historical | :HouseOwned | :IPAddress | :Identifying | :Income | :IncomeBracket | :IndividualHealthHistory | :Intention | :Interaction | :Interest | :Internal | :Job | :KnowledgeBelief | :Language | :LifeHistory | :Like | :LinkClicked | :LoanRecord | :Location | :MACAddress | :MaritalStatus | :Marriage | :MedicalHealth | :MentalHealth | :Name | :OfficialID | :Offspring | :Opinion | :Ownership | :PINCode | :Parent | :Password | :PersonalPossession | :Personality | :PhilosophicalBelief | :PhysicalAddress | :PhysicalCharacteristic | :PhysicalHealth | :PhysicalTrait | :Picture | :Piercing | :PoliticalAffiliation | :Preference | :Prescription | :PrivacyPreference | :Proclivitie | :Professional | :ProfessionalEvaluation | :ProfessionalInterview | :PublicLife | :Purchase | :PurchasesAndSpendingHabit | :Race | :Reference | :Relationship | :Religion | :ReligiousBelief | :Retina | :RoomNumber | :Salary | :Sale | :School | :SecretText | :ServiceConsumptionBehavior | :Sexual | :SexualHistory | :SexualPreference | :Sibling | :SkinTone | :Social | :SocialMediaCommunication | :SocialNetwork | :SocialStatus | :SpecialCategoryPersonalData | :Tattoo | :Tax | :TelephoneNumber | :Thought | :Tracking | :Transaction | :Transactional | :TVViewingBehavior | :UID | :Username | :VoiceCommunicationRecording | :VoiceMail | :Weight | :WorkHistory
dpv:Accent
Description: Information about an individual’s accent.
is SubClass of: dpv:Language
Source: https://enterprivacy.com/wp-content/uploads/2018/09/Categories-of-Personal-Information.pdf
Date Approved: 2019-06-04
Approval Resolution: https://www.w3.org/2019/06/04-dpvcg-minutes.html
Contributor: Elmar Kiesling; Harshvardhan J. Pandit, Fajar J. Ekaputra
dpv:AccountIdentifier
Description: Information about an individual's financial account identifier.
is SubClass of: dpv:FinancialAccount
dpv:Acquantaince
Description: Information about acquaintances in a social network.
is SubClass of: dpv:SocialNetwork
dpv:Age
Description: Information about an individual's age
is SubClass of: dpv:PhysicalCharacteristic
dpv:ApartmentOwned
Description: Information on the apartment(s) owned by an individual.
is SubClass of: dpv:HouseOwned
dpv:Association
Description: Information about associations in a social network with other individuals, groups, or entities, e.g., friend of a friend
dpv:Attitude
Description: Information that relates to an individual's attitude.
is SubClass of: dpv:Behavioral
dpv:Authenticating
Description: Information used to authenticate an individual with something they know
is SubClass of: dpv:Internal
dpv:BankAccount
Description: Information related to an individual's bank account.
dpv:Behavioral
Description: Information that describes an individual’s behavior or activity, on-line or off
is SubClass of: dpv:External
Related Terms: svd:Activity
dpv:Biometric
Description: Biometric information on an individual.
is SubClass of: dpv:Identifying ∩ dpv:SpecialCategoryPersonalData
dpv:BloodType
Description: Information about an individual's blood type.
is SubClass of: dpv:MedicalHealth
dpv:BrowserFingerprint
Description: Information that characterizes the browser used by an individual, which in turn can be used to uniquely identify a user.
is SubClass of: dpv:DeviceBased
dpv:BrowsingBehavior
Description: Information that relates to an individual's browsing behaviour.
Related Terms: svd:OnlineActivity
dpv:CallLog
Description: Information on the calls that an individual has made.
dpv:CarOwned
Description: Information about cars owned by an individual.
is SubClass of: dpv:Ownership
dpv:Certification
Description: Information about professional certifications associated with an individual
is SubClass of: dpv:Professional
dpv:Character
Description: Information about an individual's character in the public sphere
is SubClass of: dpv:PublicLife
dpv:Communication
Description: Information communicated from or to an individual
is SubClass of: dpv:Social
dpv:CommunicationsMetadata
Description: Information about communication metadata in the public sphere
Related Terms: svd:Interactive
dpv:Connection
Description: Information about and including connections of an individual in a social network
dpv:Contact
Description: Information that can be used for contacting an individual, e.g., email address or phone number
is SubClass of: dpv:Tracking
Related Terms: svd:Physical
dpv:Country
Description: Information about an individual’s country, e.g., residence, travel.
is SubClass of: dpv:Location
Notes: ISSUE-24
dpv:Credit
Description: Information about an individual’s reputation with regards to money
is SubClass of: dpv:Financial
is SubClass of: dpv:Transactional
dpv:CreditCapacity
Description: Information relating to an individual's credit capacity.
is SubClass of: dpv:Credit
dpv:CreditCardNumber
Description: Information about an individual's credit card number
is SubClass of: dpv:AccountIdentifier
dpv:CreditRecord
Description: Information relating to an individual's credit record.
dpv:CreditScore
Description: Information relating to an individual's credit score.
is SubClass of: dpv:CreditWorthiness
dpv:CreditStanding
Description: Information relating to an individual's credit standing.
dpv:CreditWorthiness
Description: Information relating to an individual's credit worthiness.
dpv:Criminal
Description: Information about an individual’s criminal activity, e.g., criminal convictions or jail time
Related Terms: svd:Judicial
dpv:CriminalCharge
Description: Information on an individual's criminal charges.
is SubClass of: dpv:Criminal
dpv:CriminalConviction
Description: Information on an individual's criminal convictions.
dpv:CriminalPardon
Description: Information on an individual's criminal pardons.
dpv:DNACode
Description: Information about an individual's DNA.
dpv:Demeanor
Description: Information that relates to an individual's demeanor.
dpv:Demographic
Description: Information that describes an individual’s characteristics shared with others
dpv:DerivedPersonalData
Description: Derived data is data that has not been directly provided by the DataSubject, but has been derived from other collected or externally obtained data.
is SubClass of: dpv:PersonalDataCategory
Date Approved: 2019-05-07
Approval Resolution: https://www.w3.org/2019/05/07-dpvcg-minutes.html
Related Terms: svd:Derived
dpv:DeviceBased
Description: Information about a device that an individual uses for personal use (even part-time or with others)
Related Terms: svd:Computer
dpv:Dialect
Description: Information about an individual’s dialect.
dpv:Disability
Description: Information about an individual's disabilities.
dpv:DisciplinaryAction
Description: Information about disciplinary actions associated with an individual
dpv:Dislike
Description: Information relating to a user's dislikes.
is SubClass of: dpv:Interest
dpv:Divorce
Description: Information about an individual's divorce(s).
is SubClass of: dpv:FamilyStructure
dpv:DrugTestResult
Description: Information about an individual's drug test results.
dpv:EmailAddress
Description: Information about an individual's Email address.
is SubClass of: dpv:Contact
dpv:EmailContent
Description: The contents of Emails that an individual sends or receives.
is SubClass of: dpv:Communication
dpv:EmploymentHistory
Description: Information about an individual's employment history
dpv:EthnicOrigin
Description: Information related to an individual's ethnic origin.
is SubClass of: dpv:Ethnicity ∩ dpv:SpecialCategoryPersonalData
dpv:Ethnicity
Description: Information that describes an individual’s origins and lineage
dpv:External
Description: Personal Data that can be observed by another person i.e. has external characteristics that make it visible
dpv:Family
Description: Information about an individual’s family and relationships
dpv:FamilyHealthHistory
Description: Information related to an individual's family health history.
is SubClass of: dpv:HealthHistory
dpv:FamilyStructure
Description: Information that describes an individual's family structure.
is SubClass of: dpv:Family
dpv:Favorite
Description: Information about an individual's favorites
is SubClass of: dpv:Preference
dpv:FavoriteColor
Description: Information about an individual's favorite color.
is SubClass of: dpv:Favorite
dpv:FavoriteFood
Description: Information about an individual's favorite food.
dpv:FavoriteMusic
Description: Information about an individual's favorite music.
dpv:Fetish
Description: Information an individual's sexual fetishes
is SubClass of: dpv:Sexual
dpv:Financial
Description: Personal data regarding finance or monetary information
Related Terms: svd:Financial
dpv:FinancialAccount
Description: Information that identifies an individual’s financial account
dpv:FinancialAccountNumber
Description: Information about an individual's financial account number
dpv:Fingerprint
Description: Information related to an individual's fingerprint used for biometric purposes.
is SubClass of: dpv:Biometric
dpv:Friend
Description: Information about friends of the individual in a social network. Includes aspects of friendships such as years together or nature of friendship.
dpv:GPSCoordinate
Description: Global position system coordinates of a user's location.
dpv:Gender
Description: Information about an individual's gender
dpv:GeneralReputation
Description: Information about an individual's reputation in the public sphere
dpv:Geographic
Description: Geographic information relating to an individual (e.g., home address)
is SubClass of: dpv:Demographic
dpv:GroupMembership
Description: Information about groups the individual is included or associated with in a social network
dpv:HairColor
Description: Information about an individual's hair colour
dpv:Health
Description: Information about an individual's health.
Related Terms: svd:Health
dpv:HealthHistory
Description: Information about an individual's health history.
dpv:HealthRecord
Description: Information about an individual's health record.
dpv:Height
Description: Information about an individual's physical height
dpv:Historical
Description: Historical personal data is that which is related to or relevant for history or past events in the context of the person or their life.
dpv:HouseOwned
Description: Information about house(s) owned by an individual.
dpv:IPAddress
Description: An Internet protocol (IP) address of a device used by an individual.
dpv:Identifying
Description: Information that uniquely or semi-uniquely identifies a specific individual
dpv:Income
Description: Information about financial income, e.g., for individual or household or family
dpv:IncomeBracket
Description: Information about an individual's income bracket.
dpv:IndividualHealthHistory
Description: Information related to an individual's information health history.
dpv:Intention
Description: Information about an individual's intentions
dpv:Interaction
Description: Information about an individual's interactions in the public sphere
dpv:Interest
Description: Information about an individual's interests
dpv:Internal
Description: Personal data about characteristics of an individual that are internal i.e. cannot be seen or observed
dpv:Job
Description: Information about an individual's professional jobs
dpv:KnowledgeBelief
Description: Information about what a person knows or believes
dpv:Language
Description: Information related to an individual's language.
is SubClass of: dpv:Ethnicity
dpv:LifeHistory
Description: Information about an individual’s personal history (e.g., events that happened in a person’s life, either to them or just around them which might have influenced them (WWII, 9/11)).
is SubClass of: dpv:Historical
dpv:Like
Description: Information relating to a user's likes.
dpv:LinkClicked
Description: Information on the links that an individual has clicked.
Related Terms: svd:Navigation
dpv:LoanRecord
Description: Information about loans provided or related to the individual
dpv:Location
Description: Information about an individual’s location
Related Terms: svd:Location
dpv:MACAddress
Description: A Media Access Control (MAC) address of a device used by an individual.
dpv:MaritalStatus
Description: Information about an individual's marital status and history
dpv:Marriage
Description: Information about an individual's marriage(s).
dpv:MedicalHealth
Description: Information that describes an individual’s health, medical conditions or health care
is SubClass of: dpv:External ∩ dpv:SpecialCategoryPersonalData
dpv:MentalHealth
Description: Information related to an individual's mental health.
is SubClass of: dpv:Health
dpv:Name
Description: A name associated with an individual, e.g., given name, nickname.
is SubClass of: dpv:Identifying
dpv:OfficialID
Description: Information on an official identification document used by an individual.
Related Terms: svd:Government
dpv:Offspring
Description: Information about an individual's offspring(s).
dpv:Opinion
Description: Information about an individual's opinions
dpv:Ownership
Description: Information about things an individual has owned, rented, borrowed, possessed
dpv:PINCode
Description: An individual's Personal identification number (PIN) used in the process of authenticating the individual as a user accessing a system.
is SubClass of: dpv:Authenticating
dpv:Parent
Description: Information about an individual's parent(s).
dpv:Password
Description: An individual's password used in the process of authenticating the individual as a user accessing a system.
dpv:PersonalPossession
Description: Information about an individual's personal possessions.
dpv:Personality
Description: Information that relates to an individual's personality (e.g., categorization in terms of the Big Five personality traits)
dpv:PhilosophicalBelief
Description: Information about an individual’s philosophical beliefs.
is SubClass of: dpv:KnowledgeBelief ∩ dpv:SpecialCategoryPersonalData
dpv:PhysicalAddress
Description: Information about an individual's physical address.
dpv:PhysicalCharacteristic
Description: Information that describes an individual’s physical characteristics
Related Terms: svd:Demographic
dpv:PhysicalHealth
Description: Information related to an individual's physical health.
dpv:PhysicalTrait
Description: Information on defining traits or features about an individuals body.
dpv:Picture
Description: A visual representation or image of an individual, e.g., profile photo.
dpv:Piercing
Description: Information about an individual's piercings
dpv:PoliticalAffiliation
Description: Information about an individual's political affiliation and history
is SubClass of: dpv:PublicLife ∩ dpv:SpecialCategoryPersonalData
Related Terms: svd:Political
dpv:Preference
Description: Information about an individual’s preferences or interests
Related Terms: svd:Preference
dpv:Prescription
Description: Information about prescriptions made for an individual.
dpv:PrivacyPreference
Description: Information about an individual's privacy preferences
dpv:Proclivitie
Description: Information about an individual's proclivities in a sexual context
dpv:Professional
Description: Information about an individual’s educational or professional career
dpv:ProfessionalEvaluation
Description: Information about professional evaluations associated with an individual
dpv:ProfessionalInterview
Description: Information about professional interviews associated with an individual
dpv:PublicLife
Description: Information about an individual’s public life
dpv:Purchase
Description: Information about purchases such as items bought, e.g., grocery or clothing
Related Terms: svd:Purchase
dpv:PurchasesAndSpendingHabit
Description: Information about analysis of purchases made and money spent expressed as a habit, e.g., monthly shopping trends
dpv:Race
Description: Information related to an individual's race.
dpv:Reference
Description: Information about an individual's references in the professional context
dpv:Relationship
Description: Information that characterizes an individual's relationships with other individuals.
dpv:Religion
Description: Information about an individual's religion, religious inclinations, and religious history.
dpv:ReligiousBelief
Description: Information about an individual’s religious beliefs.
dpv:Retina
Description: Information related to an individual's retina used for biometric purposes.
dpv:RoomNumber
Description: Room number of a location associated with an individual.
dpv:Salary
Description: Information about an individual's salary
dpv:Sale
Description: Information about sales, e.g., selling of goods or services
dpv:School
Description: Information about an individual's school such as name of school, conduct, or grades obtained.
dpv:SecretText
Description: An individual's secret text used in the process of authenticating the individual as a user accessing a system, e.g., when recovering a lost password.
dpv:ServiceConsumptionBehavior
Description: Information about the consumption of a service by an individual. Examples: time and duration of consumption.
Contributor: Harshvardhan J. Pandit, Rudy Jacob
dpv:Sexual
Description: Information that describes an individual’s sexual life
dpv:SexualHistory
Description: Information about an individual's sexual history
dpv:SexualPreference
Description: Information about an individual's sexual preferences
dpv:Sibling
Description: Information about an individual's sibling(s).
dpv:SkinTone
Description: Information about an individual's skin tone
dpv:Social
Description: Personal data about the social aspects such as for family, public life, or professional networks.
dpv:SocialMediaCommunication
Description: Information relating to an individual's social media communication, including the communication itself and metadata.
Related Terms: svd:Social
dpv:SocialNetwork
Description: Information about an individual’s friends or connections expressed as a social network
dpv:SocialStatus
Description: Information about an individual's social status
dpv:SpecialCategoryPersonalData
Description: Special category or personal data as per GDPR Art. 9 (1)
Source: https://eur-lex.europa.eu/eli/reg/2016/679/art_9/par_1/oj
Notes: trade union membership, which is explicitly included in the taxative listing in GDPR Art. 9 (1), is not covered yet.
dpv:Tattoo
Description: Information about an individual's tattoos
dpv:Tax
Description: Information about financial tax, e.g., tax records or tax due
dpv:TelephoneNumber
Description: Information about an individual's telephone number.
dpv:Thought
Description: Information about an individual's thoughts
is SubClass of: dpv:KnowledgeBelief
dpv:Tracking
Description: Personal data that can be used to track an individual or used as an identifier, e.g., location or email
dpv:Transaction
Description: Information about financial transactions, e.g., bank transfers
dpv:Transactional
Description: Information about an individual’s purchasing, spending or income
dpv:TVViewingBehavior
Description: Information that relates to an individual's TV viewing behavior, such as timestamps of channel change, duration of viewership, content consumed.
is SubClass of: dpv:ServiceConsumptionBehavior
dpv:UID
Description: An unique identifier used to identify an individual.
Related Terms: svd:UniqueId
dpv:Username
Description: A username used to identify an individual.
dpv:VoiceCommunicationRecording
Description: Recording of an individual's recorded communication, (e.g., telephony, VoIP)
Contributor: Elmar Kiesling; Harshvardhan J. Pandit, Fajar J. Ekaputra, Axel Polleres
Notes: ISSUE-23
dpv:VoiceMail
Description: Information about an individual's voice mail messages.
dpv:Weight
Description: Information about an individual's physical weight
dpv:WorkHistory
Description: Information about an individual's work history in a professional context
DPVCG at present defines a hierarchically organized set of generic categories of data handling purposes. Regulations such as GDPR generally require a specific purpose to be declared in an understandable manner. We therefore suggest to declare the specific context as an instance of one or several dpv:Purpose categories and to always declare the specific purpose with a human readable description (e.g., by using rdfs:label and rdfs:comment). E.g.
Example 1: Creating Purposes with human-readable descriptions
:NewPurpose rdfs:subClassOf dpv:DeliveryOfGoods, dpv:FraudPreventionAndDetection ;
rdfs:label “New Purpose” ;
rdfs:comment "Intended delivery of goods with fraud prevention” .
Purposes can be further restricted to specific contexts using the class dpv:Context and the property dpv:hasContext. DPVCG provides a way to restrict purposes to a specific business sector using the class dpv:Sector and the property dpv:hasSector. Hierarchies for defining business sectors include [ NACE ] (EU), [ NAICS ] (US), [ ISIC ] (UN), and [ GICS ]. Multiple classifications can be used through mappings between sector codes such as [ NACE-NAICS ]. At the moment, we recommend to specify this sector in terms of the EU NACE codes, where the codes can be specified using the URI scheme dpv-nace: NACE-CODE.
We provide an interpretation of the NACE revision 2 codes which uses rdfs:subClassOf to specify the hierarchy, available here.
Example 2: Using NACE codes to restrict Purposes
For example, a purpose can be restricted to the domain of scientific research using its corresponding NACE code M72, which can be represented as:
:SomePurpose a dpv:Purpose ;
rdfs:label “Some Purpose” ;
dpv:hasSector dpv-nace:M72 .
We suggest selecting the most appropriate or applicable purpose over more abstract ones by selecting or extending the relevant classes in the purpose taxonomy. For example, the purpose Optimisation can be further clarified to be optimisation for the consumer, or the controller.
The DPV Purposes ontology is available as an individual module here.
:AcademicResearch | :AccessControl | :Beneficiary | :CommercialInterest | :CommercialResearch | :Context | :CreateEventRecommendations | :CreatePersonalizedRecommendations | :CreateProductRecommendations | :CustomerCare | :DeliveryOfGoods | :FraudPreventionAndDetection | :IdentityVerification | :ImproveExistingProductsAndServices | :ImproveInternalCRMProcesses | :IncreaseServiceRobustness | :InternalResourceOptimisation | :NonCommercialResearch | :OptimisationForConsumer | :OptimisationForController | :OptimiseUserInterface | :PersonalisedBenefits | :ResearchAndDevelopment | :Sector | :Security | :SellDataToThirdParties | :SellInsightsFromData | :SellProductsToDataSubject | :SellTargettedAdvertisements | :ServiceOptimization | :ServicePersonalization | :ServiceProvision | :UserInterfacePersonalisation
dpv:AcademicResearch
Description: Research conducted in an academic context, e.g., within universities
is SubClass of: dpv:ResearchAndDevelopment
Source: https://www.w3.org/community/dpvcg/wiki/Purposes_for_handling_Personal_Data#High-level_categories_.28to-be-discussed.29
Date Created: 2018-12-10
Contributor: Harshvardhan J. Pandit, Javier Fernandez, Axel Polleres, Elmar Kiesling, Fajar Ekaputra, Simon Steyskal
Related Terms: svpu:Education
dpv:AccessControl
Description: To conduct or enforce access control
is SubClass of: dpv:Security
Related Terms: svpu:Login
dpv:Beneficiary
Description: self.DataSubject, self.DataController, society ? ( --- under consideration --- )
in Range of: dpv:hasBeneficiary
Notes: This needs further details, the group is asking feedback about whether Beneficiaries of a specific purposes hould be specified separately or not
dpv:CommercialInterest
Description: For purposes of commercial activities i.e. of profit or benefit to the Controller
is SubClass of: dpv:Purpose
dpv:CommercialResearch
Description: Research conducted in a commercial setting, e.g., in a company
Related Terms: svpu:Develop
dpv:Context
Description: Used to scope the purpose, e.g., restriction to a certain business sector
in Domain of: dpv:hasBeneficiary, dpv:hasSector
in Range of: dpv:hasContext
dpv:CreateEventRecommendations
Description: Create and provide personalised recommendations for events to the individual.
is SubClass of: dpv:CreatePersonalizedRecommendations
dpv:CreatePersonalizedRecommendations
Description: Create and provide personalised recommendations to the individual.
is SubClass of: dpv:ServicePersonalization
dpv:CreateProductRecommendations
Description: To create product recommendations, e.g., suggest similar products
Related Terms: svpu:Marketing
dpv:CustomerCare
Description: Processes related to providing assistance for customer satisfaction
is SubClass of: dpv:ServiceProvision
Related Terms: svpu:Feedback
dpv:DeliveryOfGoods
Description: To deliver goods and services
Related Terms: svpu:Delivery
dpv:FraudPreventionAndDetection
Description: To detect and prevent fraud
Related Terms: svpu:Government
dpv:IdentityVerification
Description: To verify and authorise identity
dpv:ImproveExistingProductsAndServices
Description: To improve existing products and services
is SubClass of: dpv:OptimisationForController
dpv:ImproveInternalCRMProcesses
Description: To improve customer-relationship management (CRM) processes
dpv:IncreaseServiceRobustness
Description: To improve the robustness and resilience of services
dpv:InternalResourceOptimisation
Description: Optimisation of internal resources used by the organisation, e.g., resource usage
dpv:NonCommercialResearch
Description: Research conducted in a non-commercial setting, e.g., for a non-profit-organisation (NGO)
dpv:OptimisationForConsumer
Description: Optimisation of activities and services for the consumer or user
is SubClass of: dpv:ServiceOptimization
Related Terms: svpu:Custom
dpv:OptimisationForController
Description: Optimisation of activities and services for the Controller
dpv:OptimiseUserInterface
Description: Optimisation of interfaces presented to the user
is SubClass of: dpv:OptimisationForConsumer
dpv:PersonalisedBenefits
Description: Personalisation of benefits received by the user
dpv:ResearchAndDevelopment
Description: Performing research and developing new methods,products, or services
dpv:Sector
Description: Used to indicate the sector of a purpose, e.g., Agriculture, Advertising (specified e.g., in the form of NACE codes)
in Range of: dpv:hasSector
dpv:Security
Description: Security of data
dpv:SellDataToThirdParties
Description: To sell data or information to third parties
is SubClass of: dpv:CommercialInterest
dpv:SellInsightsFromData
Description: To sell or commercially provide insights obtained from analysis of data
dpv:SellProductsToDataSubject
Description: To sell products or services to the data subject or user
dpv:SellTargettedAdvertisements
Description: To sell or provide targetted advertisements about the user to Third Parties
dpv:ServiceOptimization
Description: Optimization of service or activity
dpv:ServicePersonalization
Description: Personalization of service or activity for the user
dpv:ServiceProvision
Description: Provision of service or activity
dpv:UserInterfacePersonalisation
Description: Personalisation of interfaces presented to the user
:hasBeneficiary | :hasContext | :hasSector
dpv:hasBeneficiary
Description: Cui bono? Who is the ultimate beneficiary of this purpose, here a stakeholder can be declared, e.g., the DataSubjects themselves or the Data Controller. ( --- under consideration --- )
Domain: dpv:Context
Range: dpv:Beneficiary
Notes: If we want ot be able to say something about the beneficiary of a purpose, we probably also need to say something about how the beneficiary benefits? - whether it is good for the controller or data subject
dpv:hasContext
Description: Restricts a purpose to the specified context(s)
Domain: dpv:Purpose
Range: dpv:Context
dpv:hasSector
Description: Indicates the purpose is associated with activities in the indicated (Economic) Sector(s)
Range: dpv:Sector
DPV provides a hierarchy of classes to specify the operations associated with the processing of personal data. Declaring the processing or processing categories associated with personal data is required by regulations such as the GDPR. Common processing operations such as collect, share, and use have certain constraints or obligations in GDPR, which makes it necessary to accurately represent them for personal data handling. While the term ‘use’ is liberally used to refer to a broad range of processing categories in privacy notices, we suggest to select and use appropriate terms to accurately reflect the nature of processing where applicable.
We define top-level classes to represent the following broad categories of processing - Disclose, Copy, Obtain, Remove, Store, Transfer, and Transform. Each of these are then further expanded using subclasses in the taxonomy, which includes terms defined in the definition of processing in GDPR (Article 4-2).
The DPV taxonomy provides properties with a boolean range to indicate the nature of processing regarding Systematic Monitoring, Evaluation or Scoring, Automated Decision Making, Matching or Combining, Large Scale processing, and Innovative use of new solutions - which are relevant towards interpretation of legal requirements such as GDPR compliance.
The DPV Processing ontology is available as an individual module here.
:Acquire | :Adapt | :Align | :Alter | :Analyse | :Anonymise | :Collect | :Combine | :Consult | :Copy | :Derive | :Destruct | :Disclose | :DiscloseByTransmission | :Disseminate | :Erase | :MakeAvailable | :Move | :Obtain | :Organise | :Profiling | :PseudoAnonymise | :Record | :Remove | :Restrict | :Retrieve | :Share | :Store | :Structure | :Transfer | :Transform | :Transmit | :Use
dpv:Acquire
Description: to come into possession or control of the data
is SubClass of: dpv:Obtain
dpv:Adapt
Description: to modify the data, often rewritten into a new form for a new use
is SubClass of: dpv:Transform
Source: https://eur-lex.europa.eu/eli/reg/2016/679/art_4/par_2/oj
dpv:Align
Description: to adjust the data to be in relation to another data
dpv:Alter
Description: to change the data withouth changing it into something else
dpv:Analyse
Description: to study or examine the data in detail
is SubClass of: dpv:Use
Source: https://www.specialprivacy.eu/vocabs/processing
Related Terms: svpr:Analyse
dpv:Anonymise
Description: to irreversibly alter personal data in such a way that a unique data subject can no longer be identified directly or indirectly or in combination with other data
Related Terms: svpr:Anonymize
dpv:Collect
Description: to gather data from someone
Source: https://eur-lex.europa.eu/eli/reg/2016/679/art_4/par_2/oj, https://www.specialprivacy.eu/vocabs/processing
Related Terms: svpr:Collect
dpv:Combine
Description: to join or merge data
Related Terms: svpr:Aggregate
dpv:Consult
Description: to consult or query data
Related Terms: svpr:Query
dpv:Copy
Description: to produce an exact reprodution of the data
is SubClass of: dpv:Processing
Related Terms: svpr:Copy
dpv:Derive
Description: to create new derivative data from the original data
Related Terms: svpr:Derive
dpv:Destruct
Description: to process data in a way it no longer exists or cannot be repaired
is SubClass of: dpv:Remove
dpv:Disclose
Description: to make data known
dpv:DiscloseByTransmission
Description: to disclose data by means of transmission
is SubClass of: dpv:Disclose
dpv:Disseminate
Description: to spread data throughout
dpv:Erase
Description: to delete data
dpv:MakeAvailable
Description: to transform or publish data to be used
dpv:Move
Description: to move data from one location to another including deleting the original copy
is SubClass of: dpv:Transfer
Related Terms: svpr:Move
dpv:Obtain
Description: to solicit or gather data from someone
dpv:Organise
Description: to organize data for arranging or classifying
is SubClass of: dpv:Organise
dpv:Profiling
Description: to create a profile that describes or represents a person
dpv:PseudoAnonymise
Description: to replace personal identifiable information by artificial identifiers
dpv:Record
Description: to make a record (especially media)
dpv:Remove
Description: to destruct or erase data
dpv:Restrict
Description: to apply a restriction on the processsing of specific records
dpv:Retrieve
Description: to retrieve data, often in an automated manner
dpv:Share
Description: to give data (or a portion of it) to others
dpv:Store
Description: to keep data for future use
dpv:Structure
Description: to arrange data according to a structure
dpv:Transfer
Description: to move data from one place to another
Related Terms: svpr:Transfer
dpv:Transform
Description: to change the form or nature of data
dpv:Transmit
Description: to send out data
dpv:Use
Description: to use data
:innovativeUseOfNewSolutions | :isAutomatedDecisionMaking | :isEvaluationScoring | :isLargeScale | :isMatchingCombining | :isSystematicMonitoring
dpv:innovativeUseOfNewSolutions
Description: Indicates the processing comprises of innovative uses of new or radical solutions
Comments: e.g., combining fingerprint & face scan for access control. What is concidered new/innovative is of course subject to change over time.
Domain: dpv:Processing
dpv:isAutomatedDecisionMaking
Description: Indicates whether the processing comprises of or is part of or results in automated decision making
dpv:isEvaluationScoring
Description: Indicates whether the processing ir part of or results in evaluation or scoring of an individual or their personal data
Comments: including profiling and predicting,
dpv:isLargeScale
Description: Indicates the processing is carried out at large scale in terms of size of data or individuals associated
Comments: Involves large amounts of personal data or data subjects. The WP29 recommends that the following factors, in particular, be considered when determining whether the processing is carried out on a large scale (WP29 Guidelines on Data Protection Officer 16/EN WP 243): a. the number of data subjects concerned, either as a specific number or as a proportion of the relevant population; b. the volume of data and/or the range of different data items being processed; c. the duration, or permanence, of the data processing activity; d. the geographical extent of the processing activity.
dpv:isMatchingCombining
Description: Indicates whether the processing comprises of matching or combining existing data
Comments: originating from two or more data processing operations performed for different purposes and/or by different data controllers in a way that would exceed the reasonable expectations of the data subject (WP29 Opinion on Purpose limitation 13/EN WP 203, p.24). For instance Integration/Enrichment with other data (not necessarily personal only)
dpv:isSystematicMonitoring
Description: Indicates whether the processing comprises of systematic monitoring of data subjects or their personal data
Regulations require certain technical and organisational measures to be in place depending on the context of processing involving personal data. For example, GDPR (Article 32) states implementing appropriate measures by taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing, as well as risks, rights and freedoms. Examples of measures stated in the article states include:
To address these requirements, the DPVCG defines a hierarchical vocabulary for declaring technical and organisational measures. For any of the declared measures defined below, we provide a generic ObjectProperty (dpv:measureImplementedBy), and for the values of this attribute, we either allow a blank node with a single rdfs:comment to describe the measure, or a URI to a standard or best practice followed, i.e. a well-known identifier for that standard or a URL where the respective document describes the standard. The class StorageRestriction represents the measures used for storage of data with two specific properties provided for storage location and duration restrictions.
In the future, we plan to provide a collection of URIs for identifying recommended standards and best practices. Future versions of this document may extend the vocabulary by an approved taxonomy of identifiers for such standards and best practices.
The DPV Technical and Organisational Measures ontology is available as an individual module here.
:AccessControlMethod | :Anonymization | :AuthenticationProtocols | :AuthorisationProcedure | :Certification | :CertificationSeal | :CodeOfConduct | :Contract | :DeIdentification | :DesignStandard | :EncryptionInRest | :EncryptionInTransfer | :GuidelinesPrinciple | :LegalAgreement | :NDA | :OrganisationalMeasure | :PrivacyByDefault | :PrivacyByDesign | :PseudoAnonymization | :PseudonymisationEncryption | :RegularityOfRecertification | :RiskManagementProcedure | :Seal | :StaffTraining | :StorageDeletion | :StorageDuration | :StorageLocation | :StorageRestoration | :StorageRestriction | :TechnicalMeasure
dpv:AccessControlMethod
Description: methods which restrict access to a place or resource
is SubClass of: dpv:TechnicalMeasure
Contributor: Axel Polleres, Rob Brennan, Harshvardhan J. Pandit, Mark Lizar
dpv:Anonymization
Description: process by which personal data is irreversibly altered in such a way that a data subject can no longer be identified directly or indirectly, either by the data controller alone or in collaboration with any other party
is SubClass of: dpv:PseudoAnonymization
Source: ISO 25237
dpv:AuthenticationProtocols
Description: protocols involving validation of identity i.e. authentication of a person or information
dpv:AuthorisationProcedure
Description: Specifies procedures for determining permission or authority
is SubClass of: dpv:OrganisationalMeasure
Notes: non-technical authorisation procedures: How is it described on an organisational level, who gets access to the data
Description: certification mechanisms, seals, and marks for the purpose of demonstrating compliance
is SubClass of: dpv:CertificationSeal
dpv:CertificationSeal
Description: Category of certifications, seals, and marks indicating compliance to regulations or practices
dpv:CodeOfConduct
Description: A set of rules or procedures outlining the norms and practices for conducting activities
is SubClass of: dpv:GuidelinesPrinciple
dpv:Contract
Description: Contractual terms governing data handling within the data controller
is SubClass of: dpv:LegalAgreement
dpv:DeIdentification
Description: Process by identifiable personal data (PII) is converted to un-identifiable personal data
dpv:DesignStandard
Description: A set of rules or guidelines outlining criterias for design
dpv:EncryptionInRest
Description: Encryption of data when being stored (persistent encryption)
is SubClass of: dpv:PseudonymisationEncryption
dpv:EncryptionInTransfer
Description: Encryption of data in transit, e.g., when being transferred from one location to another, including sharing
dpv:GuidelinesPrinciple
Description: Guidelines or Principles regarding processing and operational measures
dpv:LegalAgreement
Description: A legally binding agreement
dpv:NDA
Description: Non-disclosure Agreements e.g., preserving confidentiality of information
dpv:OrganisationalMeasure
Description: Organisational measures required/followed when processing data of the declared category
is SubClass of: dpv:TechnicalOrganisationalMeasure
dpv:PrivacyByDefault
Description: Practices regarding selecting appropriate data protection and privacy measures as the 'default' in an activity or service
dpv:PrivacyByDesign
Description: Practices regarding incorporating data protection and privacy in the design of information and services
is SubClass of: dpv:RiskManagementProcedure
dpv:PseudoAnonymization
Description: PseudoAnonmyization or 'pseudonymisation’ means the processing of personal data in such a manner that the personal data can no longer be attributed to a specific data subject without the use of additional information, provided that such additional information is kept separately and is subject to technical and organisational measures to ensure that the personal data are not attributed to an identified or identifiable natural person;
Source: https://eur-lex.europa.eu/eli/reg/2016/679/art_4/par_5/pnt_g/oj
dpv:PseudonymisationEncryption
Description: Category of technical measures consisting of pseudoanonymization and encryption
dpv:RegularityOfRecertification
Description: Specifies policy regarding repetition or renewal of existing certification(s)
dpv:RiskManagementProcedure
Description: Risk management refers to a coordinated set of activities and methods that is used to direct an organization and to control the many risks that can affect its ability to achieve objectives. The term risk management also refers to the programme that is used to manage risk. This programme includes risk management principles, a risk management framework, and a risk management process.
Comments: Data Protection Impact Assessments as per GDPR art 35, other Privacy Impact Assessments, threat severity assessment https://www.cnil.fr/en/privacy-impact-assessment-pia
Source: ISO 31000
dpv:Seal
Description: a seal or a mark indicating proof of certification to some certification or standard
dpv:StaffTraining
Description: Practices and policies regarding training of staff members
dpv:StorageDeletion
Description: Defines how secure deletion is guaranteed
is SubClass of: dpv:StorageRestriction
dpv:StorageDuration
Description: A duration or temporal entity denoting limitation on storage of personal data
in Range of: dpv:duration
dpv:StorageLocation
Description: Defines a location or goespatial scope, where the data is (physically) stored
in Range of: dpv:location
dpv:StorageRestoration
Description: Regularity and temporal span of data restoration/backup mechanisms that guarantee that data is preserved
dpv:StorageRestriction
Description: Restrictions required or followed regarding storage of data
in Domain of: dpv:duration, dpv:location
in Range of: dpv:storage
dpv:TechnicalMeasure
Description: Technical measures required/followed when processing data of the declared category
:duration | :location | :measureImplementedBy | :storage
dpv:duration
Description: Specifies duration for storage of personal data
Domain: dpv:StorageRestriction
Range: dpv:StorageDuration
Description: Specifies location for storage of personal data
Range: dpv:StorageLocation
dpv:measureImplementedBy
Description: a generic ObjectProperty to describe how the measure is implemented. For the values of this property we either allow a blank node with a single rdfs:comment to describe the measure, or a URI to a standard or best practice followed, i.e. a well-known identifier for that standard or a URL where the respective document describes the standard.
Domain: dpv:TechnicalOrganisationalMeasure
Contributor: Axel Polleres
dpv:storage
Description: Specifies restriction on the storage of personal data
Range: dpv:StorageRestriction
Consent is one of the legal bases for the processing of personal data which has several requirements and obligations that determine its validity and use as a legal basis. DPVCG provides the necessary terms and relationships to describe consent and its attributes from a compliance perspective. While the focus of the taxonomy is on the use of consent as a legal basis within the GDPR, the vocabulary can be adapted or extended to define other forms of consent.
The DPVCG consent vocabulary uses the set of properties from the base vocabulary to associate instances of dpv:Consent with Personal Data Categories, Purposes, Processing, Data Controllers, Recipients, Technical and Organisational Measures, and Data Subject. Additionally, the vocabulary also specifies properties for provision (how consent was given) and withdrawal (how consent was withdrawn) to define the provenance of consent. The expiry of consent can be specified using the property dpv:expiry, with sub-properties provided to define expiry as a temporal entity using dpv:expiryTime or as a condition/event using dpv:expiryCondition.
Certain requirements for valid consent require some information to be presented before the consent is obtained in order for it to be considered an ‘informed consent’. This information and the notice it was provided in can be specified using the property dpv:consentNotice. Additionally, the property dpv:isExplicit can be used to specify if the consent is to be interpreted as ‘explicit consent’ using a boolean value (true/false).
To specify consent provided by delegation, such as in the case of a parent or guardian providing consent for a child, the properties dpv:provisionByJustification and dpv:withdrawalByJustification can be used to capture the nature of such ‘delegation’, with the fields dpv:provisionBy and dpv:withdrawalBy capturing the legal entity who provided the consent. By default, the consent is assumed to have been provided by the associated Data Subject.
The DPV Consent ontology is available as an individual module here.
As the Legal Bases are dependant on legal jurisdictions, and consent is one of the legal basis under GDPR, we provide the GDPR legal bases (based on Article 6 and Article 9) under a separate aligned vocabulary here.
:Consent | :LegalEntity
dpv:Consent
Description: Consent as defined by Article 4(11) of the GDPR
in Domain of: dpv:consentNotice, dpv:expiry, dpv:expiryCondition, dpv:expiryTime, dpv:isExplicit, dpv:provisionBy, dpv:provisionByJustification, dpv:provisionMethod, dpv:provisionTime, dpv:withdrawalBy, dpv:withdrawalByJustification, dpv:withdrawalMethod, dpv:withdrawalTime
Source: https://eur-lex.europa.eu/eli/reg/2016/679/art_4/par_11/oj
Contributor: Harshvardhan J. Pandit, Mark Lizar, Bud Bruegger
dpv:LegalEntity
Description: A Person or Organisation, including Data Subjects, that constitute as a legal entity.
is Parent Class of: dpv:DataSubject
in Range of: dpv:provisionBy, dpv:withdrawalBy
Related Terms: rdfs:subClassOf prov:Agent
:consentNotice | :expiry | :expiryCondition | :expiryTime | :isExplicit | :provisionBy | :provisionByJustification | :provisionMethod | :provisionTime | :withdrawalBy | :withdrawalByJustification | :withdrawalMethod | :withdrawalTime
dpv:consentNotice
Description: Links consent to the notice displayed for requesting consent
Comments: The actual notice that the Data Subject received to consent to, either a text or link to a document, which should be usable to decide whether the form or consent was compliant to legislation, e.g., documenting how the user has been informed about rights and implications (such as, right to data portability,right to rectify, right to erasure, right to restrict processing, right to object, rights regarding automated decision making or profiling, processors, third parties, sub-processors, outside-EEA transfers, automated decision-making, or other necessary details of the privacy-policy). Can be TextOrDocumentOrURI.
Domain: dpv:Consent
dpv:expiry
Description: Generic property specifying when or under which condition(s) the consent will expire
dpv:expiryCondition
Description: Specifies the condition or event that determines the expiry of consent
Comments: Can be TextOrDocumentOrURI
is Sub-Property of: dpv:expiry
dpv:expiryTime
Description: Specifies the expiry time or duration for consent
dpv:isExplicit
Description: Indicates consent is explicit as explained in GDPR Article 9.2a and Article 22.2c
dpv:provisionBy
Description: Specifies the entity that provisioned or provided consent
Comments: Normally this would be the dataSubject, but in some exceptional cases, the consent might be given on behalf by someone else, e.g., parents of minors.
Range: dpv:LegalEntity
dpv:provisionByJustification
Description: Specifies the justification for entity providing consent
Comments: This field can be used to provide a justification why the provision was provided by another DataSubject or legal entity, e.g., declaring the relationship (parent, guardian), in combination with the field provisionBy
dpv:provisionMethod
Description: Specifies the method by which consent was provisioned or provided
Comments: Can be used to record information of how consent was provided e.g., by a click to a form, in writing, etc., by logging into a system and confirm per email, or with some additional authentication, etc.
dpv:provisionTime
Description: Specifies the instant in time when consent was given
dpv:withdrawalBy
Description: Specifies the entity that withdrew consent
Comments: Normally this would be the dataSubject, but in some exceptional cases, the consent might be withdrawn on behalf by someone else, e.g., parents of minors.
dpv:withdrawalByJustification
Description: Specifies the justification for entity withdrawing consent
Comments: This field can be used to provide a justification why the withdrawal was done by another DataSubject or legal entity, e.g., declaring the relationship (parent, guardian), in combination with the field withdrawalBy
dpv:withdrawalMethod
Description: Specifies the method by which consent can be/has been withdrawn
Comments: Can be used to record information of how to withdraw consent, e.g., by a click to a form, in writing, etc., by logging into a system and confirm per email, or with some additional authentication, etc.
dpv:withdrawalTime
Description: Specifies the instant in time when consent was withdrawn
Defining recipients is important in the context of data privacy as it allows tracking the entities personal data is shared/transferred with. Similarly, a categorisation of Data Controllers and Data Subjects has bearing on the privacy of personal data handling, especially when considering situations such as where Data Subjects are children. The vocabulary currently provides a few top-level classes to describe such recipients and Data Subjects, with an invitation to suggest/provide more terms for future releases.
The DPV Recipients, Data Controllers, and Data Subjects ontology is available as an individual module here.
:Child | :DataProcessor | :ThirdParty
dpv:Child
Description: A 'child' is a natural legal person who is below a certain legal age depending on the legal jurisdiction.
Comments: A 'child' is distinct from a 'minor'. For example, the legal age for a 'minor' in most countries is 18, whereas a 'child' can be a minor below the age of 14.
is SubClass of: dpv:DataSubject
Contributor: Harshvardhan J. Pandit
dpv:DataProcessor
Description: ‘processor’ means a natural or legal person, public authority, agency or other body which processes personal data on behalf of the controller;
is SubClass of: dpv:Recipient
Source: https://eur-lex.europa.eu/eli/reg/2016/679/art_4/par_8/pnt_g/oj
dpv:ThirdParty
Description: ‘third party’ means a natural or legal person, public authority, agency or body other than the data subject, controller, processor and persons who, under the direct authority of the controller or processor, are authorised to process personal data;
Source: https://eur-lex.europa.eu/eli/reg/2016/679/art_4/par_10/pnt_g/oj
Do we need to formulate a notion of compliance in scope of the cg?
Do we want to revisit a definition of "gdpr rights" in our definitions and taxonomies?
Should our taxonomy include a distinction/modeling of data subjects to whom gdpr applies (eu citizens and/or locatedin eu)
We may want to add a non-normative comment in the spec that/how the taxonomy can be used as skos.
Do we need a generic mechanism to describe conditions, constraints and restrcitions to a specific processing or data category or can we re-use odrl's mechanism?
How to express sensitivity of data?
Ask for specific feedback on (un)ambiguity of the term descriptions
Describe use-cases and examples showing how the vocabulary should be or can be used
Personal data cateories collected might be collected in an approximate manner (e.g., age vs. age range), should we provide a mechanism in the vocabulary to distinguish this?
Should we add more subclasses to communicationrecording (e.g., distinguishing chats, personalmessaging, videocommunication, telephony, etc.) and which ones?
Should we add more specific subclasses like countryofcitizenship, countryofresidence, countryofcurrentlocation to country and which ones?
Are there mappings to gics from other coding systems naics/nace/isic ...
Where are categories of data controllers used, where are they useful? (cf. recital 98, 99, 100)
We ask for particular feedback on whether and how to extend the list/taxonomy of controllers and recipients in the current vocabulary.
Should we explicitly note that the the controller is always a recipient of the data, if not, do we need to make this explicit inth vocabulary, by declaring it?
Global Industry Classification Standard (GICS) . URL: https://www.msci.com/gics
International Standard Industrial Classification of All Economic Activities (ISIC) . URL: https://unstats.un.org/unsd/classifications
Statistical Classification of Economic Activities in the European Community (NACE) . URL: https://ec.europa.eu/eurostat/ramon/nomenclatures/index.cfm?TargetUrl=LST_NOM_DTL&StrNom=NACE_REV2
[NACE-NAICS]
NACE to NAICS mapping . URL: https://ec.europa.eu/eurostat/ramon/nomenclatures/index.cfm?TargetUrl=LST_NOM_DTL&StrNom=NACE_REV2
North American Industry Classification System (NAICS) . URL: https://www.census.gov/eos/www/naics/