dpv

DPVCG

Data Privacy Vocabularies and Controls Community Group (DPVCG) repository

Community Group (W3C) wiki

The mission of the W3C Data Privacy Vocabularies and Controls CG (DPVCG) is to develop a taxonomy of privacy and data protection related terms, which include in particular terms from the new European General Data Protection Regulation (GDPR), such as a taxonomy of personal data as well as a classification of purposes (i.e., purposes for data collection), and events of disclosures, consent, and processing such personal data.

Newcomers to the DPV are recommended to start with the Primer to familiarise themselves with the concepts, semantics, and usefulness of the DPV.

License: All work produced by DPVCG and provided through this repo or elsewhere is provided by contributors under the W3C Document License. A copy of the license is provided in the LICENSE.md file.

DPV Family of Documents

Core documents:

Note: Newcomers to the DPV are strongly recommended to first read through the Primer to familiarise themselves with the semantics and concepts of DPV.

Serialisations of DPV:

Extensions to Concepts:

Other Resources:

Guidelines on Use:

Related Links

Data Privacy Vocabulary (DPV)

The Data Privacy Vocabulary 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:

The namespace for DPV terms is http://www.w3id.org/dpv# with suggested prefix dpv. The IRI for DPV is currently redirected to serve the files hosted in this repository from GitHub pages i.e. https://w3c.github.io/dpv/dpv/ (thanks to @bert-github for setting this up). Content-negotiation should therefore be supported for all files/serialisations of the DPV and its modules.

DPV and Modules

The term ‘DPV’ represents the entire vocabulary - with its concepts and terms as defined in the specification. Serialisations for this in rdf+xml, json-ld, and turtle are provided. The ‘modules’ in DPV are separate files for each of the hierarchies and concept taxonomies - for example ‘purposes’. These are defined in the rdf folder with serialisations for each module. The core or base vocabulary or ontology is defined containing the top-level classes and data model (i.e. PersonalDataHandling).

Contribution / Participation

The DPVCG is the primary forum for contributions and participations regarding the DPV. As such, all decisions and resolutions will be conducted through the group’s meetings and call. Membership in DPVCG is not necessary to contribute to DPV, but is recommended for participating in the group’s decision making process. Contributions and questions can be sent to the group’s public mailing list or expressed as GitHub issues.

Suggesting new terms

To suggest a new term, we request following information:

Raising issues

Before submitting an issue, please see the whether the issue has been addressed on GitHub. If not, please raise the issue via the group’s public mailing list or expressed as GitHub issues.

Fixes, corrections to the terms are considered as issues and can be submitted similarly. For minor changes, we may prefer to incorporate them directly rather than through pull requests and patches. For larger issues, please check with the group before submitting a pull-request to ensure its appropriate and efficient incorporation.

Development Guide

please refrain from making changes by-hand or manually

The development and maintainence of DPV takes place primarily through a shared spreadsheet. The terms and their annotated metadata are declared in the spreadsheet, and used as input to generate the RDF files and HTML documentation through the documentation-generator tooling. The documentation tool is a collection of Python scripts to assist in the automation of downloading the spreadsheet as CSV files, generating RDF files, validating them for correctness, and producing the HTML documentation.

Therefore, whenever adding a new term or changing existing ones, the following steps are recommended to update the DPV vocabulary and documentation:

  1. Make changes appropriately in the shared spreadsheet. The links to this are available to the DPVCG members. For others, please see the CSV files in documentation_generator/vocab_csv. Ideally, create an GitHub issue for discussions and follow ups.
  2. Use the documentation-generator tooling to download the spreadsheet, generate RDF, test it, generate HTML output.
  3. Manually inspect whether the changes have been made. Tools, scripts, and software in general can propogate errors silently.
  4. The variables and parameters in documentation-generator tooling can be used to define the path where files are exported to can be set to the dpv repository to make changes in this directory. For e.g. EXPORT_DPV_HTML_PATH = ~/code/dpvcg/dpv will generate the HTML documentation in the dpv directory.
  5. Submit a pull-request for merging with the repository.

Getting help and assistance

If you’re unsure about something, or would like clarifications, or suggestions - please drop us a line or open an issue. We would be happy to help.