Entities

DPV's entities are human and legal stakeholders, including individuals, organisations, institutions, or authorities. As such, all DPV-ODRL entities can be mapped as exactly matching their DPV counterpart, using the skos:exactMatch property, and as instances of ODRL parties, i.e., to be used as assigners or assignees of ODRL policies. For conciseness, only the mapping of dpv-odrl:Entity to dpv:Entity and to odrl:Party is included in the table, however this mapping is applicable to all DPV concepts of type Entity.

Furthermore, given the hierarchical nature of DPV, certain entity terms can also be used as a left operand to filter ODRL party collections, e.g., given a party collection that contains multiple human subjects of different types, using DPV's HumanSubject as the left operand and Patient as the right operand allows the expression of a policy which is only applicable to this type of human subject.

Processing

DPV's processing concepts are related to operations which can be performed over data. As such, all DPV-ODRL processing operations can be mapped as exactly matching their DPV counterpart, using the skos:exactMatch property, and as instances of ODRL actions. For conciseness, only the mapping of dpv-odrl:Processing to dpv:Processing and to odrl:Action is included in the table, however this mapping is applicable to all DPV concepts of type Processing.

Furthermore, a few DPV processing operations have a close match in the ODRL actions taxonomy. Such a relation is represented using the skos:related property, e.g., odrl:aggregate is similar to dpv:Aggregate.

Data

DPV's data concepts can be used to indicate the use of any data, personal and non-personal. As such, all DPV-ODRL data concepts can be mapped as exactly matching their DPV counterpart, using the skos:exactMatch property, and as instances of ODRL assets. For conciseness, only the mapping of dpv-odrl:Data to dpv:Data and to odrl:Asset is included in the table, however this mapping is applicable to all DPV concepts of type Data.

Furthermore, DPV's data source concepts can be used to refine asset collections and the personal data categories in the [[PD]] extension can also be used as constraints to refine party collections, e.g., by gender or age.

Technologies

DPV's technology concepts can be used to indicate the use of any technology, including AI. As such, all DPV-ODRL technology concepts can be mapped as exactly matching their DPV counterpart, using the skos:exactMatch property, and as instances of ODRL assets. For conciseness, only the mapping of dpv-odrl:Technology to dpv:Technology and to odrl:Asset is included in the table, however this mapping is applicable to all DPV concepts of type Technology.

Furthermore, DPV's [[TECH]] and [[AI]] extensions include technological concepts that can also be used to further constraint rules within ODRL policies, e.g., a certain asset can only be used to train an AI model.

Purpose

DPV's purpose concepts can be utilised to restrict usage of a certain asset to a particular purpose or set of purposes, e.g., allow a certain asset to be used only for research and development.

Technical and Organisational Measures

DPV's technical and organisational measures can be utilised to restrict usage of a certain asset only if a particular technical, organisational, legal, physical, or risk mitigation measure is in place, e.g, allow a certain asset to be used only if there is Multi-Factor Authentication.

Location & Jurisdiction

DPV's location concepts can be utilised to restrict usage of a certain asset to particular location. For this purpose, the [[[LOC]]] extension provides concepts regarding locations such as countries and regions based on the ISO 3166 standards.

Furthermore, given that DPV has the relation dpv:hasJurisdiction to represent locations as jurisdictions, when mapping that relation into an ODRL constraint, dpv-odrl:Location can also be used as a left operand to indicate jurisdiction.

Laws & Legal Bases

DPV's law and legal basis concepts can be utilised to indicate applicable laws and the legal grounds used to justify a certain processing activity, respectively. For this purpose, the [[[LEGAL]]] extensions provide concepts to represent laws, authorities, and other legal concepts in various jurisdictions.

Furthermore, consent controls can be used to require obtaining, providing, withdrawing, refusing, or reaffirming consent, and contract controls to require accepting, negotiating, offering, refusing, and terminating actions associated with a contract.

Duration & Frequency

DPV's duration and frequency concepts can be used to indicate how long a certain rule can be exercised and with what frequency, respectively. Furthermore, these DPV concepts have a close match with a few ODRL left operands. Such a relation is represented using the skos:related property, e.g., dpv:Duration has similarities with the odrl:elapsedTime left operand.

Rights & Justifications

DPV's rights and justifications concepts can be used to indicate applicable rights and to provide reasons or explanations to justify a certain processing activity, respectively. Both concepts can be used in isolation, or they can be used simultaneously to justify the exercising of a certain activity, e.g., a data subject wants to exercise their GDPR right to erasure given that their personal data is no longer required to be processed in relation to the purposes for which it was initially processed. Furthermore, the [[[JUSTIFICATIONS]]] extension provides a taxonomy of concepts to use as justifications for certain activities.

Risk

DPV's risk concepts can be used to permit or prohibit the usage of certain assets depending on the risks associated to them, including impacts and consequences of using them, as well as calculated likelihood and severity. For this purpose, the [[[RISK]]] extension provides concepts related to risk sources, impacts, consequences or risk mitigation measures.

Sector

DPV's sector concepts can be used to permit or prohibit the usage of certain assets depending on the area of application or domain that they are to be used. For this purpose, the [[[EU-AIAct]]] extension provides concepts to represent, e.g., the education or the employment sector.

Status & Processing Context

DPV's status concepts can be used to indicate information regarding the status or state of a certain process or activity. For instance, it can be used to permit the usage of a certain asset only if the consent status for that usage is valid, i.e., using the dpv:ConsentStatusValidForProcessing concept.

DPV's processing context concepts can be used to further restrict the context or conditions within which a certain process or activity takes place. For instance, it can be used to permit the usage of a certain asset only if there is human involvement for the purposes of having human oversight over the allowed action, i.e., using dpv-odrl:HumanInvolvement as the left operand of a constraint and the dpv:HumanInvolvementForOversight concept as the right operand.

Rules

DPV's sector concepts can be used to permit or prohibit the usage of certain assets depending on the area of application or domain that they are to be used. For this purpose, the [[[EU-AIAct]]] extension provides concepts to represent, e.g., the education or the employment sector.

Contractual Terms and Legal Agreements

DPV's contractual clauses and legal agreement concepts can be mapped as additional types of ODRL policies. In this case, besides being mapped as a subclass of a odrl:Policy, the owl:disjointWith property is used to indicate that each DPV-ODRL policy is mutually exclusive from all other existing ODRL policy types, which is a requirement from the ODRL Profile Mechanism for the definition of additional policy subclasses.