Copyright © 2024 the Contributors to the DPV Use-Cases and Requirements 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.
This document lists the use-cases and requirements that motivate the development and provision of resources within the W3C Data Privacy Vocabularies and Controls Community Group (DPVCG). Specifically, it lists the background information that feeds into the continued development of the Data Privacy Vocabulary (DPV) Specification and its associated resources. It draws inspiration (and methodology) from SHACL Use Cases and Requirements. The vocabulary, and instances of use-cases and requirements are available in DPVCG GitHub repo under ./use-cases path.
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.
The DPVCG is currently updating the specifications to v2. This document is a draft and may change as part of this process.
Contributing: The DPVCG welcomes participation to improve the DPV and associated resources, including expansion or refinement of concepts, requesting information and applications, and addressing open issues. See contributing page for further information.
GitHub Issues are preferred for discussion of this specification.
Data Privacy Vocabulary (DPV) Specification: is the base/core specification for the 'Data Privacy Vocabulary', which is extended for Personal Data [PD], Locations [LOC], Risk Management [RISK], Technology [TECH], and [AI]. Specific [LEGAL] extensions are also provided which model jurisdiction specific regulations and concepts - see the complete list of extensions. To support understanding and applications of [DPV], various guides and resources [GUIDES] are provided, including a [PRIMER].
[DPV] and related resources are published on GitHub. For a general overview of the Data Protection Vocabularies and Controls Community Group [DPVCG], its history, deliverables, and activities - refer to DPVCG Website. For meetings, see the DPVCG calendar.
The peer-reviewed article “Creating A Vocabulary for Data Privacy” presents a historical overview of the DPVCG, and describes the methodology and structure of the DPV along with describing its creation. An open-access version can be accessed here, here, and here. The article preprint Data Privacy Vocabulary (DPV) - Version 2 describes the changes made in DPV v2.
The namespaces used in this document are as follows:
: | <<https://w3id.org/dpv/use-cases/vocab#> |
dpv: | <https://w3id.org/dpv#> |
dct: | <http://purl.org/dc/terms/> |
rdfs: | <http://www.w3.org/2000/01/rdf-schema#> |
skos: | <http://www.w3.org/2004/02/skos/core#> |
owl: | <http://www.w3.org/2002/07/owl#> |
vann: | <http://purl.org/vocab/vann/> |
xsd: | <http://www.w3.org/2001/XMLSchema#> |
sh: | <http://www.w3.org/ns/shacl#> |
As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.
The key words MAY and MUST in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
| IRI | https://w3id.org/dpv/use-cases/vocab#UseCase |
skos:definition | An UseCase provides a description where information within the scope of DPVCG is expected to be relevant or applied, and acts as the basis for identifying requirements (including but not limited to creation of concepts). Use cases can contain descriptions of systems, their operations, actors and entities involved, restrictions or constraints, or any other pertinent detail. They can be a simple textual paragraph or elaborative structured documents (in which case we prefer to reference them here as an URL). |
dct:title)dct:description)dct:identifier)dct:contributor)dct:date)dct:source)dct:subject)dct:references)| IRI | https://w3id.org/dpv/use-cases/vocab#Requirement |
skos:definition | A Requirement is a functional or non-functional requirement desirable to provided by or implemented within DPVCG's outputs, primarily the DPV and its extensions. Requirements can relate to the design of the resource, specific concepts and relations within it, provision of a resource and its documentation, or any other pertinent usage or behaviour exhibited by resources developed within the scope of the DPVCG. |
dct:title)dct:description)dct:identifier)dct:references)dct:contributor)dct:source)dct:subject)The DPVCG was established as part of the SPECIAL H2020 Project, which received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No. 731601 from 2017 to 2019.
Harshvardhan J. Pandit was funded to work on DPV from 2020 to 2022 by the Irish Research Council's Government of Ireland Postdoctoral Fellowship Grant#GOIPD/2020/790.
The ADAPT SFI Centre for Digital Media Technology is funded by Science Foundation Ireland through the SFI Research Centres Programme and is co-funded under the European Regional Development Fund (ERDF) through Grant#13/RC/2106 (2018 to 2020) and Grant#13/RC/2106_P2 (2021 onwards).
The contributions of Harshvardhan J. Pandit have been made with the financial support of Science Foundation Ireland under Grant Agreement No. 13/RC/2106_P2 at the ADAPT SFI Research Centre.