This document lists the examples for concepts in DPV and aligned vocabularies. The examples are available in DPVCG GitHub repo under ./examples path.

DPV Family of Documents

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.

The namespaces used in this document are as follows:

: <<>



skos:definitionAn Example 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).
  1. An Example MUST have a title (provided using dct:title)
  2. An Example MUST have a description (provided using dct:description)
  3. An Example MUST have an identifier with prefix 'U' (provided using dct:identifier)
  4. An Example MAY have one or more contributors (specified using dct:contributor)
  5. An Example MAY have a date (e.g. creation or modification) (specified using dct:date)
  6. An Example MAY specify the source of its information (using dct:source)
  7. An Example MAY specify its primary subject or concept (using dct:subject)
  8. An Example MAY specify relevant requirements derived from it (using dct:references)


E0001: Dummy Example 1

E0002: Dummy Example 2

E0003: Extending Purpose for Use-Case

E0004: DPV-OWL: Extending Purpose for Use-Case

E0005: Combining concepts to indicate they always occur together

E0006: Maintaining Interoperability between Use-Cases

E0007: Use of PersonalDataHandling to group how data is being processed

E0008: Nesting PersonalDataHandling for modular expression of processing operations

E0009: Adding human-readable descriptions

E0010: Using NACE codes to restrict Purposes

E0011: Storage Conditions

E0012: Data Sources

E0013: Automated Processing with Human Involvement

E0014: Derivation and inference of personal data

E0015: Indicating personal data is sensitive or special category

E0016: Protecting data using encryption and access control

E0017: Indicating staff training for use of Credentials

E0018: Notice used in an activity

E0019: Consent record

E0020: Controller-Processor agreement

E0021: Data transfer safeguards

E0022: Denoting Legal Basis

E0023: Consent as legal basis

E0024: Details of Consent

E0025: Consent Notice

E0026: Using consent types

E0027: Describing Entities

E0028: Contextual Necessity

E0029: Risk and Consequence