GDPRtEXT
type: Ontology
prior version: gdpr v0.1.owl
creator: http://purl.org/adaptcentre/people/harshvardhan_pandit
preferred namespace prefix: gdprov
preferred namespace uri: http://purl.org/adaptcentre/openscience/ontologies/GDPRtEXT
creator: http://purl.org/adaptcentre/people/dave_lewis
comment: PROV extension for linking Plans and parts of plans to their respective executions. Created by Daniel Garijo and Yolanda Gil
version info: Recommendation version 2013-04-30
description: The General Data Protection Regulation (GDPR) is comprised of several articles, each with points that refer to specific concepts. The general convention of referring to these points and concepts is to quote the specific article or point using a human-readable reference. This ontology provides a way to refer to the points within the GDPR using the EurLex ontology published by the European Publication Office. It also defines the concepts defined, mentioned, and requried by the GDPR using the Simple Knowledge Organization System (SKOS) ontology.
description: GDPRov is an OWL2 ontology to express provenance metadata of consent and data lifecycles towards documenting compliance for GDPR.
label: W3C PROVenance Interchange Ontology (PROV-O)
publisher: ADAPT
created: 2017-08-15
license: https://creativecommons.org/licenses/by/4.0/
version IRI: https://openscience.adaptcentre.ie/ontologies/gdprov/v/gdprov.0.6.owl
modified: 2018-04-06
status: draft
modified: 2017-10-01
comment: GDPRov is an ontology for expressing provenance metadata in the context of the General Data Protection Regulation (GDPR) and its compliance. It extends PROV-O and P-Plan. PROV-O is the ontology based on the PROV model, a W3C recommendation, while P-Plan is an extension of PROV-O. PROV is used to define terms or 'instances' of what has happened in the past, while P-Plan is used to define the abstract model or 'Plan' of things to happen. GDPRov uses P-Plan to create a template/model/plan as an abstract or model representation of a system which is then recorded using PROV-O instances to show something has happened. The aim of the ontology is to enable representation of consent and personal data lifecycles using terms relevant to GDPR and to facilitate expression of this information towards documentation related to compliance.
backward compatible with: gdpr v0.1.owl
abstract: The General Data Protection Regulation (GDPR) defines legal obligations over the use of personal data by organisations. This ontology aims to identify and model such terms and obligations as an OWL vocabulary and to directly link the terms to their occurence, usage, and influence in the GDPR text.
source: http://eur_lex.europa.eu/legal_content/EN/ALL/
modified: 2014-03-12
creator: http://purl.org/adaptcentre/people/HJP
title: The GDPR Provenance ontology
comment: This is an ontology to represent GDPR text as a set of RDF resources
created: 2017-08-01
preferred namespace uri: http://purl.org/net/p-plan#
creator: http://www.isi.edu/~gil/
label: GDPR text EXTensions
preferred namespace uri: http://purl.org/adaptcentre/openscience/ontologies/gdprov#
comment: This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page). If you wish to make comments regarding this document, please send them to public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org, archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback is welcome.
preferred namespace prefix: gdprtext
see also: Bartolini, C., Muthuri, R., & Santos, C. (2015, November). Using ontologies to model data protection requirements in workflows. In JSAI International Symposium on Artificial Intelligence (pp. 233-248). Springer, Cham.
version info: 0.6
preferred namespace prefix: p-plan
version info: 0.5
version info: 1.3
license: http://creativecommons.org/licenses/by-nc-sa/2.0/
creator: Harshvardhan J. Pandit
created: 2012-11-10
title: The P-Plan ontology
abstract: The General Data Protection Regulation (GDPR) is an European law governing the use of consent and personal data. Some of its obligations involve concepts related to the lifecycles of consent and personal data. Such obligations are concerned with how the collection, use, processing, sharing, and storing of consent and personal data takes place and provides the motivation for a form of documentation that can demonstrate the required information towards compliance. GDPRov is an OWL2 ontology for representing this information as provenance metadata using terms relevant to the GDPR. It extends PROV-O and P-Plan to represent the lifecyles as an abstract model of how things should happen or will happen (future) as well as instance of what has happened (past). The ontology is being developed as part of contributions towards PhD research by its primary author.
creator: http://delicias.dia.fi.upm.es/members/DGarijo#me
license: http://creativecommons.org/licenses/by/4.0/
description: PROV extension for linking Plans and parts of plans to their respective executions.
description: This ontology extends the canonical (official) GDPR text with additional annotations

location
type: AnnotationProperty
comment: Specifies the location of something referenced by it

involves
type: AnnotationProperty
comment: It signifies that two concepts are related within the context of the GDPR.

category
type: AnnotationProperty
comment: Classify prov-o terms into three categories, including 'starting-point', 'qualifed', and 'extended'. This classification is used by the prov-o html document to gently introduce prov-o terms to its users.

component
type: AnnotationProperty
comment: Classify prov-o terms into six components according to prov-dm, including 'agents-responsibility', 'alternate', 'annotations', 'collections', 'derivations', and 'entities-activities'. This classification is used so that readers of prov-o specification can find its correspondence with the prov-dm specification.

constraints
type: AnnotationProperty
comment: A reference to the principal section of the PROV-CONSTRAINTS document that describes this concept.

definition
type: AnnotationProperty
comment: A definition quoted from PROV-DM or PROV-CONSTRAINTS that describes the concept expressed with this OWL term.

dm
type: AnnotationProperty
comment: A reference to the principal section of the PROV-DM document that describes this concept.

editorialNote
type: AnnotationProperty
comment: A note by the OWL development team about how this term expresses the PROV-DM concept, or how it should be used in context of semantic web or linked data.

editorsDefinition
type: AnnotationProperty
comment: When the prov-o term does not have a definition drawn from prov-dm, and the prov-o editor provides one.

inverse
type: AnnotationProperty
comment: PROV-O does not define all property inverses. The directionalities defined in PROV-O should be given preference over those not defined. However, if users wish to name the inverse of a PROV-O property, the local name given by prov:inverse should be used.

http://www.w3.org/ns/prov#n
type: AnnotationProperty
comment: A reference to the principal section of the PROV-DM document that describes this concept.

qualifiedForm
type: AnnotationProperty
comment: This annotation property links a subproperty of prov:wasInfluencedBy with the subclass of prov:Influence and the qualifying property that are used to qualify it. Example annotation: prov:wasGeneratedBy prov:qualifiedForm prov:qualifiedGeneration, prov:Generation . Then this unqualified assertion: :entity1 prov:wasGeneratedBy :activity1 . can be qualified by adding: :entity1 prov:qualifiedGeneration :entity1Gen . :entity1Gen a prov:Generation, prov:Influence; prov:activity :activity1; :customValue 1337 . Note how the value of the unqualified influence (prov:wasGeneratedBy :activity1) is mirrored as the value of the prov:activity (or prov:entity, or prov:agent) property on the influence class.

unqualifiedForm
type: AnnotationProperty
comment: Classes and properties used to qualify relationships are annotated with prov:unqualifiedForm to indicate the property used to assert an unqualified provenance relation.

has Article
type: ObjectProperty
sub property of: has part
type: FunctionalProperty
domain: LegalResourceSubdivision
range: Article
comment: indicates the legal resource has the Article

has Chapter
type: ObjectProperty
sub property of: has part
type: FunctionalProperty
domain: LegalResource
range: Chapter
comment: indicates the legal resource has the Chapter

has Citation
type: ObjectProperty
sub property of: has part
domain: LegalResourceSubdivision
range: Citation
comment: indicates that the legal resource has the referenced citation

has Point
type: ObjectProperty
sub property of: has part
type: FunctionalProperty
domain: LegalResourceSubdivision
range: Point
comment: indicates the legal resource has the Point

has Recital
type: ObjectProperty
sub property of: has part
type: FunctionalProperty
domain: LegalResourceSubdivision
range: Regulation
comment: indicates the legal resource has the Recital

has Section
type: ObjectProperty
sub property of: has part
type: FunctionalProperty
domain: LegalResourceSubdivision
range: Section
comment: indicates the legal resource has the Section

has SubPoint
type: ObjectProperty
sub property of: has part
type: FunctionalProperty
domain: LegalResourceSubdivision
range: SubPoint
comment: indicates the legal resource has the SubPoint

is part of Article
type: ObjectProperty
sub property of: is part of
type: FunctionalProperty
domain: LegalResourceSubdivision
range: Article
comment: represents a legal resource subdivision to be part of a article

is part of Chapter
type: ObjectProperty
sub property of: is part of
type: FunctionalProperty
domain: LegalResourceSubdivision
range: Chapter
comment: represents a legal resource subdivision to be part of a chapter

is part of Point
type: ObjectProperty
sub property of: is part of
type: FunctionalProperty
domain: LegalResourceSubdivision
range: Point
comment: represents a legal resource subdivision to be part of a point

is part of Section
type: ObjectProperty
sub property of: is part of
type: FunctionalProperty
domain: LegalResourceSubdivision
range: Section
comment: represents a legal resource subdivision to be part of a section

anonymity level
type: ObjectProperty
domain: Data Entity
range: AnonymityLevel
deprecated: true

archives consent as
type: ObjectProperty
sub property of: hasOutputVar
sub property of:
  inverse of: isOutputVarOf
type: InverseFunctionalProperty
domain: Consent Archival Step
range: ConsentAgreement
comment: Archives the consent into some entity

collectsData
type: ObjectProperty
sub property of: hasOutputVar
sub property of:
  inverse of: isOutputVarOf
inverse of: isDataCollectedByStep
type: InverseFunctionalProperty
domain: Data Step
range: Data
comment: Links data obtained (collected) by the step/activity that acquired it

generatesAnonymisedData
type: ObjectProperty
sub property of: generatesData
sub property of:
  inverse of: isDataGeneratedByStep
inverse of: isAnonymisedByStep
type: InverseFunctionalProperty
domain: Data Anonymisation Step
range: AnonymisedData
comment: Indicates that an DataAnonymisationStep transforms a Data object into AnonymisedData

generatesConsentAgreement
type: ObjectProperty
sub property of: hasOutputVar
sub property of:
  inverse of: isOutputVarOf
inverse of: isGeneratedByStep
type: InverseFunctionalProperty
domain: Consent Step
range: ConsentAgreement
comment: Generates ConsentAgreement which is a the consent granted by the user based on the ConsentAgreementTemplate through a ConsentAcquisitionStep

generatesData
type: ObjectProperty
sub property of: hasOutputVar
sub property of:
  inverse of: isOutputVarOf
inverse of: isDataGeneratedByStep
type: InverseFunctionalProperty
domain: Data Step
range: Data
comment: produces data

hasAnonymityLevel
type: ObjectProperty
domain: PersonalData
range: AnonymityLevel
comment: Indicates the anonymity level of an AnonymisedData object using instances of the AnonymityLevel class

hasLegalBasis
type: ObjectProperty
range: Lawful Basis

has legal justification
type: ObjectProperty
domain: Activity
range: Lawful Basis
deprecated: true

hasSharedDataWith
type: ObjectProperty
domain: Data Sharing Activity
range: Agent

isAnonymisedByStep
type: ObjectProperty
sub property of: isDataGeneratedByStep
sub property of:
  inverse of: generatesData
type: FunctionalProperty

isConsentAgreementTemplateForStep
type: ObjectProperty
sub property of: isInputVarOf
sub property of:
  inverse of: hasInputVar
inverse of: usesConsentAgreementTemplate

isDataCollectedByStep
type: ObjectProperty
sub property of: isOutputVarOf
sub property of:
  inverse of: hasOutputVar
type: FunctionalProperty

isDataGeneratedByStep
type: ObjectProperty
sub property of: isOutputVarOf
sub property of:
  inverse of: hasOutputVar
type: FunctionalProperty

isGeneratedByStep
type: ObjectProperty
sub property of: isOutputVarOf
sub property of:
  inverse of: hasOutputVar
type: FunctionalProperty

isJustificationForDataStep
type: ObjectProperty
sub property of: isInputVarOf
sub property of:
  inverse of: hasInputVar
inverse of: isJustifiedUsingConsentAgreement

isJustifiedUsingConsentAgreement
type: ObjectProperty
sub property of: hasInputVar
sub property of:
  inverse of: isInputVarOf
domain: Data Step
range: ConsentAgreement
comment: justifies use of data by step through specified consent agreement

isPartOfProcess
type: ObjectProperty
sub property of: isStepOfPlan

isTermsAndConditionsForStep
type: ObjectProperty
sub property of: isInputVarOf
sub property of:
  inverse of: hasInputVar
inverse of: usesTermsAndConditions

isUsedByStep
type: ObjectProperty
sub property of: isInputVarOf
sub property of:
  inverse of: hasInputVar
inverse of: usesData

sharesData
type: ObjectProperty
sub property of: hasInputVar
sub property of:
  inverse of: isInputVarOf
inverse of: wasSharedBy
domain: Data Sharing Step
range: Data
comment: Indicates sharing of Data through a DataStep

sharesDataWith
type: ObjectProperty
domain: Data Sharing Step
range: Agent

sharesDataWithThirdParty
type: ObjectProperty
sub property of: topObjectProperty
domain: Data Sharing Step
range: ThirdParty
comment: Shares data with a third party
deprecated: true

transferredDataToRegion
type: ObjectProperty
domain: Cross Border Transfer Activity

transfersDataToRegion
type: ObjectProperty
domain: Cross-border Data Transfer

uses Consent Agreement
type: ObjectProperty
sub property of: hasInputVar
sub property of:
  inverse of: isInputVarOf
domain: Consent Step
range: ConsentAgreement
comment: uses Consent Agreement entity

usesConsentAgreementTemplate
type: ObjectProperty
sub property of: hasInputVar
sub property of:
  inverse of: isInputVarOf
domain: Consent Acquisition Step
range: ConsentAgreementTemplate
comment: links a Consent Acquisition Step with the Consent Agreement Template used to acquire consent

usesData
type: ObjectProperty
sub property of: hasInputVar
sub property of:
  inverse of: isInputVarOf
domain: Data Step
range: Data
comment: links step with data used

usesTermsAndConditions
type: ObjectProperty
sub property of: hasInputVar
sub property of:
  inverse of: isInputVarOf
domain: Consent Acquisition Step
range: TermsAndConditions
comment: Links a Consent Acquisition Step with the Terms and Conditions presented to the user when acquiring Consent

correspondsToStep
type: ObjectProperty
type: FunctionalProperty
domain: Activity
range: Step
definition: p-plan:correspondsToStep links a p-plan:Activity to its planned p-plan:Step

correspondsToVariable
type: ObjectProperty
type: FunctionalProperty
domain: Entity
range: Variable
definition: p-plan:correspondsToVariable binds a p-plan:Entity (used by a p-plan:Activity in the execution of a plan) to the p-plan:Variable it represented it in the p-plan:Plan.

hasInputVar
type: ObjectProperty
inverse of: isInputVarOf
domain: Step
range: Variable
definition: p-plan:hasInputVar binds a p-plan:Step to the p-plan:Variable that takes as input for the planned execution

hasOutputVar
type: ObjectProperty
inverse of: isOutputVarOf
type: InverseFunctionalProperty
domain: Step
range: Variable
definition: p-plan:hasOutputVar binds a p-plan:Step to the p-plan:Variable that will be produced as output in the planned execution

isDecomposedAsPlan
type: ObjectProperty
domain: MultiStep
range: Plan
definition: The p-plan:isDecomposedAsPlan relationship binds a p-plan:MultiStep to the p-plan:Plan holding the definition of that step. That is, p-plan:isDecomposedAsPlan links the MultiStep to the Plan sptecification where it is decomposed.

isInputVarOf
type: ObjectProperty
domain: Variable
range: Step
definition: p-plan:isInputVarOf links an input variable of a step to the step.

isOutputVarOf
type: ObjectProperty
type: FunctionalProperty
domain: Variable
range: Step
definition: p-plan:isOutputVarOf is intended to link an output variable of a step to the step.

isPrecededBy
type: ObjectProperty
type: TransitiveProperty
domain: Step
range: Step
comment: Property that asserts which Step preceeds the current one.

isStepOfPlan
type: ObjectProperty
domain: Step
range: Plan
definition: p-plan:isStepOfPlan links a p-plan:Step to the p-plan:Plan which it corresponds to.

isSubPlanOfPlan
type: ObjectProperty
sub property of: topObjectProperty
domain: Plan
range: Plan
definition: A p-plan:Plan may be a subplan of another bigger p-plan:Plan. p-plan:isSubPlanOfPlan is used to state the link among the two different plans. Note that if p1 is a p-plan:subPlan of p2, p1will not necessarily be a step of p2. A multistep will represent p1 in p2, and link to p1 with the p-plan.hasStepDecomposition relationship.

isVariableofPlan
type: ObjectProperty
domain: Variable
range: Plan
definition: p-plan:IsVariableOfPlan binds a p-plan:Variable to the p-plan:Plan it corresponds to.

actedOnBehalfOf
type: ObjectProperty
sub property of: wasInfluencedBy
sub property of:
  inverse of: influenced
domain: Agent
range: Agent
property chain axiom: qualifiedDelegation
property chain axiom: agent
comment: An object property to express the accountability of an agent towards another agent. The subordinate agent acted on behalf of the responsible agent in an actual activity.
category: starting-point
component: agents-responsibility
inverse: hadDelegate
qualified form: Delegation
qualified form: qualifiedDelegation

activity
type: ObjectProperty
sub property of: influencer
domain: ActivityInfluence
range: Activity
category: qualified
editorial note: This property behaves in spirit like rdf:object; it references the object of a prov:wasInfluencedBy triple.
editors definition: The prov:activity property references an prov:Activity which influenced a resource. This property applies to an prov:ActivityInfluence, which is given by a subproperty of prov:qualifiedInfluence from the influenced prov:Entity, prov:Activity or prov:Agent.
inverse: activityOfInfluence

agent
type: ObjectProperty
sub property of: influencer
domain: AgentInfluence
range: Agent
category: qualified
editorial note: This property behaves in spirit like rdf:object; it references the object of a prov:wasInfluencedBy triple.
editors definition: The prov:agent property references an prov:Agent which influenced a resource. This property applies to an prov:AgentInfluence, which is given by a subproperty of prov:qualifiedInfluence from the influenced prov:Entity, prov:Activity or prov:Agent.
inverse: agentOfInfluence

alternateOf
type: ObjectProperty
domain: Entity
range: Entity
category: expanded
component: alternate
constraints: http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig
definition: Two alternate entities present aspects of the same thing. These aspects may be the same or different, and the alternate entities may or may not overlap in time.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-alternate
inverse: alternateOf
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-alternate

atLocation
type: ObjectProperty
domain: Class
  union of: Activity
  union of: Agent
  union of: Entity
  union of: InstantaneousEvent
range: Location
comment: The Location of any resource.
comment: This property has multiple RDFS domains to suit multiple OWL Profiles. See PROV-O OWL Profile.
category: expanded
editorial note: The naming of prov:atLocation parallels prov:atTime, and is not named prov:hadLocation to avoid conflicting with the convention that prov:had* properties are used on prov:Influence classes.
editorial note: This property is not functional because the many values could be at a variety of granularies (In this building, in this room, in that chair).
inverse: locationOf
shares definition with: Location

entity
type: ObjectProperty
sub property of: influencer
domain: EntityInfluence
range: Entity
category: qualified
editorial note: This property behaves in spirit like rdf:object; it references the object of a prov:wasInfluencedBy triple.
editors definition: The prov:entity property references an prov:Entity which influenced a resource. This property applies to an prov:EntityInfluence, which is given by a subproperty of prov:qualifiedInfluence from the influenced prov:Entity, prov:Activity or prov:Agent.
inverse: entityOfInfluence

generated
type: ObjectProperty
sub property of: influenced
sub property of:
  inverse of: wasInfluencedBy
inverse of: wasGeneratedBy
type: AsymmetricProperty
type: IrreflexiveProperty
domain: Activity
range: Entity
category: expanded
component: entities-activities
editorial note: prov:generated is one of few inverse property defined, to allow Activity-oriented assertions in addition to Entity-oriented assertions.
inverse: wasGeneratedBy
shares definition with: Generation

hadActivity
type: ObjectProperty
domain: Influence
domain: Class
  union of: Delegation
  union of: Derivation
  union of: End
  union of: Start
range: Activity
comment: The _optional_ Activity of an Influence, which used, generated, invalidated, or was the responsibility of some Entity. This property is _not_ used by ActivityInfluence (use prov:activity instead).
comment: This property has multiple RDFS domains to suit multiple OWL Profiles. See PROV-O OWL Profile.
category: qualified
component: derivations
editorial note: The multiple rdfs:domain assertions are intended. One is simpler and works for OWL-RL, the union is more specific but is not recognized by OWL-RL.
inverse: wasActivityOfInfluence
shares definition with: Activity

hadGeneration
type: ObjectProperty
type: AsymmetricProperty
type: IrreflexiveProperty
domain: Derivation
range: Generation
comment: The _optional_ Generation involved in an Entity's Derivation.
category: qualified
component: derivations
inverse: generatedAsDerivation
shares definition with: Generation

hadMember
type: ObjectProperty
sub property of: wasInfluencedBy
sub property of:
  inverse of: influenced
domain: Collection
range: Entity
category: expanded
component: expanded
inverse: wasMemberOf
shares definition with: Collection

Axiom
annotated source: hadMember
annotated property: range
annotated target: Entity
comment: A collection is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be member of the collections.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-collection

hadPlan
type: ObjectProperty
domain: Association
range: Plan
comment: The _optional_ Plan adopted by an Agent in Association with some Activity. Plan specifications are out of the scope of this specification.
category: qualified
component: agents-responsibility
inverse: wasPlanOf
shares definition with: Plan

hadPrimarySource
type: ObjectProperty
sub property of: wasDerivedFrom
domain: Entity
range: Entity
property chain axiom: qualifiedPrimarySource
property chain axiom: entity
category: expanded
component: derivations
inverse: wasPrimarySourceOf
qualified form: PrimarySource
qualified form: qualifiedPrimarySource

Axiom
annotated source: hadPrimarySource
annotated property: subPropertyOf
annotated target: wasDerivedFrom
comment: hadPrimarySource property is a particular case of wasDerivedFrom (see http://www.w3.org/TR/prov-dm/#term-original-source) that aims to give credit to the source that originated some information.

hadRole
type: ObjectProperty
domain: Influence
domain: Class
  union of: Association
  union of: InstantaneousEvent
range: Role
comment: The _optional_ Role that an Entity assumed in the context of an Activity. For example, :baking prov:used :spoon; prov:qualified [ a prov:Usage; prov:entity :spoon; prov:hadRole roles:mixing_implement ].
comment: This property has multiple RDFS domains to suit multiple OWL Profiles. See PROV-O OWL Profile.
category: qualified
component: agents-responsibility
editors definition: prov:hadRole references the Role (i.e. the function of an entity with respect to an activity), in the context of an instantaneous usage, generation, association, start, and end.
inverse: wasRoleIn
shares definition with: Role

hadUsage
type: ObjectProperty
domain: Derivation
range: Usage
comment: The _optional_ Usage involved in an Entity's Derivation.
category: qualified
component: derivations
inverse: wasUsedInDerivation
shares definition with: Usage

influenced
type: ObjectProperty
inverse of: wasInfluencedBy
category: expanded
component: agents-responsibility
inverse: wasInfluencedBy
shares definition with: Influence

influencer
type: ObjectProperty
domain: Influence
range: Thing
comment: Subproperties of prov:influencer are used to cite the object of an unqualified PROV-O triple whose predicate is a subproperty of prov:wasInfluencedBy (e.g. prov:used, prov:wasGeneratedBy). prov:influencer is used much like rdf:object is used.
category: qualified
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-influence
editorial note: This property and its subproperties are used in the same way as the rdf:object property, i.e. to reference the object of an unqualified prov:wasInfluencedBy or prov:influenced triple.
editors definition: This property is used as part of the qualified influence pattern. Subclasses of prov:Influence use these subproperties to reference the resource (Entity, Agent, or Activity) whose influence is being qualified.
inverse: hadInfluence

invalidated
type: ObjectProperty
sub property of: influenced
sub property of:
  inverse of: wasInfluencedBy
inverse of: wasInvalidatedBy
type: AsymmetricProperty
type: IrreflexiveProperty
domain: Activity
range: Entity
category: expanded
component: entities-activities
editorial note: prov:invalidated is one of few inverse property defined, to allow Activity-oriented assertions in addition to Entity-oriented assertions.
inverse: wasInvalidatedBy
shares definition with: Invalidation

qualifiedAssociation
type: ObjectProperty
sub property of: qualifiedInfluence
domain: Activity
range: Association
comment: If this Activity prov:wasAssociatedWith Agent :ag, then it can qualify the Association using prov:qualifiedAssociation [ a prov:Association; prov:agent :ag; :foo :bar ].
category: qualified
component: agents-responsibility
inverse: qualifiedAssociationOf
shares definition with: Association
unqualified form: wasAssociatedWith

qualifiedAttribution
type: ObjectProperty
sub property of: qualifiedInfluence
domain: Entity
range: Attribution
comment: If this Entity prov:wasAttributedTo Agent :ag, then it can qualify how it was influenced using prov:qualifiedAttribution [ a prov:Attribution; prov:agent :ag; :foo :bar ].
category: qualified
component: agents-responsibility
inverse: qualifiedAttributionOf
shares definition with: Attribution
unqualified form: wasAttributedTo

qualifiedCommunication
type: ObjectProperty
sub property of: qualifiedInfluence
domain: Activity
range: Communication
comment: If this Activity prov:wasInformedBy Activity :a, then it can qualify how it was influenced using prov:qualifiedCommunication [ a prov:Communication; prov:activity :a; :foo :bar ].
category: qualified
component: entities-activities
inverse: qualifiedCommunicationOf
qualified form: Communication
shares definition with: Communication

qualifiedDelegation
type: ObjectProperty
sub property of: qualifiedInfluence
domain: Agent
range: Delegation
comment: If this Agent prov:actedOnBehalfOf Agent :ag, then it can qualify how with prov:qualifiedResponsibility [ a prov:Responsibility; prov:agent :ag; :foo :bar ].
category: qualified
component: agents-responsibility
inverse: qualifiedDelegationOf
shares definition with: Delegation
unqualified form: actedOnBehalfOf

qualifiedDerivation
type: ObjectProperty
sub property of: qualifiedInfluence
domain: Entity
range: Derivation
comment: If this Entity prov:wasDerivedFrom Entity :e, then it can qualify how it was derived using prov:qualifiedDerivation [ a prov:Derivation; prov:entity :e; :foo :bar ].
category: qualified
component: derivations
inverse: qualifiedDerivationOf
shares definition with: Derivation
unqualified form: wasDerivedFrom

qualifiedEnd
type: ObjectProperty
sub property of: qualifiedInfluence
domain: Activity
range: End
comment: If this Activity prov:wasEndedBy Entity :e1, then it can qualify how it was ended using prov:qualifiedEnd [ a prov:End; prov:entity :e1; :foo :bar ].
category: qualified
component: entities-activities
inverse: qualifiedEndOf
shares definition with: End
unqualified form: wasEndedBy

qualifiedGeneration
type: ObjectProperty
sub property of: qualifiedInfluence
type: AsymmetricProperty
type: IrreflexiveProperty
domain: Entity
range: Generation
comment: If this Activity prov:generated Entity :e, then it can qualify how it performed the Generation using prov:qualifiedGeneration [ a prov:Generation; prov:entity :e; :foo :bar ].
category: qualified
component: entities-activities
inverse: qualifiedGenerationOf
shares definition with: Generation
unqualified form: wasGeneratedBy

qualifiedInfluence
type: ObjectProperty
domain: Class
  union of: Activity
  union of: Agent
  union of: Entity
range: Influence
comment: Because prov:qualifiedInfluence is a broad relation, the more specific relations (qualifiedCommunication, qualifiedDelegation, qualifiedEnd, etc.) should be used when applicable.
category: qualified
component: derivations
inverse: qualifiedInfluenceOf
shares definition with: Influence
unqualified form: wasInfluencedBy

qualifiedInvalidation
type: ObjectProperty
sub property of: qualifiedInfluence
type: AsymmetricProperty
type: IrreflexiveProperty
domain: Entity
range: Invalidation
comment: If this Entity prov:wasInvalidatedBy Activity :a, then it can qualify how it was invalidated using prov:qualifiedInvalidation [ a prov:Invalidation; prov:activity :a; :foo :bar ].
category: qualified
component: entities-activities
inverse: qualifiedInvalidationOf
shares definition with: Invalidation
unqualified form: wasInvalidatedBy

qualifiedPrimarySource
type: ObjectProperty
sub property of: qualifiedInfluence
domain: Entity
range: PrimarySource
comment: If this Entity prov:hadPrimarySource Entity :e, then it can qualify how using prov:qualifiedPrimarySource [ a prov:PrimarySource; prov:entity :e; :foo :bar ].
category: qualified
component: derivations
inverse: qualifiedSourceOf
shares definition with: PrimarySource
unqualified form: hadPrimarySource

qualifiedQuotation
type: ObjectProperty
sub property of: qualifiedInfluence
domain: Entity
range: Quotation
comment: If this Entity prov:wasQuotedFrom Entity :e, then it can qualify how using prov:qualifiedQuotation [ a prov:Quotation; prov:entity :e; :foo :bar ].
category: qualified
component: derivations
inverse: qualifiedQuotationOf
shares definition with: Quotation
unqualified form: wasQuotedFrom

qualifiedRevision
type: ObjectProperty
sub property of: qualifiedInfluence
domain: Entity
range: Revision
comment: If this Entity prov:wasRevisionOf Entity :e, then it can qualify how it was revised using prov:qualifiedRevision [ a prov:Revision; prov:entity :e; :foo :bar ].
category: qualified
component: derivations
inverse: revisedEntity
shares definition with: Revision
unqualified form: wasRevisionOf

qualifiedStart
type: ObjectProperty
sub property of: qualifiedInfluence
domain: Activity
range: Start
comment: If this Activity prov:wasStartedBy Entity :e1, then it can qualify how it was started using prov:qualifiedStart [ a prov:Start; prov:entity :e1; :foo :bar ].
category: qualified
component: entities-activities
inverse: qualifiedStartOf
shares definition with: Start
unqualified form: wasStartedBy

qualifiedUsage
type: ObjectProperty
sub property of: qualifiedInfluence
domain: Activity
range: Usage
comment: If this Activity prov:used Entity :e, then it can qualify how it used it using prov:qualifiedUsage [ a prov:Usage; prov:entity :e; :foo :bar ].
category: qualified
component: entities-activities
inverse: qualifiedUsingActivity
shares definition with: Usage
unqualified form: used

specializationOf
type: ObjectProperty
sub property of: alternateOf
domain: Entity
category: expanded
component: alternate
constraints: http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig
definition: An entity that is a specialization of another shares all aspects of the latter, and additionally presents more specific aspects of the same thing as the latter. In particular, the lifetime of the entity being specialized contains that of any specialization. Examples of aspects include a time period, an abstraction, and a context associated with the entity.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-specialization
inverse: generalizationOf
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-specialization

used
type: ObjectProperty
sub property of: wasInfluencedBy
sub property of:
  inverse of: influenced
type: AsymmetricProperty
type: IrreflexiveProperty
domain: Activity
range: Entity
property chain axiom: qualifiedUsage
property chain axiom: entity
comment: A prov:Entity that was used by this prov:Activity. For example, :baking prov:used :spoon, :egg, :oven .
category: starting-point
component: entities-activities
inverse: wasUsedBy
qualified form: Usage
qualified form: qualifiedUsage

wasAssociatedWith
type: ObjectProperty
sub property of: wasInfluencedBy
sub property of:
  inverse of: influenced
domain: Activity
range: Agent
property chain axiom: qualifiedAssociation
property chain axiom: agent
comment: An prov:Agent that had some (unspecified) responsibility for the occurrence of this prov:Activity.
category: starting-point
component: agents-responsibility
inverse: wasAssociateFor
qualified form: Association
qualified form: qualifiedAssociation

wasAttributedTo
type: ObjectProperty
sub property of: wasInfluencedBy
sub property of:
  inverse of: influenced
domain: Entity
range: Agent
property chain axiom: qualifiedAttribution
property chain axiom: agent
comment: Attribution is the ascribing of an entity to an agent.
category: starting-point
component: agents-responsibility
definition: Attribution is the ascribing of an entity to an agent.
inverse: contributed
qualified form: Attribution
qualified form: qualifiedAttribution

Axiom
annotated source: wasAttributedTo
annotated property: subPropertyOf
annotated target: wasInfluencedBy
comment: Attribution is a particular case of trace (see http://www.w3.org/TR/prov-dm/#concept-trace), in the sense that it links an entity to the agent that ascribed it.
definition: IF wasAttributedTo(e2,ag1,aAttr) holds, THEN wasInfluencedBy(e2,ag1) also holds.

wasDerivedFrom
type: ObjectProperty
sub property of: wasInfluencedBy
sub property of:
  inverse of: influenced
domain: Entity
range: Entity
property chain axiom: qualifiedDerivation
property chain axiom: entity
comment: The more specific subproperties of prov:wasDerivedFrom (i.e., prov:wasQuotedFrom, prov:wasRevisionOf, prov:hadPrimarySource) should be used when applicable.
category: starting-point
component: derivations
definition: A derivation is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-existing entity.
inverse: hadDerivation
qualified form: Derivation
qualified form: qualifiedDerivation

Axiom
annotated source: wasDerivedFrom
annotated property: subPropertyOf
annotated target: wasInfluencedBy
comment: Derivation is a particular case of trace (see http://www.w3.org/TR/prov-dm/#term-trace), since it links an entity to another entity that contributed to its existence.

wasEndedBy
type: ObjectProperty
sub property of: wasInfluencedBy
sub property of:
  inverse of: influenced
type: AsymmetricProperty
type: IrreflexiveProperty
domain: Activity
range: Entity
property chain axiom: qualifiedEnd
property chain axiom: entity
comment: End is when an activity is deemed to have ended. An end may refer to an entity, known as trigger, that terminated the activity.
category: expanded
component: entities-activities
inverse: ended
qualified form: End
qualified form: qualifiedEnd

wasGeneratedBy
type: ObjectProperty
sub property of: wasInfluencedBy
sub property of:
  inverse of: influenced
type: AsymmetricProperty
type: IrreflexiveProperty
domain: Entity
range: Activity
property chain axiom: qualifiedGeneration
property chain axiom: activity
category: starting-point
component: entities-activities
inverse: generated
qualified form: Generation
qualified form: qualifiedGeneration

wasInfluencedBy
type: ObjectProperty
domain: Class
  union of: Activity
  union of: Agent
  union of: Entity
range: Class
  union of: Activity
  union of: Agent
  union of: Entity
comment: Because prov:wasInfluencedBy is a broad relation, its more specific subproperties (e.g. prov:wasInformedBy, prov:actedOnBehalfOf, prov:wasEndedBy, etc.) should be used when applicable.
comment: This property has multiple RDFS domains to suit multiple OWL Profiles. See PROV-O OWL Profile.
category: qualified
component: agents-responsibility
editorial note: The sub-properties of prov:wasInfluencedBy can be elaborated in more detail using the Qualification Pattern. For example, the binary relation :baking prov:used :spoon can be qualified by asserting :baking prov:qualifiedUsage [ a prov:Usage; prov:entity :spoon; prov:atLocation :kitchen ] . Subproperties of prov:wasInfluencedBy may also be asserted directly without being qualified. prov:wasInfluencedBy should not be used without also using one of its subproperties.
inverse: influenced
qualified form: Influence
qualified form: qualifiedInfluence
shares definition with: Influence

Axiom
annotated source: wasInfluencedBy
annotated property: domain
annotated target: Class
  union of: Activity
  union of: Agent
  union of: Entity
definition: influencee: an identifier (o2) for an entity, activity, or agent;
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-influence

Axiom
annotated source: wasInfluencedBy
annotated property: range
annotated target: Class
  union of: Activity
  union of: Agent
  union of: Entity
definition: influencer: an identifier (o1) for an ancestor entity, activity, or agent that the former depends on;
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-influence

wasInformedBy
type: ObjectProperty
sub property of: wasInfluencedBy
sub property of:
  inverse of: influenced
domain: Activity
range: Activity
property chain axiom: qualifiedCommunication
property chain axiom: activity
comment: An activity a2 is dependent on or informed by another activity a1, by way of some unspecified entity that is generated by a1 and used by a2.
category: starting-point
component: entities-activities
inverse: informed
qualified form: Communication
qualified form: qualifiedCommunication

wasInvalidatedBy
type: ObjectProperty
sub property of: wasInfluencedBy
sub property of:
  inverse of: influenced
type: AsymmetricProperty
type: IrreflexiveProperty
domain: Entity
range: Activity
property chain axiom: qualifiedInvalidation
property chain axiom: activity
category: expanded
component: entities-activities
inverse: invalidated
qualified form: Invalidation
qualified form: qualifiedInvalidation

wasQuotedFrom
type: ObjectProperty
sub property of: wasDerivedFrom
domain: Entity
range: Entity
property chain axiom: qualifiedQuotation
property chain axiom: entity
comment: An entity is derived from an original entity by copying, or 'quoting', some or all of it.
category: expanded
component: derivations
inverse: quotedAs
qualified form: Quotation
qualified form: qualifiedQuotation

Axiom
annotated source: wasQuotedFrom
annotated property: subPropertyOf
annotated target: wasDerivedFrom
comment: Quotation is a particular case of derivation (see http://www.w3.org/TR/prov-dm/#term-quotation) in which an entity is derived from an original entity by copying, or "quoting", some or all of it.

wasRevisionOf
type: ObjectProperty
sub property of: wasDerivedFrom
domain: Entity
property chain axiom: qualifiedRevision
property chain axiom: entity
comment: A revision is a derivation that revises an entity into a revised version.
category: expanded
component: derivations
inverse: hadRevision
qualified form: Revision
qualified form: qualifiedRevision

Axiom
annotated source: wasRevisionOf
annotated property: subPropertyOf
annotated target: wasDerivedFrom
comment: Revision is a derivation (see http://www.w3.org/TR/prov-dm/#term-Revision). Moreover, according to http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#term-Revision 23 April 2012 'wasRevisionOf is a strict sub-relation of wasDerivedFrom since two entities e2 and e1 may satisfy wasDerivedFrom(e2,e1) without being a variant of each other.'

wasStartedBy
type: ObjectProperty
sub property of: wasInfluencedBy
sub property of:
  inverse of: influenced
type: AsymmetricProperty
type: IrreflexiveProperty
domain: Activity
range: Entity
property chain axiom: qualifiedStart
property chain axiom: entity
comment: Start is when an activity is deemed to have started. A start may refer to an entity, known as trigger, that initiated the activity.
category: expanded
component: entities-activities
inverse: started
qualified form: Start
qualified form: qualifiedStart

atTime
type: DatatypeProperty
domain: InstantaneousEvent
range: dateTime
comment: The time at which an InstantaneousEvent occurred, in the form of xsd:dateTime.
category: qualified
component: entities-activities
shares definition with: InstantaneousEvent
unqualified form: endedAtTime
unqualified form: generatedAtTime
unqualified form: invalidatedAtTime
unqualified form: startedAtTime

endedAtTime
type: DatatypeProperty
domain: Activity
range: dateTime
comment: The time at which an activity ended. See also prov:startedAtTime.
category: starting-point
component: entities-activities
editorial note: It is the intent that the property chain holds: (prov:qualifiedEnd o prov:atTime) rdfs:subPropertyOf prov:endedAtTime.
qualified form: End
qualified form: atTime

generatedAtTime
type: DatatypeProperty
domain: Entity
range: dateTime
comment: The time at which an entity was completely created and is available for use.
category: expanded
component: entities-activities
editorial note: It is the intent that the property chain holds: (prov:qualifiedGeneration o prov:atTime) rdfs:subPropertyOf prov:generatedAtTime.
qualified form: Generation
qualified form: atTime

invalidatedAtTime
type: DatatypeProperty
domain: Entity
range: dateTime
comment: The time at which an entity was invalidated (i.e., no longer usable).
category: expanded
component: entities-activities
editorial note: It is the intent that the property chain holds: (prov:qualifiedInvalidation o prov:atTime) rdfs:subPropertyOf prov:invalidatedAtTime.
qualified form: Invalidation
qualified form: atTime

startedAtTime
type: DatatypeProperty
domain: Activity
range: dateTime
comment: The time at which an activity started. See also prov:endedAtTime.
category: starting-point
component: entities-activities
editorial note: It is the intent that the property chain holds: (prov:qualifiedStart o prov:atTime) rdfs:subPropertyOf prov:startedAtTime.
qualified form: Start
qualified form: atTime

value
type: DatatypeProperty
domain: Entity
category: expanded
component: entities-activities
definition: Provides a value that is a direct representation of an entity.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute-value
editorial note: The editor's definition comes from http://www.w3.org/TR/rdf-primer/#rdfvalue
editorial note: This property serves the same purpose as rdf:value, but has been reintroduced to avoid some of the definitional ambiguity in the RDF specification (specifically, 'may be used in describing structured values').

Banking Info
type: Class
subclass of: Sensitive Personal Data
disjoint with: ConsentAgreement
disjoint with: ConsentAgreementTemplate
disjoint with: TermsAndConditions
comment: Information about a Customer's Bank/Payment/Account/Transaction

Customer Info
type: Class
subclass of: PersonalData
disjoint with: ConsentAgreement
disjoint with: ConsentAgreementTemplate
disjoint with: TermsAndConditions
comment: Information about the Customer (A User who has ordered products)

Service User
type: Class
subclass of: Data Subject
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: A User of the Services provided

Principle of Accountability
type: Class
subclass of: Principle
involves: Compliance
involves: Controller Responsibility
involves: Lawful Basis
involves: Processing
comment: The principle of accountability states that the controller shall be responsible for, and be able to demonstrate compliance with the processing of personal data as defined by the justifications permissible under the GDPR

Principle of Accuracy
type: Class
subclass of: Principle
involves: Erase Data
involves: Kept up to date
involves: Personal Data
involves: Rectify Data
involves: Rectify Inaccuracies
comment: The principle of accuracy states that personal data must be accurate and, where necessary, kept up to date; every reasonable step must be taken to ensure that personal data that are inaccurate, having regard to the purposes for which they are processed, are erased or rectified without delay.

Accuracy is contested
type: Class
subclass of: Right to restrict processing
involves: Personal Data
comment: The data subject can exercise the right to restrict processing of their personal data when the accuracy of personal data is contested

Accurate Collection
type: Class
subclass of: Obligation for data collection
involves: Collection of Personal Data
involves: Personal Data
comment: This obligation specifies that the collection of (or collected) personal data should in an accurate form - i.e. the personal data should be accurate.

Activity
type: Class
subclass of: Concept
comment: An Activity signifies some process(es) or step(s) towards specific deed(s), action(s), function(s), or sphere(s) of action.

Adequate for processing
type: Class
subclass of: Data Retention
involves: Processing
involves: Store Data
comment: Only the personal data adequat for required processing should be maintained

Adherence
type: Class
subclass of: Awarding Seals and Certifications
comment: The seal or certification does not reduce or impact the responsiblity of the controller or processor for compliance with the GDPR

Anonymous Data
type: Class
subclass of: Data
involves: Personal Data
comment: Data is termed to be anonymous if it cannot be connected or associated with individual person or persons that have provided or are associated with it.

Appointing Sub-Processors
type: Class
subclass of: Processor Obligations
involves: Processor
involves: Sub-Processor
comment: These are the obligations for Processors over appointing sub-processors

Appointment of Processors
type: Class
subclass of: Activity
subclass of: Controller Obligation
involves: Controller
involves: Processor
comment: These are the obligations specified by the GDPR for the appointment of Processors by Controllers.

Archive Data
type: Class
subclass of: Data Activity
involves: Personal Data
comment: An activity where personal data is archived

Article
type: Class
subclass of: LegalResourceSubdivision
comment: Article in GDPR text
example: gdpr:article10 a eli:LegalResourceSubdivision, GDPRtext:Article ; eli:is_part_of gdpr:GDPR, gdpr:chapterII ; eli:number "10"^^xsd:string ; eli:title_alternative "Article 10"^^xsd:string ; GDPRtext:hasPoint gdpr:article10-1 ; GDPRtext:isPartOfChapter gdpr:chapterII .

Assist in complying with rights
type: Class
subclass of: Processor Obligations
involves: Compliance
involves: Controller
involves: Processor
involves: Data Subject's Rights
comment: Processors must assist Controllers in complying with the various rights provided by the GDPR to data subjects which can be exercised at any time.

Automatic decision making with significant effect
type: Class
subclass of: Automated Processing
subclass of: Factors for Impact Assessment
involves: Data Subject
involves: Personal Data
comment: Automated decision making with significant effect
comment: This type of processing involves automated processing that does decision making having significant effects on the data subject.

Automated Processing
type: Class
subclass of: Processing
subclass of: Use Data
involves: Personal Data
comment: This is automated processing of data subject's personal data.

Can be withdrawn easily
type: Class
subclass of: Obligation for obtaining consent
involves: Given Consent
involves: Withdrawing Given Consent
comment: This obligation states that the data subject should be able to withdraw the consent as easily as it was to give it.

Certification
type: Class
subclass of: Seals and Certifications
comment: A certification pertaining to GDPR compliance

Certification Body
type: Class
subclass of: Entity
involves: Certification
involves: Seal
comment: A Certification Body is an entity that can award/issue/renew a certification pertaining to compliance towards the GDPR.

Chapter
type: Class
subclass of: LegalResourceSubdivision
comment: Chapter in GDPR text
example: gdpr:chapterI a eli:LegalResourceSubdivision, GDPRtext:Chapter ; eli:is_part_of gdpr:GDPR ; eli:number "I"^^xsd:string ; eli:title "General provisions"^^xsd:string ; eli:title_alternative "Chapter I"^^xsd:string ; GDPRtext:hasArticle gdpr:article1, gdpr:article2, gdpr:article3, gdpr:article4 .

Citation
type: Class
subclass of: LegalResourceSubdivision
comment: Citation in GDPR text
example: gdpr:citation1 a eli:LegalResourceSubdivision, GDPRtext:Citation ; eli:description "OJ C 229, 31.7.2012, p. 90."^^xsd:string ; eli:is_part_of gdpr:GDPR ; eli:number "1"^^xsd:string .

Clear explanation
type: Class
subclass of: Obligation for obtaining consent
involves: Processing
comment: Obtaining consent must provide clear explanations of the processing involved over the personal data

Code of Conduct
type: Class
subclass of: Concept
comment: A Code of Conduct for the purpose of specifying the application of GDPR which may be monitored, evaluated, or processed by a third party appointed by the organisation.

Collection of Personal Data
type: Class
subclass of: Data Activity
involves: Personal Data
comment: Collection of Personal Data is an Activity that deals with acquiring data subject's personal data through some model of interaction.

Compliance
type: Class
subclass of: Concept
comment: Represents the act of complying with the obligations and actions specified by the GDPR.

Compliance with Controller's instructions
type: Class
subclass of: Processor Obligations
involves: Controller
involves: Processor
comment: The processor has an obligation to comply with the controller's instructions

Awarding Seals and Certifications
type: Class
subclass of: Seals and Certifications
involves: Adherence
involves: Maximum validty 3 years
involves: Voluntary accredition
comment: GDPR mentions some conditions or criterion for the creation and issuing of seals and certifications pertaining to GDPR compliance

Confirming or matching datasets
type: Class
subclass of: Factors for Impact Assessment
subclass of: Processing
subclass of: Use Data
involves: Personal Data
comment: This type of processing involves matching data subject's identity or personal data in different datasets.

Consent
type: Class
subclass of: Concept
comment: Consent in the context of the GDPR refers to the assent or agreement by the data subject in relation to their personal data for the proposed processing activities associated with one or more organisations.

Consent Activity
type: Class
subclass of: Activity
involves: Consent
comment: An activity involving data subject's consent.

Context of data collection
type: Class
subclass of: Purpose of new processing
involves: Collection of Personal Data
comment: The purpose of new processing should take the context of how the original data was collected into consideration

Contract with Data Subject
type: Class
subclass of: Lawful Basis
involves: Data Subject
comment: The lawful basis for processing personal data is provided through a contract with the data subject.

Controller
type: Class
subclass of: Entity
comment: The natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data.

Controller Accountability
type: Class
subclass of: Controller Obligation
involves: Controller
comment: These obligations specify the accountability of the Controller.

Controller has taken action
type: Class
subclass of: Exceptions on reporting data breach
involves: Controller
involves: Data Breach
comment: The data subjects were not notified about the data breach because the controller had already taken action regarding the data breach.

Controller Obligation
type: Class
subclass of: Obligation
involves: Controller
comment: These are the obligations specified by the GDPR as being specifically the responsbility of the Controller.

Controller Representative
type: Class
subclass of: Entity
involves: Controller
comment: A natural or legal person established in the Union who, designated by the controllerin writing, represents the controller with regard to their respective obligations under the GDPR.

Controller Responsibility
type: Class
subclass of: Controller Obligation
involves: Controller
comment: These obligations specify the responsiblity of the Controller

Co-operate with DPA
type: Class
subclass of: Controller Obligation
subclass of: Processor Obligations
involves: DPA
comment: This obligation specifies the Controller/Processor must co-operate with the Data Protection Authority (DPA).

Crime data
type: Class
subclass of: Sensitive Personal Data
involves: Data Subject
comment: Personal data related to criminal convictions and offences.

Cross-border Transfer
type: Class
subclass of: Data Activity
subclass of: Factors for Impact Assessment
involves: Personal Data
comment: Cross-border data transfer refers to data transfer crossing the boundaries of EU (legislative) region.

DPA
type: Class
subclass of: Entity
comment: The Data Protection Authority (DPA) is a public institution responsible for monitoring the application of data protection laws.

DPO
type: Class
subclass of: Entity
involves: Controller
involves: Monitor Compliance
involves: Notify about DPO
involves: Processor
comment: The Data Protection Officer (DPO) is an individual(s) appointed by the organisation to monitor compliance and assist in complying with the GDPR.

DPO Obligation
type: Class
subclass of: Obligation
involves: DPO
comment: These are the obligations specified for the Data Protection Office (DPO) within the GDPR

Data
type: Class
subclass of: Concept
comment: A generic term to refer to Data.

Data Activity
type: Class
subclass of: Activity
involves: Personal Data
comment: An activity involving personal data of data subject(s).

Data Breach
type: Class
subclass of: Concept
involves: Personal Data
comment: A data breach is the intentional or unintentional release of secure or private/confidential information to an untrusted environment.

Principle of Data Minimisation
type: Class
subclass of: Principle
involves: Accurate Collection
involves: Explicit Purpose
involves: Personal Data
involves: Processing
involves: Specified purpose
comment: The principle of data minimisation states that personal data must be adequate, relevant and limited to what is necessary in relation to the purposes for which they are processed.

Data no longer needed for original purpose
type: Class
subclass of: Right to restrict processing
involves: Collection of Personal Data
involves: Personal Data
comment: The data subject can exercise the right to restrict processing of their personal data when the personal data is no longer required for the original purpose it was collected under

Data protection by design and default
type: Class
subclass of: Controller Obligation
involves: Controller
comment: This obligation requires Controllers to follow data protection by design and by default.

Data Security
type: Class
subclass of: Controller Obligation
subclass of: Processor Obligations
involves: Controller
involves: Personal Data
involves: Security of Personal Data
comment: These are obligations regarding security of data managed by the Controllers.

Data Subject
type: Class
subclass of: Entity
comment: An individual or entity to whom their personal data relates.

Data inferred or derived
type: Class
subclass of: Exlcusions and Exceptions
involves: Data
comment: The obligation or activity coult not be completed because the data was inferred or derived, and therefore did not come from the data subject or other sources.

Demonstrating Consent
type: Class
subclass of: Activity
subclass of: Compliance
involves: Given Consent
involves: Valid Consent
comment: The act of demonstrating consent is an activity whereby previously acquired consent is provided as sufficient justification for processing activities involving data subject's personal information.

Direct Marketing
type: Class
subclass of: Marketing
involves: Data Subject
comment: Type of Marketing that reaches data subjects directly by communications directly addressed to the data subject.

Employment Law
type: Class
subclass of: Lawful Basis
comment: Lawful basis for processing is provided by Employment Law

Entity
type: Class
subclass of: Concept
comment: A general term for any institution, company, corporation, partnership, government agency, university, or any other organization including individuals.

Erase Data
type: Class
subclass of: Data Activity
involves: Personal Data
comment: An activity that erases data

Erase if conesnt was withdrawn
type: Class
subclass of: Right of Erasure
involves: Erase Data
involves: Given Consent
involves: Withdrawing Given Consent
comment: The right of erasure applies when the data subject withdraws given consent

Erase if no longer needed for original purpose
type: Class
subclass of: Right of Erasure
involves: Collection of Personal Data
involves: Erase Data
involves: Explicit Purpose
comment: The right to erasure applies where data is no longer needed for original purposes for which it was collected

Evaluation of data subjects
type: Class
subclass of: Factors for Impact Assessment
involves: Data Subject
comment: Whether the proposed activity involves the evaluation of the data subject.

Exceptions on reporting data breach
type: Class
subclass of: Exlcusions and Exceptions
involves: Report Data Breach
comment: Exceptions associated with compliance for reporting data breach to the affected data subjects.

Exlcusions and Exceptions
type: Class
subclass of: Concept
comment: Exclusions and Exemptions provided by the GDPR for not complying with the specified obligations.

Exempted by National Law
type: Class
subclass of: Lawful Basis
comment: Lawful basis for processing is provided by National Law

Exempted without identity
type: Class
subclass of: Exlcusions and Exceptions
involves: Identification of Data Subject
comment: The request or activity could not or was not completed because there was no sufficient proof of the data subject's identity.

Exercise Rights
type: Class
subclass of: Activity
involves: Data Subject
involves: Data Subject's Rights
comment: The activity represents exercising of rights provided by GDPR by the data subject.

Existence of safeguards
type: Class
subclass of: Purpose of new processing
involves: Personal Data
involves: Security of Personal Data
comment: The purpose of new processing should take into context the existence of appropriate safeguards

Explicit Purpose
type: Class
subclass of: Obligation for data collection
involves: Collection of Personal Data
comment: This obligation specifies that the collected (or collection) of personal data should be for/with explicit purposes.

Factors for Impact Assessment
type: Class
subclass of: Concept
involves: Impact Assessment
comment: These are the factors stated by the GDPR for Impact Assessment.

Rights protection
type: Class
subclass of: Exlcusions and Exceptions
comment: The stated obligation could not be completed as it concerns rights protection.

Freely given
type: Class
subclass of: Valid Consent
involves: Given Consent
involves: Obtaining Consent from Data Subject
comment: GDPR obligation that specifies consent must be freely given by the data subject for it to be valid.

Genetic Data
type: Class
subclass of: Sensitive Personal Data
involves: Data Subject
comment: Personal data relating to the inherited or acquired genetic characteristics of a natural person which result from the analysis of a biological sample from the natural person in question, in particular chromosomal, deoxyribonucleic acid (DNA) or ribonucleic acid (RNA) analysis, or from the analysis of another element enabling equivalent information to be obtained.

Given Consent
type: Class
subclass of: Consent
subclass of: Lawful Basis
involves: Data Subject
involves: Personal Data
involves: Processing
comment: Given Consent refers specifically to the form of consent given by the data subject in relation to their personal data and the proposed usage by activities.

Harm was remote
type: Class
subclass of: Exceptions on reporting data breach
involves: Data Breach
comment: The data subjects were not notified about the data breach because the harm was deemed to be remote.

Health data
type: Class
subclass of: Sensitive Personal Data
involves: Data Subject
comment: Personal data related to the physical or mental health of a natural person, including the provision of health care services, which reveal information about his or her health status.

Historic, Statistical, or Scientific purposes
type: Class
subclass of: Lawful Basis
comment: Lawful basis if provided by the GDPR for processing related to historic, statistical, or scientific purposes.

Identifiable for required processing
type: Class
subclass of: Data Retention
involves: Identification of Data Subject
involves: Store Data
comment: Retention of personal data should be identifiable for the requried processing

Identification of Data Subject
type: Class
subclass of: Activity
involves: Data Subject
comment: Activity where the data subject is explicitly identified through direct or indirect means.

If and where Controller is processing
type: Class
subclass of: Right to Access Personal Data
involves: Controller
involves: Personal Data
involves: Processing
comment: The right to access personal data also includes information about whether and where the controller is processing the data subject's personal data

Impact Assessment
type: Class
subclass of: Activity
involves: Factors for Impact Assessment
involves: Personal Data
involves: Processing
comment: The activity wherein the controller carries out an assessment of the impact of the envisaged processing operations on the protection of personal data.

Implement technical measures
type: Class
subclass of: Controller Responsibility
involves: Compliance
involves: Controller
comment: This obligation requires Controllers to implement the required technical measures necessary for compliance of the GDPR

Impose confidentiality obligations on personnel
type: Class
subclass of: Processor Obligations
involves: Processor
comment: The processor must impose confidentiality agreements on its personnel in relation to handling of personal data

Information about automated processing with significant effects
type: Class
subclass of: Right to Access Personal Data
involves: Automated Processing
involves: Data Subject
comment: The right to access personal data also includes information about automated processing that has significant effects on the data subject.

Information about categories of recipients
type: Class
subclass of: Right to Access Personal Data
involves: Personal Data
involves: Record categories of recipients
involves: Share Personal Data with Third Party
comment: The right to access personal data also includes information about the categories of recipients the data is shared with.

Information about categories of data being processed
type: Class
subclass of: Right to Access Personal Data
involves: Personal Data
involves: Processing
comment: The right to access personal data also includes information about categories of data being processed

Information about rights
type: Class
subclass of: Right to Access Personal Data
involves: Data Subject's Rights
comment: The right to access personal data also includes information about the existence of rights provided by the GDPR to the data subject

Information about processing
type: Class
subclass of: Right to Access Personal Data
involves: Personal Data
involves: Processing
comment: The right to access personal data also includes information about the processing of personal data of the data subject

Information about data source
type: Class
subclass of: Right to Access Personal Data
involves: Collection of Personal Data
involves: Personal Data
comment: The right to access personal data also includes information about the source of the personal data

Information about storage period
type: Class
subclass of: Right to Access Personal Data
involves: Personal Data
involves: Store Data
comment: The right to access personal data also includes information about the storage period of the data subject's personal data

Inform Controller of conflict with law
type: Class
subclass of: Processor Obligations
involves: Controller
comment: In case of conflict with the controller's intructions and the law, the processor must immediately inform the controller of this conflict

Information about third parties
type: Class
subclass of: Right to basic information about processing of personal data
involves: Controller
involves: Processor
involves: Share Personal Data with Third Party
comment: The right to basic information also provides data subject's with information about third parties involved in the processing.

Concise
type: Class
subclass of: Right to Transparency
involves: Right to Transparency
comment: The information provided under the right to transparency should be concise

Easily Accessible
type: Class
subclass of: Right to Transparency
involves: Right to Transparency
comment: The information provided under the right to transparency should be easily accessible

Intelligible
type: Class
subclass of: Right to Transparency
involves: Right to Transparency
comment: The information provided under the right to transparency should be intelligible

Transparent
type: Class
subclass of: Right to Transparency
involves: Principle of Lawfulness, Fairness, and Transparency
involves: Right to Transparency
comment: The information provided under the right to transparency should be transparent and clear (i.e. not umambigious or vague)

Informed
type: Class
subclass of: Valid Consent
involves: Data Activity
involves: Given Consent
involves: Obtaining Consent from Data Subject
involves: Personal Data
comment: GDPR obligation that specifies consent must be informed for it be valid.

Principle of Integrity and Confidentiality
type: Class
subclass of: Principle
involves: Data Security
involves: Personal Data
involves: Processing
involves: Protection against accidental loss
involves: Protection against damage
involves: Protection against destruction
comment: The principle of integrity and confidentiality states that personal data must be processed in a manner that ensures appropriate security of the personal data, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage, using appropriate technical or organisational measures.

Is impossible
type: Class
subclass of: Exlcusions and Exceptions
comment: The obligation or activity could not be completed as it was deemed to be impossible.

Joint Controller
type: Class
subclass of: Controller
involves: Controller
comment: A joint controller is two or more controllers jointly determine the purposes and means of processing.

Kept up to date
type: Class
subclass of: Data Retention
involves: Personal Data
comment: Retained personal data must be kept up-to-date

Large scale processing
type: Class
subclass of: Factors for Impact Assessment
subclass of: Processing
subclass of: Use Data
involves: Personal Data
involves: Processing
comment: The processing of personal data at a large scale of quantity or significant proportions.

Lawful Basis
type: Class
subclass of: Obligation
involves: Processing
comment: This provides the basis for lawful processing of personal data.

Principle of Lawfulness, Fairness, and Transparency
type: Class
subclass of: Principle
involves: Data
involves: Lawful Basis
involves: Processing
comment: The principle of lawfulness, fairness, and transparency states that personal data must be processed lawfully, fairly and in a transparent manner in relation to the data subject.

Legal Claims
type: Class
subclass of: Lawful Basis
comment: Lawful basis for processing is provided by legal claims.

Legal Obligations
type: Class
subclass of: Lawful Basis
comment: Lawful basis for processing is covered by legal obligation(s).

Legitimate Interests
type: Class
subclass of: Lawful Basis
involves: Data Subject
comment: Lawful basis for processing is provided through the legitimate interests pursued by the Controller or by a third party

Legitimate purpose
type: Class
subclass of: Obligation for data collection
involves: Collection of Personal Data
comment: This specifies that the collection (or collected) personal data should be used/specified to be used for legitimate purposes.

Liability of Joint-Controllers
type: Class
subclass of: Controller Obligation
involves: Joint Controller
comment: These specify the liability of Joint Controllers, i.e. cases where more than one Controller share the responsiblity.

Limited for processing
type: Class
subclass of: Data Retention
involves: Personal Data
involves: Processing
comment: Personal data retained should be limited in its use only for the requried processing

Lnk between new and old processing
type: Class
subclass of: Purpose of new processing
involves: Processing
involves: Purpose of new processing
comment: Whether there is a link between the new and old purposes of processing

Made Public
type: Class
subclass of: Lawful Basis
involves: Data Subject
comment: Lawful basis is provided through the data being publicly made available by the data subject

Maintain Record of Breach
type: Class
subclass of: Report Data Breach
involves: Data Breach
comment: GDPR mandates the recording of data breaches and its effects.

Maintain records for processing
type: Class
subclass of: Controller Obligation
subclass of: Processor Obligations
involves: Processing
comment: This obligation requires the Controller/Processor to maintain adequate records about their processing activities.

Marketing
type: Class
subclass of: Activity
comment: The process or technique of promoting, selling, and distributing a product or service.

Maximum validty 3 years
type: Class
subclass of: Awarding Seals and Certifications
comment: The maximum validity for all seals and certifications should be 3 years from the date of issue.

Medical or Diagnostics
type: Class
subclass of: Lawful Basis
involves: Data Subject
comment: Lawful basis for processing is provided by the GDPR for medical or diagnostics purposes pertaining to the data subject

Monitor Compliance
type: Class
subclass of: Activity
subclass of: Compliance
subclass of: DPO Obligation
involves: Obligation
involves: Principle
involves: Data Subject's Rights
comment: The activity or process of overseeing an organisation's compliance.

National Security
type: Class
subclass of: Exlcusions and Exceptions
comment: The stated obligation could not be completed as it concerns national security.

Nature of data involved
type: Class
subclass of: Purpose of new processing
involves: Personal Data
comment: The nature of the personal data involved, whether it is sensitive or confidential.

No charges levied
type: Class
subclass of: Right to Access Personal Data
involves: Data Subject's Rights
comment: The right to access personal data should not incur any undue charge levied on the data subject for exercising their right

Not-for-profit organisation
type: Class
subclass of: Lawful Basis
comment: Lawful basis is provided by the GDPR for activities of/for not-for-profit organisations

Not from silence or inactivity
type: Class
subclass of: Obligation for obtaining consent
involves: Given Consent
comment: Consent should not be obtained from silence or inactivity of the data subject

Not further processed
type: Class
subclass of: Obligation for data collection
involves: Processing
comment: This obligation specifies that the collected personal data should not be processed beyond the purpose for which it was originally collected without an updated consent for the proposed purposes.

Notification requires disproportionate efforts
type: Class
subclass of: Exceptions on reporting data breach
subclass of: Requires disproportionate efforts
involves: Report Data Breach
comment: The data subjects were not notified about the data breach because it required disproportionate efforts.

Notify consequences of breach
type: Class
subclass of: Notify Data Subject of Breach
involves: Data Breach
comment: Affected data subject's must be notified about the consequences of the data breach.

Notify about DPO
type: Class
subclass of: Notify Data Subject of Breach
involves: Data Breach
involves: Data Subject
comment: Affected data subjects must be notified with the name and contact of the DPO responsible/handling for the data breach.

Notify Data Subject of Breach
type: Class
subclass of: Report Data Breach
involves: Data Breach
involves: Data Subject
comment: Affected data subjects must be notified of the data breach and its effects.

Notify measures taken
type: Class
subclass of: Notify Data Subject of Breach
involves: Data Breach
involves: Data Subject
comment: Affect data subjets must be notified of the measures taken against the data breach.

Obligation
type: Class
subclass of: Concept
comment: These are the obligations specified by the GDPR. Following the obligations is necessary for compliance.

Obligation for data collection
type: Class
subclass of: Obligation
involves: Collection of Personal Data
comment: Collection of Personal Data is an Activity that deals with acquiring data subject's personal data through some model of interaction.

Obligation for obtaining consent
type: Class
subclass of: Obligation
involves: Obtaining Consent from Data Subject
comment: These are the obligations specified by the GDPR for obtaining consent

Obtaining Consent from Data Subject
type: Class
subclass of: Consent Activity
involves: Data Subject
involves: Given Consent
comment: The act of getting a data subject's consent.

Only act on Controller instructions
type: Class
subclass of: Processor Obligations
involves: Controller
comment: The processor must only act on the intructions provided and documented by the controller

Outside Material Scope
type: Class
subclass of: Exlcusions and Exceptions
comment: The activity was deemed to be outside the material scope of the GDPR.

Personal Data
type: Class
subclass of: Data
involves: Data Subject
comment: Personal data means any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person.

Point
type: Class
subclass of: LegalResourceSubdivision
comment: Point in GDPR text
example: gdpr:article27-2 a eli:LegalResourceSubdivision, GDPRtext:Point ; eli:description "The obligation laid down in paragraph 1 of this Article shall not apply to:"^^xsd:string ; eli:is_part_of gdpr:GDPR, gdpr:article27, gdpr:chapterIV, gdpr:chapterIV-1 ; eli:number "2"^^xsd:string ; eli:title_alternative "Article27(2)"^^xsd:string ; GDPRtext:hasSubPoint gdpr:article27-2-a, gdpr:article27-2-b ; GDPRtext:isPartOfArticle gdpr:article27 ; GDPRtext:isPartOfChapter gdpr:chapterIV ; GDPRtext:isPartOfSection gdpr:chapterIV-1 .

Consequences for data subjects
type: Class
subclass of: Purpose of new processing
involves: Data Subject
comment: The possible consequences of the change in processing for the data subject

Principle
type: Class
subclass of: Concept
comment: A Principle is a rule or standard defined by the GDPR which is essential to be followed for compliance

Privacy by Design
type: Class
subclass of: Controller Obligation
comment: Privacy by Design is the approach of taking privacy into consideration throughout the whole planning and execution processes.

Processing
type: Class
equivalent class: Use Data
subclass of: Activity
subclass of: Data Activity
involves: Personal Data
comment: Processing here refers to an Activity that acts on the Data Subject's personal information.

Processing affected or vulnerable individuals
type: Class
subclass of: Factors for Impact Assessment
subclass of: Processing
subclass of: Use Data
involves: Data Subject
involves: Personal Data
comment: This type of processing involves data subjects that are vulnerable, such as children, or people with disabilities.

Processing is unlawful
type: Class
subclass of: Right to restrict processing
involves: Personal Data
involves: Unlawful Processing
comment: The data subject can exercise the right to restrict processing of their personal data when the processing is unlawful

Processing sensitive data
type: Class
subclass of: Factors for Impact Assessment
subclass of: Processing
subclass of: Use Data
involves: Sensitive Personal Data
comment: This involves processing involving sensitive personal data.

Processing using untested technologies
type: Class
subclass of: Factors for Impact Assessment
subclass of: Processing
subclass of: Use Data
involves: Personal Data
comment: This type of processing uses technologies that are new or have not yet been deemed to be fit or stable for usage.

Processor
type: Class
subclass of: Entity
involves: Controller
comment: A natural or legal person, public authority, agency or other body which processes personal data on behalf of the controller.

Agreement between Processor and Controller
type: Class
subclass of: Concept
involves: Appointment of Processors
involves: Controller
involves: Processor
comment: Signifies the agreement between Controller and Processors for processing of personal data

Processor Obligations
type: Class
subclass of: Obligation
involves: Processor
comment: These are the obligations specified by the GDPR in the context of Processors

Processor Representative
type: Class
subclass of: Entity
involves: Processor
comment: A natural or legal person established in the Union who, designated by the processor in writing, represents the processor with regard to their respective obligations under the GDPR.

Propogate rights to Third Parties
type: Class
subclass of: Activity
subclass of: Controller Obligation
subclass of: Processor Obligations
involves: Controller
involves: Processor
involves: Data Subject's Rights
comment: To propogate a data subject's right once they have been exercised to other third parties that are involved through the data subject's personal data.

Protection against accidental loss
type: Class
subclass of: Security of Personal Data
involves: Data Security
involves: Personal Data
comment: Protection of data subject's personal data against accidental loss.

Protection against damage
type: Class
subclass of: Security of Personal Data
involves: Data Security
involves: Personal Data
comment: Protection of data subject's personal data against damage to the data.

Protection against destruction
type: Class
subclass of: Security of Personal Data
involves: Data Security
involves: Personal Data
comment: Protection of data subject's personal data against destruction of data.

Protection against unlawful processing
type: Class
subclass of: Security of Personal Data
involves: Data Security
involves: Personal Data
involves: Unlawful Processing
comment: Protection of data subject's personal data against unlawful processing of data.

Provide information for compliance
type: Class
subclass of: Processor Obligations
involves: Compliance
involves: Controller
comment: The processor must provide the controller with the information necessary to demonstrate compliance

Provide copy of Personal Data
type: Class
subclass of: Data Activity
subclass of: Right of Data Portability
involves: Personal Data
comment: The right of data portability requries providing a copy of the data subject's personal data

Pseudo-anonymous data
type: Class
subclass of: Data
involves: Data Subject
comment: Personal data that can no longer be attributed to a specific data subject without the use of additional information.

Public Interest
type: Class
subclass of: Lawful Basis
comment: Lawful basis is provided by the GDPR as being in the interest of the public

Principle of Purpose Limitation
type: Class
subclass of: Principle
involves: Archive Data
involves: Collection of Personal Data
involves: Explicit Purpose
involves: Historic, Statistical, or Scientific purposes
involves: Legitimate purpose
involves: Not further processed
involves: Personal Data
involves: Specified purpose
comment: The principle of purpose limitation states that personal data must be collected for specified, explicit and legitimate purposes and not further processed in a manner that is incompatible with those purposes; further processing for archiving purposes in the public interest, scientific or historical research purposes or statistical purposes shall, in accordance with Article 89(1) of the GDPR, not be considered to be incompatible with the initial purposes.

Purpose of new processing
type: Class
subclass of: Lawful Basis
involves: Processing
comment: These are the obligations over determining the new or changed purposes of processing

Regulation (EC) No 45/2001
type: Class
subclass of: Exlcusions and Exceptions
comment: Related to Regulation (EC) No. 45/2001

Personal or Household activity
type: Class
subclass of: Exlcusions and Exceptions
comment: Exempted as the GDPR does not apply to personal or household activity that does not have a professional or commercial activity associated with it.

Covered by Directive (EU) 2016/680
type: Class
subclass of: Exlcusions and Exceptions
comment: Exempted as it involves areas covered by Directive (EU) 2016/680

Racial origin data
type: Class
subclass of: Sensitive Personal Data
involves: Data Subject
comment: Personal data revealing racial or ethnic origin.

Regulation
type: Class
subclass of: LegalResourceSubdivision
comment: Regulation in GDPR text
example: gdpr:recital1 a eli:LegalResourceSubdivision, GDPRtext:Recital ; eli:description "The protection of natural persons in relation to the processing of personal data is a fundamental right. Article 8(1) of the Charter of Fundamental Rights of the European Union (the ‘Charter’) and Article 16(1) of the Treaty on the Functioning of the European Union (TFEU) provide that everyone has the right to the protection of personal data concerning him or her."^^xsd:string ; eli:is_part_of gdpr:GDPR ; eli:number "1"^^xsd:string .

Categories of data subjects and personal data
type: Class
subclass of: Maintain records for processing
involves: Data Subject
involves: Personal Data
comment: This obligation requires Controllers to record the categories of data subjects and the personal data involved in processing/activities.

Record categories of recipients
type: Class
subclass of: Maintain records for processing
involves: Share Personal Data with Third Party
comment: This obligation requires Controllers to record the categories of recipients the personal data was shared with.

Record cross-border transfers
type: Class
subclass of: Maintain records for processing
involves: Cross-border Transfer
comment: This obligation requires Controllers to record the cross-border data transfers.

Record data retention periods
type: Class
subclass of: Maintain records for processing
involves: Store Data
comment: This obligation requires Controllers to record the data retention period of personal data.

Record purpose of processing
type: Class
subclass of: Maintain records for processing
involves: Processing
comment: This obligation requires Controllers to record the purpose of processing associated with personal data and the given consent.

Record security measures
type: Class
subclass of: Maintain records for processing
involves: Security of Personal Data
comment: This obligation requires Controllers to record the measures taken to ensure adequate safety measures of personal data and the involved activities.

Rectify Data
type: Class
subclass of: Data Activity
involves: Personal Data
comment: An activity that rectifies data

Rectify Inaccuracies
type: Class
subclass of: Data Retention
involves: Personal Data
comment: Any inaccuracies or discrepancies in the retained data must be rectified

Regulatory Authority
type: Class
subclass of: Entity
comment: The authority responsible for regulating data protection laws.

Relevant for processing
type: Class
subclass of: Data Retention
involves: Personal Data
involves: Processing
comment: Any retained personal data must be relevant for subsiquent processing

Report Data Breach
type: Class
subclass of: Activity
subclass of: Compliance
subclass of: Controller Obligation
involves: Data Breach
involves: Maintain Record of Breach
involves: Notify Data Subject of Breach
involves: Report breach to DPA within 72 hours
comment: The act of reporting a data breach to entities mentioned within the GDPR. These are the Data Protection Authority (DPA), and in the case of Processors, the Controller they have an agreement with.

Report data breach to Controller
type: Class
subclass of: Processor Obligations
subclass of: Report Data Breach
involves: Controller
involves: Data Breach
involves: Processor
involves: Report Data Breach
comment: The occurence of a data breach must be reported to the Controller.

Report breach to DPA within 72 hours
type: Class
subclass of: Report Data Breach
involves: DPA
involves: Data Breach
comment: The occurence of a data breach must be reported to the Data Protection Authority (DPA) within 72 hours

Requires disproportionate efforts
type: Class
subclass of: Exlcusions and Exceptions
comment: The stated obligation or activity could not be completed as it requires disproportionate efforts to complete.

Written consent of Controller
type: Class
subclass of: Appointing Sub-Processors
involves: Consent
involves: Controller
involves: Sub-Processor
comment: Appointing a sub-processor requires the written consent of the controller specifying permission or consent

Restrictions on cross-border transfers
type: Class
subclass of: Processor Obligations
involves: Cross-border Transfer
involves: Processor
comment: These provide restrictions on cross-border transfers for Processors

Data Retention
type: Class
subclass of: Obligation
involves: Personal Data
involves: Store Data
comment: These are the obligations specified by the GDPR on the retention of personal data

Return or destroy data
type: Class
subclass of: Processor Obligations
involves: Erase Data
involves: Processor
involves: Agreement between Processor and Controller
comment: The processor must return or destroy personal data at the end of term (of its agreement with the controller)

Right of Data Portability
type: Class
subclass of: Data Subject's Rights
involves: Collection of Personal Data
involves: Data Subject
involves: Personal Data
involves: Provide copy of Personal Data
involves: Copy should be in a commonly used format
involves: Copy should be in a machine readable format
involves: Should be structured
involves: Shoud support reuse
comment: The data subject has the right to receive the personal data concerning him or her, which he or she has provided to a controller, in a structured, commonly used and machine-readable format and has the right to transmit those data to another controller without hindrance from the controller to which the personal data have been provided.

Right of Erasure
type: Class
subclass of: Data Subject's Rights
involves: Data Subject
involves: Erase Data
involves: Personal Data
comment: The data subject has the right to obtain erasure of their personal data

Right to Access Personal Data
type: Class
subclass of: Data Subject's Rights
involves: Data Subject
involves: Personal Data
involves: Processing
involves: Provide copy of Personal Data
comment: The data subject shall have the right to obtain from the controller confirmation as to whether or not personal data concerning him or her are being processed, and, where that is the case, access to the personal data along with additional information about it.

Right to basic information about processing of personal data
type: Class
subclass of: Data Subject's Rights
involves: Data Subject
involves: Processing
comment: The right to basic information about processing provides data subjects with information about the processing activities involving their personal data

Right to not be evaluated through automated processing
type: Class
subclass of: Data Subject's Rights
involves: Automated Processing
involves: Data Subject
comment: The data subject has a right to not be evaluated through automated processing

Right to object direct marketting
type: Class
subclass of: Data Subject's Rights
involves: Data Subject
involves: Direct Marketing
comment: The data subject has a right to object to direct marketting based on their personal data

Right to object processing
type: Class
subclass of: Data Subject's Rights
involves: Data Subject
involves: Personal Data
involves: Processing
comment: The data subject has the right to object to processing of their personal data

Right to rectify
type: Class
subclass of: Data Subject's Rights
involves: Data Subject
involves: Rectify Data
comment: The data subject has a right to recitify their personal data

Right to restrict processing
type: Class
subclass of: Data Subject's Rights
involves: Accuracy is contested
involves: Data no longer needed for original purpose
involves: Data Subject
involves: Processing
involves: Processing is unlawful
comment: The data subject has the rights to restrict the processing of their personal data

Right to Transparency
type: Class
subclass of: Data Subject's Rights
involves: Controller
involves: Data Subject
involves: Concise
involves: Easily Accessible
involves: Intelligible
involves: Transparent
involves: Principle of Lawfulness, Fairness, and Transparency
involves: Personal Data
involves: Processing
comment: The right to transparency requires controllers to provide information about the processing activities as well as personal data and its usage in a transparent manner

Data Subject's Rights
type: Class
subclass of: Concept
comment: The GDPR provides several rights to the data subjects which may be exercised at any time by the data subject and which are mandatory for the organisation to provide, comply with, and inform the data subject about.

Freedoms protection
type: Class
subclass of: Exlcusions and Exceptions
comment: The stated obligation could not be completed as it concerns freedoms protection.

Seal
type: Class
subclass of: Seals and Certifications
comment: A seal pertaining to GDPR compliance

Seals and Certifications
type: Class
subclass of: Concept
involves: Awarding Seals and Certifications
comment: GDPR provides for the creation and provision of seals and certificates pertaining to compliance or related activities

Section
type: Class
subclass of: LegalResourceSubdivision
comment: Section in GDPR text
example: gdpr:chapterIV-5 a eli:LegalResourceSubdivision, GDPRtext:Section ; eli:is_part_of gdpr:GDPR, gdpr:chapterIV ; eli:number "5"^^xsd:string ; eli:title "Codes of conduct and certification"^^xsd:string ; eli:title_alternative "Section 5"^^xsd:string ; GDPRtext:hasArticle gdpr:article40, gdpr:article41, gdpr:article42, gdpr:article43 ; GDPRtext:isPartOfChapter gdpr:chapterIV .

Security of Personal Data
type: Class
subclass of: Activity
subclass of: Obligation
involves: Data Security
involves: Personal Data
comment: This activity refers to security of data subject's personal data.

Sensitive Personal Data
type: Class
subclass of: Personal Data
involves: Data Subject
comment: Personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person's sex life or sexual orientation.

Share Personal Data with Third Party
type: Class
subclass of: Data Activity
involves: Controller
involves: Personal Data
involves: Processor
comment: This activity represents the sharing of data subject's personal data with a third party.

Copy should be in a commonly used format
type: Class
subclass of: Provide copy of Personal Data
comment: The provided copy of personal data should be in a commonly used format

Demonstrable
type: Class
subclass of: Obligation for obtaining consent
involves: Demonstrating Consent
involves: Given Consent
comment: Obtained consent should be in a demonstrable form

Distinguishable from other matters
type: Class
subclass of: Obligation for obtaining consent
involves: Given Consent
comment: Obtained consent should be distinguishable from other related matters (in the context of the process)

Copy should be in a machine readable format
type: Class
subclass of: Provide copy of Personal Data
comment: The provided copy of personal data should be machine readable

Should be structured
type: Class
subclass of: Provide copy of Personal Data
comment: The provided copy of personal data should be structured

Shoud support reuse
type: Class
subclass of: Provide copy of Personal Data
comment: The provided copy of personal data should support reuse

Specific
type: Class
subclass of: Valid Consent
involves: Given Consent
comment: GDPR obligation that specifies consent must be specific for it to be valid.

Specified purpose
type: Class
subclass of: Obligation for data collection
involves: Collection of Personal Data
involves: Processing
comment: This obligation states that the collection of personal data should happen only for the specified purposes (for which the data subject has consented).

Principle of Storage Limitation
type: Class
subclass of: Principle
involves: Archive Data
involves: Historic, Statistical, or Scientific purposes
involves: Identifiable for required processing
involves: Identification of Data Subject
involves: Personal Data
involves: Public Interest
involves: Store Data
comment: The principle of storage limitation states that personal data must be kept in a form which permits identification of data subjects for no longer than is necessary for the purposes for which the personal data are processed; personal data may be stored for longer periods insofar as the personal data will be processed solely for archiving purposes in the public interest, scientific or historical research purposes or statistical purposes in accordance with Article 89(1) of the GDPR subject to implementation of the appropriate technical and organisational measures required by this Regulation in order to safeguard the rights and freedoms of the data subject.

Store Data
type: Class
subclass of: Data Activity
involves: Personal Data
comment: An activity where personal data is being stored

SubPoint
type: Class
subclass of: LegalResourceSubdivision
comment: SubPoint in GDPR text
example: gdpr:article12-5-b a eli:LegalResourceSubdivision, GDPRtext:SubPoint ; eli:description "refuse to act on the request."^^xsd:string ; eli:is_part_of gdpr:GDPR, gdpr:article12, gdpr:article12-5, gdpr:chapterIII, gdpr:chapterIII-1 ; eli:number "b"^^xsd:string ; eli:title_alternative "Article12(5)(b)"^^xsd:string ; GDPRtext:isPartOfArticle gdpr:article12 ; GDPRtext:isPartOfChapter gdpr:chapterIII ; GDPRtext:isPartOfPoint gdpr:article12-5 ; GDPRtext:isPartOfSection gdpr:chapterIII-1 .

Sub-Processor
type: Class
subclass of: Processor
involves: Controller
involves: Processor
comment: A sub-processor is a processor acting under another processor.

Follow same terms
type: Class
subclass of: Appointing Sub-Processors
involves: Agreement between Processor and Controller
involves: Sub-Processor
comment: Sub-processors must follow the same rules and obligations (or terms) as the agreement between processor and controller.

Systematic Monitoring
type: Class
subclass of: Activity
subclass of: Factors for Impact Assessment
involves: Processing
comment: This activity provides a systematic monitoring or overview of processes/activities taking place within the context of the organisation.

Unlawful Processing
type: Class
subclass of: Processing
subclass of: Use Data
comment: Processing of personal data that is termed to be unlawful in the context of the GDPR or other relevant laws and regulations

Use Data
type: Class
subclass of: Data Activity
involves: Personal Data
comment: An activity that uses personal data

Valid Consent
type: Class
subclass of: Given Consent
subclass of: Obligation for obtaining consent
involves: Freely given
involves: Given Consent
involves: Informed
involves: Specific
comment: Consent is termed to be valid if it passes all the criteria or obligations laid down by the GDPR.

Vital Interests
type: Class
subclass of: Lawful Basis
involves: Data Subject
comment: These are obligations pertaining to the vital interests of the data subjects

Voluntary & Opt-in
type: Class
subclass of: Valid Consent
involves: Given Consent
comment: Consent must be obtained through the data subject's voluntary action and should be opt-in and not opt-out or by default.

Voluntary accredition
type: Class
subclass of: Awarding Seals and Certifications
comment: The seals and certifications should be a voluntary system of accredition

Withdrawing Given Consent
type: Class
subclass of: Consent Activity
involves: Data Subject
involves: Given Consent
comment: This activity represents the data subject withdrawing given consent.

Acquire Consent Activity
type: Class
subclass of: Consent Activity
disjoint with: Anonymised Data Entity
disjoint with: Appoint Processor
disjoint with: Consent Withdrawal Process
disjoint with: Data Access Process
disjoint with: Data Archival Process
disjoint with: Data Entity
disjoint with: Data Erasure Process
disjoint with: Data Rectification Process
disjoint with: Direct Marketing
disjoint with: Given Consent
disjoint with: Given Consent Template
disjoint with: HandleDataBreachProcess
disjoint with: Handle Right of Data Portability
disjoint with: Handle Right of Erasure
disjoint with: Handle Right to access Personal Data
disjoint with: Handle Right to basic information about Processing
disjoint with: Handle Right to not be evaluated through Automated Processing
disjoint with: Handle Right to Object to Direct Marketing
disjoint with: Handle Right to Object to Processing
disjoint with: Handle Right to Rectification
disjoint with: Handle Right to restrict Processing
disjoint with: Handle Right to Transparency
disjoint with: HandleSAR
disjoint with: Impact Assessment
disjoint with: Marketing
disjoint with: Monitor Compliance
disjoint with: Personal Data Entity
disjoint with: Process
disjoint with: Report Data Breach
disjoint with: Sensitive Data Entity
disjoint with: Terms and Conditions Entity
disjoint with: User Identifier Entity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: Is an activity that acquires consent.

Anonymisation Activity
type: Class
subclass of: Data Transformation Activity
disjoint with: Anonymised Data Entity
disjoint with: Appoint Processor
disjoint with: Consent Withdrawal Process
disjoint with: Data Access Process
disjoint with: Data Archival Process
disjoint with: Data Entity
disjoint with: Data Erasure Process
disjoint with: Data Rectification Process
disjoint with: Direct Marketing
disjoint with: Given Consent
disjoint with: Given Consent Template
disjoint with: HandleDataBreachProcess
disjoint with: Handle Right of Data Portability
disjoint with: Handle Right of Erasure
disjoint with: Handle Right to access Personal Data
disjoint with: Handle Right to basic information about Processing
disjoint with: Handle Right to not be evaluated through Automated Processing
disjoint with: Handle Right to Object to Direct Marketing
disjoint with: Handle Right to Object to Processing
disjoint with: Handle Right to Rectification
disjoint with: Handle Right to restrict Processing
disjoint with: Handle Right to Transparency
disjoint with: HandleSAR
disjoint with: Impact Assessment
disjoint with: Marketing
disjoint with: Monitor Compliance
disjoint with: Personal Data Entity
disjoint with: Process
disjoint with: Report Data Breach
disjoint with: Sensitive Data Entity
disjoint with: Terms and Conditions Entity
disjoint with: User Identifier Entity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: Is an activity that anonymises data.

AnonymisedData
type: Class
subclass of: PersonalData
subclass of: Restriction
  on property: hasAnonymityLevel
  some values from: AnonymityLevel
disjoint with: ConsentAgreement
disjoint with: ConsentAgreementTemplate
disjoint with: TermsAndConditions
comment: Represents data that has been Anonymised at some level reflected by the hasAnonymityLevel object property

Anonymised Data Entity
type: Class
subclass of: Personal Data Entity
disjoint with: An activity that archives given/acquired consent for storage.
disjoint with: Consent Activity
disjoint with: Cross Border Transfer Activity
disjoint with: Data Activity
disjoint with: Data Archival Activity
disjoint with: Data Breach Activity
disjoint with: Data Collection Activity
disjoint with: Data Deletion Activity
disjoint with: Data Sharing Activity
disjoint with: Data Storage Activity
disjoint with: DataTransferActivity
disjoint with: Data Transformation Activity
disjoint with: Data Usage Activity
disjoint with: DeAnonymisation Activity
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: Is an entity where personal data has been anonymised to some extent.

AnonymityLevel
type: Class
comment: Provides a way to express the Anonymity Level of AnonymisedData objects through the object property hasAnonymityLevel

Appoint Processor
type: Class
subclass of: Process
disjoint with: An activity that archives given/acquired consent for storage.
disjoint with: Consent Activity
disjoint with: Cross Border Transfer Activity
disjoint with: Data Activity
disjoint with: Data Archival Activity
disjoint with: Data Breach Activity
disjoint with: Data Collection Activity
disjoint with: Data Deletion Activity
disjoint with: Data Sharing Activity
disjoint with: Data Storage Activity
disjoint with: DataTransferActivity
disjoint with: Data Transformation Activity
disjoint with: Data Usage Activity
disjoint with: DeAnonymisation Activity
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: Reflects the process(es) used to appoint processors

An activity that archives given/acquired consent for storage.
type: Class
subclass of: Consent Activity
disjoint with: Consent Withdrawal Process
disjoint with: Data Access Process
disjoint with: Data Archival Process
disjoint with: Data Entity
disjoint with: Data Erasure Process
disjoint with: Data Rectification Process
disjoint with: Direct Marketing
disjoint with: Given Consent
disjoint with: Given Consent Template
disjoint with: HandleDataBreachProcess
disjoint with: Handle Right of Data Portability
disjoint with: Handle Right of Erasure
disjoint with: Handle Right to access Personal Data
disjoint with: Handle Right to basic information about Processing
disjoint with: Handle Right to not be evaluated through Automated Processing
disjoint with: Handle Right to Object to Direct Marketing
disjoint with: Handle Right to Object to Processing
disjoint with: Handle Right to Rectification
disjoint with: Handle Right to restrict Processing
disjoint with: Handle Right to Transparency
disjoint with: HandleSAR
disjoint with: Impact Assessment
disjoint with: Marketing
disjoint with: Monitor Compliance
disjoint with: Personal Data Entity
disjoint with: Process
disjoint with: Report Data Breach
disjoint with: Sensitive Data Entity
disjoint with: Terms and Conditions Entity
disjoint with: User Identifier Entity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
label: Archive Consent Activity

AutomatedStep
type: Class
subclass of: Step

Consent Acquisition Step
type: Class
subclass of: Consent Step
comment: ConsentAcquisitionStep deals with acquiring consent from the user. It uses Terms and Conditions along with the appropriate Consent Model as the basis of obtaining consent from the user. The output of this step is the consent object agreed upon by the user.

Consent Activity
type: Class
subclass of: Activity
disjoint with: Consent Withdrawal Process
disjoint with: Data Access Process
disjoint with: Data Archival Process
disjoint with: Data Entity
disjoint with: Data Erasure Process
disjoint with: Data Rectification Process
disjoint with: Direct Marketing
disjoint with: Given Consent
disjoint with: Given Consent Template
disjoint with: HandleDataBreachProcess
disjoint with: Handle Right of Data Portability
disjoint with: Handle Right of Erasure
disjoint with: Handle Right to access Personal Data
disjoint with: Handle Right to basic information about Processing
disjoint with: Handle Right to not be evaluated through Automated Processing
disjoint with: Handle Right to Object to Direct Marketing
disjoint with: Handle Right to Object to Processing
disjoint with: Handle Right to Rectification
disjoint with: Handle Right to restrict Processing
disjoint with: Handle Right to Transparency
disjoint with: HandleSAR
disjoint with: Impact Assessment
disjoint with: Marketing
disjoint with: Monitor Compliance
disjoint with: Personal Data Entity
disjoint with: Process
disjoint with: Report Data Breach
disjoint with: Sensitive Data Entity
disjoint with: Terms and Conditions Entity
disjoint with: User Identifier Entity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: Is an activity dealing with consent.

ConsentAgreement
type: Class
subclass of: Variable
disjoint with: ConsentAgreementTemplate
disjoint with: Data
disjoint with: PersonalData
disjoint with: Sensitive Personal Data
disjoint with: TermsAndConditions
disjoint with: UserIdentifier
comment: ConsentAgreement reflects the consent provided by the user based on the provided Terms and Conditions and Consent Agreement Templates. It is the set of permissions the user has specifically provided or refused to provide. This consent is useful to provide justification of activities that use user data.

ConsentAgreementTemplate
type: Class
subclass of: Variable
disjoint with: Data
disjoint with: PersonalData
disjoint with: Sensitive Personal Data
disjoint with: TermsAndConditions
disjoint with: UserIdentifier
comment: This is a template for consent requested from the user.

Consent Archival Step
type: Class
subclass of: Consent Step
comment: ConsentArchivalStep archives acquired consent to form a record of the consent given by the user.

Consent Modification Step
type: Class
subclass of: Consent Step
comment: ConsentModificationStep deals with modifications to the consent by the user. It invalidates the previous consent object and produces a new updated consent object that represents the modified consent.

Consent Step
type: Class
subclass of: Step
comment: A ConsentStep acts/interacts with/uses Consent

Consent Withdrawal Process
type: Class
subclass of: Process
disjoint with: Cross Border Transfer Activity
disjoint with: Data Activity
disjoint with: Data Archival Activity
disjoint with: Data Breach Activity
disjoint with: Data Collection Activity
disjoint with: Data Deletion Activity
disjoint with: Data Sharing Activity
disjoint with: Data Storage Activity
disjoint with: DataTransferActivity
disjoint with: Data Transformation Activity
disjoint with: Data Usage Activity
disjoint with: DeAnonymisation Activity
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: A ConsentWithdrawalProcess deals with the withdrawal of consent by the user and the corresponding activity carried out within the system

Consent Withdrawal Step
type: Class
subclass of: Consent Modification Step
comment: ConsentWithdrawalStep deals with withdrawal of consent

Controller
type: Class
subclass of: ThirdParty
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: A ThirdPartyDataController is a Third Party entity that acts as a Data Controller
label: Controller

Controller Representative
type: Class
subclass of: Agent
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: A Representative of the Controller

Cross-border Data Transfer
type: Class
subclass of: Data Step
comment: Reflects cross-border transfer of data

Cross Border Transfer Activity
type: Class
subclass of: Data Activity
disjoint with: Data Access Process
disjoint with: Data Archival Process
disjoint with: Data Entity
disjoint with: Data Erasure Process
disjoint with: Data Rectification Process
disjoint with: Direct Marketing
disjoint with: Given Consent
disjoint with: Given Consent Template
disjoint with: HandleDataBreachProcess
disjoint with: Handle Right of Data Portability
disjoint with: Handle Right of Erasure
disjoint with: Handle Right to access Personal Data
disjoint with: Handle Right to basic information about Processing
disjoint with: Handle Right to not be evaluated through Automated Processing
disjoint with: Handle Right to Object to Direct Marketing
disjoint with: Handle Right to Object to Processing
disjoint with: Handle Right to Rectification
disjoint with: Handle Right to restrict Processing
disjoint with: Handle Right to Transparency
disjoint with: HandleSAR
disjoint with: Impact Assessment
disjoint with: Marketing
disjoint with: Monitor Compliance
disjoint with: Personal Data Entity
disjoint with: Process
disjoint with: Report Data Breach
disjoint with: Sensitive Data Entity
disjoint with: Terms and Conditions Entity
disjoint with: User Identifier Entity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: Is an activity that transfer data across borders (as defined in the GDPR).

Data Protection Officer (DPO)
type: Class
subclass of: Agent
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: The Data Protection Officer appointed to an organisation.

Data
type: Class
subclass of: Variable
disjoint with: TermsAndConditions
comment: Represents class of data collected or generated through various activities

Data Access Process
type: Class
subclass of: Process
disjoint with: Data Activity
disjoint with: Data Archival Activity
disjoint with: Data Breach Activity
disjoint with: Data Collection Activity
disjoint with: Data Deletion Activity
disjoint with: Data Sharing Activity
disjoint with: Data Storage Activity
disjoint with: DataTransferActivity
disjoint with: Data Transformation Activity
disjoint with: Data Usage Activity
disjoint with: DeAnonymisation Activity
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: A DataAccessProcess corresponds to the request made by an user for access to their data within the system. This process is responsible for handling the request process and providing the appropriate data to the end user.

Data Activity
type: Class
subclass of: Activity
disjoint with: Data Archival Process
disjoint with: Data Entity
disjoint with: Data Erasure Process
disjoint with: Data Rectification Process
disjoint with: Direct Marketing
disjoint with: Given Consent
disjoint with: Given Consent Template
disjoint with: HandleDataBreachProcess
disjoint with: Handle Right of Data Portability
disjoint with: Handle Right of Erasure
disjoint with: Handle Right to access Personal Data
disjoint with: Handle Right to basic information about Processing
disjoint with: Handle Right to not be evaluated through Automated Processing
disjoint with: Handle Right to Object to Direct Marketing
disjoint with: Handle Right to Object to Processing
disjoint with: Handle Right to Rectification
disjoint with: Handle Right to restrict Processing
disjoint with: Handle Right to Transparency
disjoint with: HandleSAR
disjoint with: Impact Assessment
disjoint with: Marketing
disjoint with: Monitor Compliance
disjoint with: Personal Data Entity
disjoint with: Process
disjoint with: Report Data Breach
disjoint with: Sensitive Data Entity
disjoint with: Terms and Conditions Entity
disjoint with: User Identifier Entity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: Is an activity involving data.

Data Anonymisation Step
type: Class
subclass of: Data Transformation Step
comment: DataAnonymisationStep anonymises data by transforming it from one form to another along the anonymisation chain. Anonymisation can be represented as a spectrum going from raw user data to pseudo-anonymised data that can be de-anonymised by the same agent/organisation to pseudo-anonymous data that cannot be deanonymised internally, but may be done by external agents who have access to other data, and finally to completely anonymised data.

Data Archival Activity
type: Class
subclass of: Data Storage Activity
subclass of: Data Transformation Activity
disjoint with: Data Archival Process
disjoint with: Data Entity
disjoint with: Data Erasure Process
disjoint with: Data Rectification Process
disjoint with: Direct Marketing
disjoint with: Given Consent
disjoint with: Given Consent Template
disjoint with: HandleDataBreachProcess
disjoint with: Handle Right of Data Portability
disjoint with: Handle Right of Erasure
disjoint with: Handle Right to access Personal Data
disjoint with: Handle Right to basic information about Processing
disjoint with: Handle Right to not be evaluated through Automated Processing
disjoint with: Handle Right to Object to Direct Marketing
disjoint with: Handle Right to Object to Processing
disjoint with: Handle Right to Rectification
disjoint with: Handle Right to restrict Processing
disjoint with: Handle Right to Transparency
disjoint with: HandleSAR
disjoint with: Impact Assessment
disjoint with: Marketing
disjoint with: Monitor Compliance
disjoint with: Personal Data Entity
disjoint with: Process
disjoint with: Report Data Breach
disjoint with: Sensitive Data Entity
disjoint with: Terms and Conditions Entity
disjoint with: User Identifier Entity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: Is an activity that archives data. Archival is transformation of data into some form for storage.

Data Archival Process
type: Class
subclass of: Process
disjoint with: Data Breach Activity
disjoint with: Data Collection Activity
disjoint with: Data Deletion Activity
disjoint with: Data Sharing Activity
disjoint with: Data Storage Activity
disjoint with: DataTransferActivity
disjoint with: Data Transformation Activity
disjoint with: Data Usage Activity
disjoint with: DeAnonymisation Activity
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: A DataArchivalProcess describes the process of data archival

Data Archival Step
type: Class
subclass of: Data Storage Step
subclass of: Data Transformation Step
comment: DataArchivalStep archives data by transforming it and storing it

Data Breach Activity
type: Class
subclass of: Activity
disjoint with: Data Entity
disjoint with: Data Erasure Process
disjoint with: Data Rectification Process
disjoint with: Direct Marketing
disjoint with: Given Consent
disjoint with: Given Consent Template
disjoint with: HandleDataBreachProcess
disjoint with: Handle Right of Data Portability
disjoint with: Handle Right of Erasure
disjoint with: Handle Right to access Personal Data
disjoint with: Handle Right to basic information about Processing
disjoint with: Handle Right to not be evaluated through Automated Processing
disjoint with: Handle Right to Object to Direct Marketing
disjoint with: Handle Right to Object to Processing
disjoint with: Handle Right to Rectification
disjoint with: Handle Right to restrict Processing
disjoint with: Handle Right to Transparency
disjoint with: HandleSAR
disjoint with: Impact Assessment
disjoint with: Marketing
disjoint with: Monitor Compliance
disjoint with: Personal Data Entity
disjoint with: Process
disjoint with: Report Data Breach
disjoint with: Sensitive Data Entity
disjoint with: Terms and Conditions Entity
disjoint with: User Identifier Entity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: Is an activity dealing with data breach.

Data Breach Record
type: Class
subclass of: Variable
comment: A record of a data breach.

Data Breach Step
type: Class
subclass of: Step
comment: Step representing an action associated with data breach.

Data Collection Activity
type: Class
subclass of: Data Activity
disjoint with: Data Entity
disjoint with: Data Erasure Process
disjoint with: Data Rectification Process
disjoint with: Direct Marketing
disjoint with: Given Consent
disjoint with: Given Consent Template
disjoint with: HandleDataBreachProcess
disjoint with: Handle Right of Data Portability
disjoint with: Handle Right of Erasure
disjoint with: Handle Right to access Personal Data
disjoint with: Handle Right to basic information about Processing
disjoint with: Handle Right to not be evaluated through Automated Processing
disjoint with: Handle Right to Object to Direct Marketing
disjoint with: Handle Right to Object to Processing
disjoint with: Handle Right to Rectification
disjoint with: Handle Right to restrict Processing
disjoint with: Handle Right to Transparency
disjoint with: HandleSAR
disjoint with: Impact Assessment
disjoint with: Marketing
disjoint with: Monitor Compliance
disjoint with: Personal Data Entity
disjoint with: Process
disjoint with: Report Data Breach
disjoint with: Sensitive Data Entity
disjoint with: Terms and Conditions Entity
disjoint with: User Identifier Entity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: Is an activity that collects or acquires data.

Data Collection Step
type: Class
subclass of: Data Step
comment: DataCollectionStep collects data from the user

Data Deanonymisation Step
type: Class
subclass of: Data Transformation Step
comment: DataDeanonymisationStep deanonymises data by transforming it from one form to another along the anonymisation chain.

Data Deletion Activity
type: Class
subclass of: Data Activity
disjoint with: Data Entity
disjoint with: Data Erasure Process
disjoint with: Data Rectification Process
disjoint with: Direct Marketing
disjoint with: Given Consent
disjoint with: Given Consent Template
disjoint with: HandleDataBreachProcess
disjoint with: Handle Right of Data Portability
disjoint with: Handle Right of Erasure
disjoint with: Handle Right to access Personal Data
disjoint with: Handle Right to basic information about Processing
disjoint with: Handle Right to not be evaluated through Automated Processing
disjoint with: Handle Right to Object to Direct Marketing
disjoint with: Handle Right to Object to Processing
disjoint with: Handle Right to Rectification
disjoint with: Handle Right to restrict Processing
disjoint with: Handle Right to Transparency
disjoint with: HandleSAR
disjoint with: Impact Assessment
disjoint with: Marketing
disjoint with: Monitor Compliance
disjoint with: Personal Data Entity
disjoint with: Process
disjoint with: Report Data Breach
disjoint with: Sensitive Data Entity
disjoint with: Terms and Conditions Entity
disjoint with: User Identifier Entity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: Is an activity that deletes or erases data.

Data Deletion Step
type: Class
subclass of: Data Step
comment: DataDeletionStep deletes data from within the system; The deletion is expressed as prov:invalidated over the dataset.

Data Entity
type: Class
subclass of: Entity
disjoint with: Data Sharing Activity
disjoint with: Data Storage Activity
disjoint with: DataTransferActivity
disjoint with: Data Transformation Activity
disjoint with: Data Usage Activity
disjoint with: DeAnonymisation Activity
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: Represents a data entity.

Data Erasure Process
type: Class
subclass of: Process
disjoint with: Data Sharing Activity
disjoint with: Data Storage Activity
disjoint with: DataTransferActivity
disjoint with: Data Transformation Activity
disjoint with: Data Usage Activity
disjoint with: DeAnonymisation Activity
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: A DataErasureProcess is responsible for handling the data erasure of a data subject.

Data Rectification Process
type: Class
subclass of: Process
disjoint with: Data Sharing Activity
disjoint with: Data Storage Activity
disjoint with: DataTransferActivity
disjoint with: Data Transformation Activity
disjoint with: Data Usage Activity
disjoint with: DeAnonymisation Activity
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: A DataRectificationProcess describes the process of data rectification, which is the correction of data already present within the system

Data Sharing Activity
type: Class
subclass of: Data Activity
disjoint with: Direct Marketing
disjoint with: Given Consent
disjoint with: Given Consent Template
disjoint with: HandleDataBreachProcess
disjoint with: Handle Right of Data Portability
disjoint with: Handle Right of Erasure
disjoint with: Handle Right to access Personal Data
disjoint with: Handle Right to basic information about Processing
disjoint with: Handle Right to not be evaluated through Automated Processing
disjoint with: Handle Right to Object to Direct Marketing
disjoint with: Handle Right to Object to Processing
disjoint with: Handle Right to Rectification
disjoint with: Handle Right to restrict Processing
disjoint with: Handle Right to Transparency
disjoint with: HandleSAR
disjoint with: Impact Assessment
disjoint with: Marketing
disjoint with: Monitor Compliance
disjoint with: Personal Data Entity
disjoint with: Process
disjoint with: Report Data Breach
disjoint with: Sensitive Data Entity
disjoint with: Terms and Conditions Entity
disjoint with: User Identifier Entity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: Is an activity that shares data.

Data Sharing Step
type: Class
subclass of: Data Step
comment: DataSharingStep shares data with another agent/organisation. These may be internal or external entities.

Data Step
type: Class
subclass of: Step
comment: A DataStep deals with data

Data Storage Activity
type: Class
subclass of: Data Activity
disjoint with: Direct Marketing
disjoint with: Given Consent
disjoint with: Given Consent Template
disjoint with: HandleDataBreachProcess
disjoint with: Handle Right of Data Portability
disjoint with: Handle Right of Erasure
disjoint with: Handle Right to access Personal Data
disjoint with: Handle Right to basic information about Processing
disjoint with: Handle Right to not be evaluated through Automated Processing
disjoint with: Handle Right to Object to Direct Marketing
disjoint with: Handle Right to Object to Processing
disjoint with: Handle Right to Rectification
disjoint with: Handle Right to restrict Processing
disjoint with: Handle Right to Transparency
disjoint with: HandleSAR
disjoint with: Impact Assessment
disjoint with: Marketing
disjoint with: Monitor Compliance
disjoint with: Personal Data Entity
disjoint with: Process
disjoint with: Report Data Breach
disjoint with: Sensitive Data Entity
disjoint with: Terms and Conditions Entity
disjoint with: User Identifier Entity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: Is an activity that stores data.

Data Storage Step
type: Class
subclass of: Data Step
comment: DataStorageStep stores data within the system

Data Subject
type: Class
subclass of: Agent
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: An individual or entity

DataTransferStep
type: Class
subclass of: Data Step

Data Transformation Activity
type: Class
subclass of: Data Activity
disjoint with: Direct Marketing
disjoint with: Given Consent
disjoint with: Given Consent Template
disjoint with: HandleDataBreachProcess
disjoint with: Handle Right of Data Portability
disjoint with: Handle Right of Erasure
disjoint with: Handle Right to access Personal Data
disjoint with: Handle Right to basic information about Processing
disjoint with: Handle Right to not be evaluated through Automated Processing
disjoint with: Handle Right to Object to Direct Marketing
disjoint with: Handle Right to Object to Processing
disjoint with: Handle Right to Rectification
disjoint with: Handle Right to restrict Processing
disjoint with: Handle Right to Transparency
disjoint with: HandleSAR
disjoint with: Impact Assessment
disjoint with: Marketing
disjoint with: Monitor Compliance
disjoint with: Personal Data Entity
disjoint with: Process
disjoint with: Report Data Breach
disjoint with: Sensitive Data Entity
disjoint with: Terms and Conditions Entity
disjoint with: User Identifier Entity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: Is an activity that transforms data.

Data Transformation Step
type: Class
subclass of: Data Step
comment: DataTransformationStep transforms data from one form into another.

Data Usage Activity
type: Class
subclass of: Data Activity
disjoint with: Direct Marketing
disjoint with: Given Consent
disjoint with: Given Consent Template
disjoint with: HandleDataBreachProcess
disjoint with: Handle Right of Data Portability
disjoint with: Handle Right of Erasure
disjoint with: Handle Right to access Personal Data
disjoint with: Handle Right to basic information about Processing
disjoint with: Handle Right to not be evaluated through Automated Processing
disjoint with: Handle Right to Object to Direct Marketing
disjoint with: Handle Right to Object to Processing
disjoint with: Handle Right to Rectification
disjoint with: Handle Right to restrict Processing
disjoint with: Handle Right to Transparency
disjoint with: HandleSAR
disjoint with: Impact Assessment
disjoint with: Marketing
disjoint with: Monitor Compliance
disjoint with: Personal Data Entity
disjoint with: Process
disjoint with: Report Data Breach
disjoint with: Sensitive Data Entity
disjoint with: Terms and Conditions Entity
disjoint with: User Identifier Entity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: Is an activity that uses data. Can also be termed as 'Processing' of data.

Data Usage Step
type: Class
subclass of: Data Step
comment: A DataUsageStep is a DataStep that uses existing data present within the system

DeAnonymisation Activity
type: Class
subclass of: Data Transformation Activity
disjoint with: Direct Marketing
disjoint with: Given Consent
disjoint with: Given Consent Template
disjoint with: HandleDataBreachProcess
disjoint with: Handle Right of Data Portability
disjoint with: Handle Right of Erasure
disjoint with: Handle Right to access Personal Data
disjoint with: Handle Right to basic information about Processing
disjoint with: Handle Right to not be evaluated through Automated Processing
disjoint with: Handle Right to Object to Direct Marketing
disjoint with: Handle Right to Object to Processing
disjoint with: Handle Right to Rectification
disjoint with: Handle Right to restrict Processing
disjoint with: Handle Right to Transparency
disjoint with: HandleSAR
disjoint with: Impact Assessment
disjoint with: Marketing
disjoint with: Monitor Compliance
disjoint with: Personal Data Entity
disjoint with: Process
disjoint with: Report Data Breach
disjoint with: Sensitive Data Entity
disjoint with: Terms and Conditions Entity
disjoint with: User Identifier Entity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: Is an activity that deanonymises data.

Direct Marketing
type: Class
subclass of: Marketing
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: Direct Marketing where the marketing is done directly to the data subject.

Given Consent
type: Class
subclass of: Entity
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: Represents the given consent by the data subject.

Given Consent Template
type: Class
subclass of: Entity
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: Is the template used to obtain the given consent.

HandleDataBreachProcess
type: Class
subclass of: Process
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: A process that defines the actions that should be undertaken in event of a data breach

Handle Right of Data Portability
type: Class
subclass of: Process
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: The process or series of steps that handle the right of data portability.

Handle Right of Erasure
type: Class
subclass of: Process
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: The process or series of steps that handle the right of erasure.

Handle Right to access Personal Data
type: Class
subclass of: Process
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: The process or series of steps that handle the right to access personal data.

Handle Right to basic information about Processing
type: Class
subclass of: Process
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: The process or series of steps that handle the right to basic information about processing.

Handle Right to not be evaluated through Automated Processing
type: Class
subclass of: Process
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: The process or series of steps that handle the right to not be processed automatically.

Handle Right to Object to Direct Marketing
type: Class
subclass of: Process
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: The process or series of steps that handle the right to object to direct marketing.

Handle Right to Object to Processing
type: Class
subclass of: Process
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: The process or series of steps that handle the right to object to processing.

Handle Right to Rectification
type: Class
subclass of: Process
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: The process or series of steps that handle the right to rectification of personal data.

Handle Right to restrict Processing
type: Class
subclass of: Process
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: The process or series of steps that handle the right to restrict processing.

Handle Right to Transparency
type: Class
subclass of: Process
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: The process or series of steps that handle the right to transparency.

HandleSAR
type: Class
subclass of: Process
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage

Impact Assessment
type: Class
subclass of: Process
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: Impact Assessment for the organisation
comment: Represents the process or collection of steps representing the Impact Assessment.

Joint Controller(s)
type: Class
subclass of: Controller
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: A Joint Controller is where two or more controllers jointly determine the purposes and means of processing.

Marketing
type: Class
subclass of: Process
disjoint with: Modify Consent Activity
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: Marketing as a process or collection of steps.

Modify Consent Activity
type: Class
subclass of: Consent Activity
disjoint with: Monitor Compliance
disjoint with: Personal Data Entity
disjoint with: Process
disjoint with: Report Data Breach
disjoint with: Sensitive Data Entity
disjoint with: Terms and Conditions Entity
disjoint with: User Identifier Entity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: Is an activity that modifies given consent.

Monitor Compliance
type: Class
subclass of: Process
disjoint with: Notify Controller Activity
disjoint with: Notify DPA Activity
disjoint with: Notify Data Subject Activity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: The process of monitoring compliance as mandated by the GDPR.

Notify Controller
type: Class
subclass of: Data Breach Step
comment: Step that notifies the controller of data breach.

Notify Controller Activity
type: Class
subclass of: Data Breach Activity
disjoint with: Personal Data Entity
disjoint with: Process
disjoint with: Report Data Breach
disjoint with: Sensitive Data Entity
disjoint with: Terms and Conditions Entity
disjoint with: User Identifier Entity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: Is an activity that notifies controller about data breach

Notify Data Protection Authority
type: Class
subclass of: Data Breach Step
comment: Step that notifies the Data Protection Authorities of a data breach.

Notify DPA Activity
type: Class
subclass of: Data Breach Activity
disjoint with: Personal Data Entity
disjoint with: Process
disjoint with: Report Data Breach
disjoint with: Sensitive Data Entity
disjoint with: Terms and Conditions Entity
disjoint with: User Identifier Entity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: Is an activity that notifies data protection authorities about data breach

Notify Data Subject
type: Class
subclass of: Data Breach Step
comment: Step that notifies the data subject of data breach.

Notify Data Subject Activity
type: Class
subclass of: Data Breach Activity
disjoint with: Personal Data Entity
disjoint with: Process
disjoint with: Report Data Breach
disjoint with: Sensitive Data Entity
disjoint with: Terms and Conditions Entity
disjoint with: User Identifier Entity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: Is an activity that notifies data subjects about data breach

PersonalData
type: Class
subclass of: Data
disjoint with: TermsAndConditions
comment: PersonalData is any data pertaining to the user which can contain personally identifiable information or a data set generated by the system using personally identifiable information acquired through direct or indirect means

Personal Data Entity
type: Class
subclass of: Data Entity
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: Represents a personal data entity.

Process
type: Class
subclass of: Plan
disjoint with: Rectify Data Activity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: A Process describes a 'Plan' of action for carrying out a particular activity that uses or is related to Data or Consent

Processor
type: Class
subclass of: ThirdParty
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: A ThirdPartyDataProcessor is a Third Party entity that acts as a Data Processor
label: Processor

Processor Representative
type: Class
subclass of: Agent
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: A representative of the Processor.

Provide copy of Personal Data
type: Class
subclass of: Data Step
comment: A step that provides the data subject with a copy of their personal data.

Rectify Data
type: Class
subclass of: Data Step
comment: Rectifies existing data
label: Rectify Data

Rectify Data Activity
type: Class
subclass of: Data Activity
disjoint with: Report Data Breach
disjoint with: Sensitive Data Entity
disjoint with: Terms and Conditions Entity
disjoint with: User Identifier Entity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: Is an activity that recitifies data.

Report Data Breach
type: Class
subclass of: HandleDataBreachProcess
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: The process of reporting after a data breach has taken place.

Sensitive Personal Data
type: Class
subclass of: PersonalData
disjoint with: TermsAndConditions
comment: Personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person's sex life or sexual orientation.

Sensitive Data Entity
type: Class
subclass of: Personal Data Entity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: Is an entity containing sensitive personal information.

Sub-Processor
type: Class
subclass of: Processor
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: A Processor appointed under or by another Processor is a Sub-Processor.

TermsAndConditions
type: Class
subclass of: Variable
disjoint with: UserIdentifier
comment: Terms and Conditions of usage as provided to the user in agreement of provided service

Terms and Conditions Entity
type: Class
subclass of: Entity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: Represents the Terms and Conditions entity.

ThirdParty
type: Class
subclass of: Agent
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: A ThirdParty is any external entitiy associated with some internal activity

UserIdentifier
type: Class
subclass of: PersonalData
comment: An UserIdentifier is a specific way to identify the user through a unique ID or a combination of other attributes

User Identifier Entity
type: Class
subclass of: Personal Data Entity
disjoint with: Withdraw Consent Activity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: Is an entity acting as the user identifier. Or contains an identifier.

Withdraw Consent Activity
type: Class
subclass of: Modify Consent Activity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: Is an activity that withdraws given consent. Can also term it so as to depict withdrawal as a modification of consent.

Activity
type: Class
subclass of: Activity
disjoint with: Bundle
disjoint with: Entity
disjoint with: MultiStep
disjoint with: Plan
disjoint with: Collection
disjoint with: EmptyCollection
comment: A p-plan:Activity represents the execution process planned in a p-plan:Step

Bundle
type: Class
subclass of: Entity
subclass of: Bundle
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
definition: A p-plan:Bundle is a specific type of prov:Bundle that contains the provenance assertions of the execution of a p-plan:Plan

Entity
type: Class
subclass of: Entity
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
definition: A p-plan:Entity represents the input of the execution of a p-plan:Activity. It corresponds to a p-plan:Variable.

MultiStep
type: Class
subclass of: Plan
subclass of: Step
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
definition: A multi step is the representation of a plan that appears as a step of another plan.

Plan
type: Class
subclass of: Entity
subclass of: Plan
disjoint with: Activity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
definition: A p-plan:Plan is a specific type of prov:Plan. It is composed of smaller steps that use and produce Variables.

Step
type: Class
definition: A p-plan:Step represents the planned execution activity

Variable
type: Class
definition: A p-plan:Variable represents a description of the input of the planned Activity (p-plan:Step)

Activity
type: Class
disjoint with: Bundle
disjoint with: Collection
disjoint with: EmptyCollection
disjoint with: Entity
disjoint with: Plan
category: starting-point
component: entities-activities
constraints: http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig
definition: An activity is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Activity
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Activity

ActivityInfluence
type: Class
subclass of: Influence
subclass of: Restriction
  on property: hadActivity
  max cardinality: 0
disjoint with: Derivation
disjoint with: End
disjoint with: EntityInfluence
disjoint with: PrimarySource
disjoint with: Quotation
disjoint with: Revision
disjoint with: Start
disjoint with: Usage
comment: ActivityInfluence provides additional descriptions of an Activity's binary influence upon any other kind of resource. Instances of ActivityInfluence use the prov:activity property to cite the influencing Activity.
comment: It is not recommended that the type ActivityInfluence be asserted without also asserting one of its more specific subclasses.
category: qualified
editors definition: ActivitiyInfluence is the capacity of an activity to have an effect on the character, development, or behavior of another by means of generation, invalidation, communication, or other.

Agent
type: Class
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
category: starting-point
component: agents-responsibility
definition: An agent is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-agent
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Agent

AgentInfluence
type: Class
subclass of: Influence
comment: AgentInfluence provides additional descriptions of an Agent's binary influence upon any other kind of resource. Instances of AgentInfluence use the prov:agent property to cite the influencing Agent.
comment: It is not recommended that the type AgentInfluence be asserted without also asserting one of its more specific subclasses.
category: qualified
editors definition: AgentInfluence is the capacity of an agent to have an effect on the character, development, or behavior of another by means of attribution, association, delegation, or other.

Association
type: Class
subclass of: AgentInfluence
comment: An instance of prov:Association provides additional descriptions about the binary prov:wasAssociatedWith relation from an prov:Activity to some prov:Agent that had some responsiblity for it. For example, :baking prov:wasAssociatedWith :baker; prov:qualifiedAssociation [ a prov:Association; prov:agent :baker; :foo :bar ].
category: qualified
component: agents-responsibility
definition: An activity association is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Association
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Association
unqualified form: wasAssociatedWith

Attribution
type: Class
subclass of: AgentInfluence
comment: An instance of prov:Attribution provides additional descriptions about the binary prov:wasAttributedTo relation from an prov:Entity to some prov:Agent that had some responsible for it. For example, :cake prov:wasAttributedTo :baker; prov:qualifiedAttribution [ a prov:Attribution; prov:entity :baker; :foo :bar ].
category: qualified
component: agents-responsibility
constraints: http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig
definition: Attribution is the ascribing of an entity to an agent. When an entity e is attributed to agent ag, entity e was generated by some unspecified activity that in turn was associated to agent ag. Thus, this relation is useful when the activity is not known, or irrelevant.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribution
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-attribution
unqualified form: wasAttributedTo

Bundle
type: Class
subclass of: Entity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
comment: Note that there are kinds of bundles (e.g. handwritten letters, audio recordings, etc.) that are not expressed in PROV-O, but can be still be described by PROV-O.
category: expanded
definition: A bundle is a named set of provenance descriptions, and is itself an Entity, so allowing provenance of provenance to be expressed.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-bundle-entity
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-bundle-declaration

Collection
type: Class
subclass of: Entity
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
category: expanded
component: collections
definition: A collection is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be member of the collections.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-collection

Communication
type: Class
subclass of: ActivityInfluence
disjoint with: Derivation
disjoint with: End
disjoint with: EntityInfluence
disjoint with: PrimarySource
disjoint with: Quotation
disjoint with: Revision
disjoint with: Start
disjoint with: Usage
comment: An instance of prov:Communication provides additional descriptions about the binary prov:wasInformedBy relation from an informed prov:Activity to the prov:Activity that informed it. For example, :you_jumping_off_bridge prov:wasInformedBy :everyone_else_jumping_off_bridge; prov:qualifiedCommunication [ a prov:Communication; prov:activity :everyone_else_jumping_off_bridge; :foo :bar ].
category: qualified
component: entities-activities
constraints: http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig
definition: Communication is the exchange of an entity by two activities, one activity using the entity generated by the other.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Communication
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-wasInformedBy
unqualified form: wasInformedBy

Delegation
type: Class
subclass of: AgentInfluence
comment: An instance of prov:Delegation provides additional descriptions about the binary prov:actedOnBehalfOf relation from a performing prov:Agent to some prov:Agent for whom it was performed. For example, :mixing prov:wasAssociatedWith :toddler . :toddler prov:actedOnBehalfOf :mother; prov:qualifiedDelegation [ a prov:Delegation; prov:entity :mother; :foo :bar ].
category: qualified
component: agents-responsibility
definition: Delegation is the assignment of authority and responsibility to an agent (by itself or by another agent) to carry out a specific activity as a delegate or representative, while the agent it acts on behalf of retains some responsibility for the outcome of the delegated work. For example, a student acted on behalf of his supervisor, who acted on behalf of the department chair, who acted on behalf of the university; all those agents are responsible in some way for the activity that took place but we do not say explicitly who bears responsibility and to what degree.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-delegation
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-delegation
unqualified form: actedOnBehalfOf

Derivation
type: Class
subclass of: EntityInfluence
disjoint with: Generation
disjoint with: Invalidation
comment: An instance of prov:Derivation provides additional descriptions about the binary prov:wasDerivedFrom relation from some derived prov:Entity to another prov:Entity from which it was derived. For example, :chewed_bubble_gum prov:wasDerivedFrom :unwrapped_bubble_gum; prov:qualifiedDerivation [ a prov:Derivation; prov:entity :unwrapped_bubble_gum; :foo :bar ].
comment: The more specific forms of prov:Derivation (i.e., prov:Revision, prov:Quotation, prov:PrimarySource) should be asserted if they apply.
category: qualified
component: derivations
constraints: http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig
definition: A derivation is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-existing entity.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Derivation
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#Derivation-Relation
unqualified form: wasDerivedFrom

EmptyCollection
type: Class
subclass of: Collection
disjoint with: End
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
category: expanded
component: collections
definition: An empty collection is a collection without members.

End
type: Class
subclass of: EntityInfluence
subclass of: InstantaneousEvent
disjoint with: Entity
disjoint with: Generation
disjoint with: Invalidation
disjoint with: Organization
disjoint with: Person
disjoint with: Plan
disjoint with: SoftwareAgent
comment: An instance of prov:End provides additional descriptions about the binary prov:wasEndedBy relation from some ended prov:Activity to an prov:Entity that ended it. For example, :ball_game prov:wasEndedBy :buzzer; prov:qualifiedEnd [ a prov:End; prov:entity :buzzer; :foo :bar; prov:atTime '2012-03-09T08:05:08-05:00'^^xsd:dateTime ].
category: qualified
component: entities-activities
constraints: http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig
definition: End is when an activity is deemed to have been ended by an entity, known as trigger. The activity no longer exists after its end. Any usage, generation, or invalidation involving an activity precedes the activity's end. An end may refer to a trigger entity that terminated the activity, or to an activity, known as ender that generated the trigger.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-End
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-End
unqualified form: wasEndedBy

Entity
type: Class
disjoint with: Generation
disjoint with: InstantaneousEvent
disjoint with: Invalidation
disjoint with: Start
disjoint with: Usage
category: starting-point
component: entities-activities
constraints: http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig
definition: An entity is a physical, digital, conceptual, or other kind of thing with some fixed aspects; entities may be real or imaginary.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-entity
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Entity

EntityInfluence
type: Class
subclass of: Influence
disjoint with: Generation
disjoint with: Invalidation
comment: EntityInfluence provides additional descriptions of an Entity's binary influence upon any other kind of resource. Instances of EntityInfluence use the prov:entity property to cite the influencing Entity.
comment: It is not recommended that the type EntityInfluence be asserted without also asserting one of its more specific subclasses.
category: qualified
editors definition: EntityInfluence is the capacity of an entity to have an effect on the character, development, or behavior of another by means of usage, start, end, derivation, or other.

Generation
type: Class
subclass of: ActivityInfluence
subclass of: InstantaneousEvent
disjoint with: Organization
disjoint with: Person
disjoint with: Plan
disjoint with: PrimarySource
disjoint with: Quotation
disjoint with: Revision
disjoint with: SoftwareAgent
disjoint with: Start
disjoint with: Usage
comment: An instance of prov:Generation provides additional descriptions about the binary prov:wasGeneratedBy relation from a generated prov:Entity to the prov:Activity that generated it. For example, :cake prov:wasGeneratedBy :baking; prov:qualifiedGeneration [ a prov:Generation; prov:activity :baking; :foo :bar ].
category: qualified
component: entities-activities
constraints: http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig
definition: Generation is the completion of production of a new entity by an activity. This entity did not exist before generation and becomes available for usage after this generation.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Generation
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Generation
unqualified form: wasGeneratedBy

Influence
type: Class
comment: An instance of prov:Influence provides additional descriptions about the binary prov:wasInfluencedBy relation from some influenced Activity, Entity, or Agent to the influencing Activity, Entity, or Agent. For example, :stomach_ache prov:wasInfluencedBy :spoon; prov:qualifiedInfluence [ a prov:Influence; prov:entity :spoon; :foo :bar ] . Because prov:Influence is a broad relation, the more specific relations (Communication, Delegation, End, etc.) should be used when applicable.
comment: Because prov:Influence is a broad relation, its most specific subclasses (e.g. prov:Communication, prov:Delegation, prov:End, prov:Revision, etc.) should be used when applicable.
category: qualified
component: derivations
definition: Influence is the capacity of an entity, activity, or agent to have an effect on the character, development, or behavior of another by means of usage, start, end, generation, invalidation, communication, derivation, attribution, association, or delegation.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-influence
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-influence
unqualified form: wasInfluencedBy

InstantaneousEvent
type: Class
disjoint with: Organization
disjoint with: Person
disjoint with: Plan
disjoint with: SoftwareAgent
comment: An instantaneous event, or event for short, happens in the world and marks a change in the world, in its activities and in its entities. The term 'event' is commonly used in process algebra with a similar meaning. Events represent communications or interactions; they are assumed to be atomic and instantaneous.
category: qualified
component: entities-activities
constraints: http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#dfn-event
definition: The PROV data model is implicitly based on a notion of instantaneous events (or just events), that mark transitions in the world. Events include generation, usage, or invalidation of entities, as well as starting or ending of activities. This notion of event is not first-class in the data model, but it is useful for explaining its other concepts and its semantics.

Invalidation
type: Class
subclass of: ActivityInfluence
subclass of: InstantaneousEvent
disjoint with: Organization
disjoint with: Person
disjoint with: Plan
disjoint with: PrimarySource
disjoint with: Quotation
disjoint with: Revision
disjoint with: SoftwareAgent
disjoint with: Start
disjoint with: Usage
comment: An instance of prov:Invalidation provides additional descriptions about the binary prov:wasInvalidatedBy relation from an invalidated prov:Entity to the prov:Activity that invalidated it. For example, :uncracked_egg prov:wasInvalidatedBy :baking; prov:qualifiedInvalidation [ a prov:Invalidation; prov:activity :baking; :foo :bar ].
category: qualified
component: entities-activities
constraints: http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig
definition: Invalidation is the start of the destruction, cessation, or expiry of an existing entity by an activity. The entity is no longer available for use (or further invalidation) after invalidation. Any generation or usage of an entity precedes its invalidation.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Invalidation
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Invalidation
unqualified form: wasInvalidatedBy

Location
type: Class
category: expanded
definition: A location can be an identifiable geographic place (ISO 19112), but it can also be a non-geographic place such as a directory, row, or column. As such, there are numerous ways in which location can be expressed, such as by a coordinate, address, landmark, and so forth.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute-location
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-attribute

Organization
type: Class
subclass of: Agent
disjoint with: Start
disjoint with: Usage
category: expanded
component: agents-responsibility
definition: An organization is a social or legal institution such as a company, society, etc.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-agent
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-types

Person
type: Class
subclass of: Agent
disjoint with: Start
disjoint with: Usage
category: expanded
component: agents-responsibility
definition: Person agents are people.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-agent
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-types

Plan
type: Class
subclass of: Entity
disjoint with: Start
disjoint with: Usage
comment: There exist no prescriptive requirement on the nature of plans, their representation, the actions or steps they consist of, or their intended goals. Since plans may evolve over time, it may become necessary to track their provenance, so plans themselves are entities. Representing the plan explicitly in the provenance can be useful for various tasks: for example, to validate the execution as represented in the provenance record, to manage expectation failures, or to provide explanations.
category: expanded
category: qualified
component: agents-responsibility
definition: A plan is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Association
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Association

PrimarySource
type: Class
subclass of: Derivation
comment: An instance of prov:PrimarySource provides additional descriptions about the binary prov:hadPrimarySource relation from some secondary prov:Entity to an earlier, primary prov:Entity. For example, :blog prov:hadPrimarySource :newsArticle; prov:qualifiedPrimarySource [ a prov:PrimarySource; prov:entity :newsArticle; :foo :bar ] .
category: qualified
component: derivations
definition: A primary source for a topic refers to something produced by some agent with direct experience and knowledge about the topic, at the time of the topic's study, without benefit from hindsight. Because of the directness of primary sources, they 'speak for themselves' in ways that cannot be captured through the filter of secondary sources. As such, it is important for secondary sources to reference those primary sources from which they were derived, so that their reliability can be investigated. A primary source relation is a particular case of derivation of secondary materials from their primary sources. It is recognized that the determination of primary sources can be up to interpretation, and should be done according to conventions accepted within the application's domain.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-primary-source
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-original-source
unqualified form: hadPrimarySource

Quotation
type: Class
subclass of: Derivation
comment: An instance of prov:Quotation provides additional descriptions about the binary prov:wasQuotedFrom relation from some taken prov:Entity from an earlier, larger prov:Entity. For example, :here_is_looking_at_you_kid prov:wasQuotedFrom :casablanca_script; prov:qualifiedQuotation [ a prov:Quotation; prov:entity :casablanca_script; :foo :bar ].
category: qualified
component: derivations
definition: A quotation is the repeat of (some or all of) an entity, such as text or image, by someone who may or may not be its original author. Quotation is a particular case of derivation.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-quotation
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-quotation
unqualified form: wasQuotedFrom

Revision
type: Class
subclass of: Derivation
comment: An instance of prov:Revision provides additional descriptions about the binary prov:wasRevisionOf relation from some newer prov:Entity to an earlier prov:Entity. For example, :draft_2 prov:wasRevisionOf :draft_1; prov:qualifiedRevision [ a prov:Revision; prov:entity :draft_1; :foo :bar ].
category: qualified
component: derivations
definition: A revision is a derivation for which the resulting entity is a revised version of some original. The implication here is that the resulting entity contains substantial content from the original. Revision is a particular case of derivation.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-revision
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Revision
unqualified form: wasRevisionOf

Role
type: Class
category: qualified
component: agents-responsibility
definition: A role is the function of an entity or agent with respect to an activity, in the context of a usage, generation, invalidation, association, start, and end.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute-role
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-attribute

SoftwareAgent
type: Class
subclass of: Agent
disjoint with: Start
disjoint with: Usage
category: expanded
component: agents-responsibility
definition: A software agent is running software.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-agent
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-types

Start
type: Class
subclass of: EntityInfluence
subclass of: InstantaneousEvent
comment: An instance of prov:Start provides additional descriptions about the binary prov:wasStartedBy relation from some started prov:Activity to an prov:Entity that started it. For example, :foot_race prov:wasStartedBy :bang; prov:qualifiedStart [ a prov:Start; prov:entity :bang; :foo :bar; prov:atTime '2012-03-09T08:05:08-05:00'^^xsd:dateTime ] .
category: qualified
component: entities-activities
constraints: http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig
definition: Start is when an activity is deemed to have been started by an entity, known as trigger. The activity did not exist before its start. Any usage, generation, or invalidation involving an activity follows the activity's start. A start may refer to a trigger entity that set off the activity, or to an activity, known as starter, that generated the trigger.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Start
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Start
unqualified form: wasStartedBy

Usage
type: Class
subclass of: EntityInfluence
subclass of: InstantaneousEvent
comment: An instance of prov:Usage provides additional descriptions about the binary prov:used relation from some prov:Activity to an prov:Entity that it used. For example, :keynote prov:used :podium; prov:qualifiedUsage [ a prov:Usage; prov:entity :podium; :foo :bar ].
category: qualified
component: entities-activities
constraints: http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig
definition: Usage is the beginning of utilizing an entity by an activity. Before usage, the activity had not begun to utilize this entity and could not have been affected by the entity.
dm: http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Usage
n: http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Usage
unqualified form: used

Ads Generation Process
type: NamedIndividual
type: Process
type: Entity
type: Plan
hasLegalBasis: Given Consent
comment: A process to generate Ads to be shown along with the Product

Ads
type: NamedIndividual
type: Data
type: Variable
isDataGeneratedByStep: Request Ads from Provider
isOutputVarOf: Request Ads from Provider
comment: Ads shown along with a product

Ads Provider
type: NamedIndividual
type: Processor
type: ThirdParty
type: Agent
comment: Third Party that provides Ads based on given information

Anonymise user data (for removal)
type: NamedIndividual
type: Data Anonymisation Step
type: Data Step
type: Data Transformation Step
type: Step
generatesAnonymisedData: User Profile (Anonymised)
generatesData: User Profile (Anonymised)
isPartOfProcess: Remove user's account
usesData: Customer Address
usesData: Customer Bank Account
usesData: Customer Card Details
usesData: Customer Contact Number
usesData: Customer Email
usesData: Customer Name
hasInputVar: Customer Address
hasInputVar: Customer Bank Account
hasInputVar: Customer Card Details
hasInputVar: Customer Contact Number
hasInputVar: Customer Email
hasInputVar: Customer Name
hasOutputVar: User Profile (Anonymised)
isPrecededBy: Archive consent (for removal)
isStepOfPlan: Remove user's account
comment: A user's personal data that has been anonymised before deletion

User Profile (Anonymised)
type: NamedIndividual
type: AnonymisedData
type: Data
type: PersonalData
type: Variable
isAnonymisedByStep: Anonymise user data (for removal)
isDataGeneratedByStep: Anonymise user data (for removal)
isOutputVarOf: Anonymise user data (for removal)
comment: A User Profile where all personal information has been either removed or anonymised

Archive consent (for removal)
type: NamedIndividual
type: Consent Archival Step
type: Consent Step
type: Step
archives consent as: Consent (Archived)
isPartOfProcess: Remove user's account
uses Consent Agreement: Consent from New User
hasInputVar: Consent from New User
hasOutputVar: Consent (Archived)
isStepOfPlan: Remove user's account
comment: Archived copy of given consent preserved (before deletion) for compliance purposes

Consent (Archived)
type: NamedIndividual
type: ConsentAgreement
type: Variable
isOutputVarOf: Archive consent (for removal)
comment: Archived copy of consent

Backup Servers
type: Thing
type: NamedIndividual
location: Ireland
comment: Backup Servers hosting data and situated in Ireland

Consent Withdrawal Step
type: NamedIndividual
type: Consent Modification Step
type: Consent Step
type: Step
generatesConsentAgreement: Consent (modified)
uses Consent Agreement: Stored Consent
hasInputVar: Stored Consent
hasOutputVar: Consent (modified)
comment: This step withdraws consent (User's Given Consent)

Personal Data (copy)
type: NamedIndividual
type: Data
type: PersonalData
type: Variable
isDataGeneratedByStep: Provide a copy of user's personal data
isOutputVarOf: Provide a copy of user's personal data
format: https://www.iana.org/assignments/media-types/application/json
comment: This is a copy of (all of) the user's personal data.

Customer Address
type: NamedIndividual
type: Customer Info
type: Data
type: PersonalData
type: Variable
isDataCollectedByStep: Get Details for New User
isUsedByStep: Anonymise user data (for removal)
isUsedByStep: Order Product
isUsedByStep: Provide a copy of user's personal data
isUsedByStep: Provide user's data as part of SAR
isUsedByStep: Store new user's details
isInputVarOf: Anonymise user data (for removal)
isInputVarOf: Order Product
isInputVarOf: Provide a copy of user's personal data
isInputVarOf: Provide user's data as part of SAR
isInputVarOf: Store new user's details
isOutputVarOf: Get Details for New User
comment: The address of the customer

Customer Bank Account
type: NamedIndividual
type: Banking Info
type: Data
type: PersonalData
type: Sensitive Personal Data
type: Variable
isDataCollectedByStep: Order Product
isUsedByStep: Anonymise user data (for removal)
isUsedByStep: Order Product
isUsedByStep: Provide a copy of user's personal data
isUsedByStep: Provide user's data as part of SAR
isInputVarOf: Anonymise user data (for removal)
isInputVarOf: Order Product
isInputVarOf: Provide a copy of user's personal data
isInputVarOf: Provide user's data as part of SAR
isOutputVarOf: Order Product
comment: The Bank Account or Transaction details of Customer

Customer Card Details
type: NamedIndividual
type: Banking Info
type: Data
type: PersonalData
type: Sensitive Personal Data
type: Variable
isDataCollectedByStep: Order Product
isUsedByStep: Anonymise user data (for removal)
isUsedByStep: Order Product
isUsedByStep: Provide a copy of user's personal data
isUsedByStep: Provide user's data as part of SAR
isInputVarOf: Anonymise user data (for removal)
isInputVarOf: Order Product
isInputVarOf: Provide a copy of user's personal data
isInputVarOf: Provide user's data as part of SAR
isOutputVarOf: Order Product
comment: Payment information such as Card details for Customer

Customer Contact Number
type: NamedIndividual
type: Customer Info
type: Data
type: PersonalData
type: Variable
isDataCollectedByStep: Get Details for New User
isUsedByStep: Anonymise user data (for removal)
isUsedByStep: Order Product
isUsedByStep: Provide a copy of user's personal data
isUsedByStep: Provide user's data as part of SAR
isUsedByStep: Store new user's details
isInputVarOf: Anonymise user data (for removal)
isInputVarOf: Order Product
isInputVarOf: Provide a copy of user's personal data
isInputVarOf: Provide user's data as part of SAR
isInputVarOf: Store new user's details
isOutputVarOf: Get Details for New User
comment: Customer's contact information, such as telephone number

Customer Email
type: NamedIndividual
type: Customer Info
type: Data
type: PersonalData
type: Variable
isDataCollectedByStep: Get Details for New User
isUsedByStep: Anonymise user data (for removal)
isUsedByStep: Order Product
isUsedByStep: Provide a copy of user's personal data
isUsedByStep: Provide user's data as part of SAR
isUsedByStep: Store new user's details
isInputVarOf: Anonymise user data (for removal)
isInputVarOf: Order Product
isInputVarOf: Provide a copy of user's personal data
isInputVarOf: Provide user's data as part of SAR
isInputVarOf: Store new user's details
isOutputVarOf: Get Details for New User
comment: Customer's contact information, such as email

Customer Name
type: NamedIndividual
type: Customer Info
type: Data
type: PersonalData
type: Variable
isDataCollectedByStep: Get Details for New User
isUsedByStep: Anonymise user data (for removal)
isUsedByStep: Order Product
isUsedByStep: Provide a copy of user's personal data
isUsedByStep: Provide user's data as part of SAR
isUsedByStep: Store new user's details
isInputVarOf: Anonymise user data (for removal)
isInputVarOf: Order Product
isInputVarOf: Provide a copy of user's personal data
isInputVarOf: Provide user's data as part of SAR
isInputVarOf: Store new user's details
isOutputVarOf: Get Details for New User
comment: Name of Customer

Delete User Account Data
type: NamedIndividual
type: Data Activity
type: Data Deletion Activity
type: Data Deletion Step
type: Data Step
type: Activity
type: Step
invalidates data: Customer Address
invalidates data: Customer Bank Account
invalidates data: Customer Card Details
invalidates data: Customer Contact Number
invalidates data: Customer Email
invalidates data: Customer Name
isPartOfProcess: Remove user's account
isPrecededBy: Anonymise user data (for removal)
isPrecededBy: Archive consent (for removal)
isStepOfPlan: Remove user's account
comment: This step deletes user (customer records) data

Erase (selected) Data
type: NamedIndividual
type: Data Deletion Step
type: Data Step
type: Step
isPartOfProcess: Handle Right of Erasure
isStepOfPlan: Handle Right of Erasure
comment: This step deletes (partially) some of the user's data. It allows the user to select which data should be deleted.

Gather required information for Impact Assessment
type: NamedIndividual
type: AutomatedStep
type: Step
isPartOfProcess: Impact Assessment
isStepOfPlan: Impact Assessment
refers to process: Ads Generation Process
refers to process: Sign up process for New Users
refers to process: Ordering Products
refers to process: Remove user's account
comment: This step gathers information required for an Impact Assessment within the framework of the system model. It is a pre-cursor for the Impact Assessment step.

Generate Impact Assessment Report
type: NamedIndividual
type: Data Step
type: Step
generatesData: Impact Assessment Report
isPartOfProcess: Impact Assessment
hasOutputVar: Impact Assessment Report
isPrecededBy: Gather required information for Impact Assessment
isStepOfPlan: Impact Assessment
comment: This step generates the Impact Assessment report

Get Consent for New User
type: NamedIndividual
type: Consent Acquisition Step
type: Consent Step
type: UserInputStep
type: UserInteractionStep
type: Step
collects consent from agent: User
generatesConsentAgreement: Consent from New User
involves agent: User
isPartOfProcess: Sign up process for New Users
usesConsentAgreementTemplate: Sign up form for New Users
usesTermsAndConditions: Terms and Conditions
hasInputVar: Sign up form for New Users
hasInputVar: Terms and Conditions
hasOutputVar: Consent from New User
isStepOfPlan: Sign up process for New Users
hasLegalBasis: Legal Obligations
comment: This step is responsible for retrieving the (new) user's consent.

Get Details for New User
type: NamedIndividual
type: Data Collection Step
type: Data Step
type: UserInputStep
type: UserInteractionStep
type: Step
collectsData: Customer Address
collectsData: Customer Contact Number
collectsData: Customer Email
collectsData: Customer Name
collects data from agent: User
involves agent: User
isPartOfProcess: Sign up process for New Users
hasOutputVar: Customer Address
hasOutputVar: Customer Contact Number
hasOutputVar: Customer Email
hasOutputVar: Customer Name
isPrecededBy: Get Consent for New User
isStepOfPlan: Sign up process for New Users
hasLegalBasis: Legitimate Interests
comment: This step is responsible for gathering the (new) user's details required for operation of services

Handle Data Breach
type: NamedIndividual
type: HandleDataBreachProcess
type: Process
type: Entity
type: Plan
comment: This process outlines the set of actions to be carried out in the event of a data breach

Handle Right to Data Portability
type: NamedIndividual
type: Handle Right of Data Portability
type: Process
type: Entity
type: Plan
comment: This process is responsible for handling the Right to Data Portability

Handle Right of Erasure
type: NamedIndividual
type: Process
type: Entity
type: Plan
comment: This process is responsible for handling the Right of Erasure

Handle Right to Object to Processing
type: NamedIndividual
type: Process
type: Entity
type: Plan
comment: This process is responsible for handling the Right to Object to Processing

Handle Right to Rectification
type: NamedIndividual
type: Process
type: Entity
type: Plan
comment: This process is responsible for handling the Right to Rectification

Handle Subject Access Requests
type: NamedIndividual
type: HandleSAR
type: Process
type: Entity
type: Plan
comment: This process is responsible for handling Subject Access Requests

Impact Assessment
type: NamedIndividual
type: Process
type: Entity
type: Plan
comment: This process undertakes the Impact Assessment for the current state of the system (model)

Impact Assessment Report
type: NamedIndividual
type: Data
type: Variable
isDataGeneratedByStep: Generate Impact Assessment Report
isOutputVarOf: Generate Impact Assessment Report
comment: This is the Impact Assessment Report, produced as the outcome of the Impact Assessment Process

Invoice (Order)
type: NamedIndividual
type: Data
type: Variable
isDataGeneratedByStep: Order Product
isOutputVarOf: Order Product
comment: This is an Invoice shown/presented to the user upon ordering a product

Marketing
type: NamedIndividual
type: Process
type: Entity
type: Plan

Consent (modified)
type: NamedIndividual
type: ConsentAgreement
type: Variable
isGeneratedByStep: Consent Withdrawal Step
isOutputVarOf: Consent Withdrawal Step

Consent from New User
type: NamedIndividual
type: ConsentAgreement
type: Variable
isGeneratedByStep: Get Consent for New User
isInputVarOf: Archive consent (for removal)
isInputVarOf: Store new user's consent
isOutputVarOf: Get Consent for New User

Sign up form for New Users
type: NamedIndividual
type: ConsentAgreementTemplate
type: Variable
isConsentAgreementTemplateForStep: Get Consent for New User
isInputVarOf: Get Consent for New User

Sign up process for New Users
type: NamedIndividual
type: Process
type: Entity
type: Plan

Notify Data Breach to Users
type: NamedIndividual
type: Data Breach Step
type: Notify Data Subject
type: Step
isPartOfProcess: Report Data Breach
isStepOfPlan: Report Data Breach

Notify Data Breach to Supervisory Authorities
type: NamedIndividual
type: Data Breach Step
type: Notify Data Protection Authority
type: Step
isPartOfProcess: Report Data Breach
isStepOfPlan: Report Data Breach

Ordering Products
type: NamedIndividual
type: Process
type: Entity
type: Plan

Order Product
type: NamedIndividual
type: Data Collection Step
type: Data Step
type: Data Usage Step
type: UserInputStep
type: UserInteractionStep
type: Step
collectsData: Customer Bank Account
collectsData: Customer Card Details
collectsData: Product
collects data from agent: User
generatesData: Invoice (Order)
involves agent: User
isPartOfProcess: Ordering Products
usesData: Customer Address
usesData: Customer Bank Account
usesData: Customer Card Details
usesData: Customer Contact Number
usesData: Customer Email
usesData: Customer Name
hasInputVar: Customer Address
hasInputVar: Customer Bank Account
hasInputVar: Customer Card Details
hasInputVar: Customer Contact Number
hasInputVar: Customer Email
hasInputVar: Customer Name
hasOutputVar: Customer Bank Account
hasOutputVar: Customer Card Details
hasOutputVar: Invoice (Order)
hasOutputVar: Product
isStepOfPlan: Ordering Products
hasLegalBasis: Legitimate Interests

Product
type: NamedIndividual
type: Data
type: Variable
isDataCollectedByStep: Order Product
isOutputVarOf: Order Product

Provide a copy of user's personal data
type: NamedIndividual
type: Data Step
type: Provide copy of Personal Data
type: UserInteractionStep
type: UserOutputStep
type: Step
generatesData: Personal Data (copy)
isPartOfProcess: Handle Right to Data Portability
usesData: Customer Address
usesData: Customer Bank Account
usesData: Customer Card Details
usesData: Customer Contact Number
usesData: Customer Email
usesData: Customer Name
hasInputVar: Customer Address
hasInputVar: Customer Bank Account
hasInputVar: Customer Card Details
hasInputVar: Customer Contact Number
hasInputVar: Customer Email
hasInputVar: Customer Name
hasOutputVar: Personal Data (copy)
isStepOfPlan: Handle Right to Data Portability

Rectify specified user data
type: NamedIndividual
type: Data Step
type: Rectify Data
type: UserInputStep
type: UserInteractionStep
type: Step
isPartOfProcess: Handle Right to Rectification
isStepOfPlan: Handle Right to Rectification

Remove user's account
type: NamedIndividual
type: Process
type: Entity
type: Plan

Report Data Breach
type: NamedIndividual
type: HandleDataBreachProcess
type: Process
type: Entity
type: Plan
type: Step
isPartOfProcess: Handle Data Breach
isStepOfPlan: Handle Data Breach

Request Ads from Provider
type: NamedIndividual
type: AutomatedStep
type: Data Sharing Step
type: Data Step
type: Step
generatesData: Ads
isPartOfProcess: Ads Generation Process
hasOutputVar: Ads
isStepOfPlan: Ads Generation Process
hasLegalBasis: Given Consent
sharesData: Customer Address
sharesData: Customer Contact Number
sharesData: Customer Email
sharesData: Customer Name
sharesDataWith: Ads Provider

Provide user's data as part of SAR
type: NamedIndividual
type: Data Step
type: Data Usage Step
type: UserInteractionStep
type: UserOutputStep
type: Step
isPartOfProcess: Handle Subject Access Requests
usesData: Customer Address
usesData: Customer Bank Account
usesData: Customer Card Details
usesData: Customer Contact Number
usesData: Customer Email
usesData: Customer Name
hasInputVar: Customer Address
hasInputVar: Customer Bank Account
hasInputVar: Customer Card Details
hasInputVar: Customer Contact Number
hasInputVar: Customer Email
hasInputVar: Customer Name
isStepOfPlan: Handle Subject Access Requests
refers to process: Ads Generation Process
refers to process: Marketing
refers to process: Ordering Products

Store new user's details
type: NamedIndividual
type: Data Step
type: Data Storage Step
type: Step
isPartOfProcess: Sign up process for New Users
usesData: Customer Address
usesData: Customer Contact Number
usesData: Customer Email
usesData: Customer Name
hasInputVar: Customer Address
hasInputVar: Customer Contact Number
hasInputVar: Customer Email
hasInputVar: Customer Name
isPrecededBy: Get Consent for New User
isPrecededBy: Get Details for New User
isStepOfPlan: Sign up process for New Users
hasLegalBasis: Given Consent

Store new user's consent
type: NamedIndividual
type: Consent Archival Step
type: Consent Step
type: Step
archives consent as: Stored Consent
isPartOfProcess: Sign up process for New Users
uses Consent Agreement: Consent from New User
hasInputVar: Consent from New User
hasOutputVar: Stored Consent
isPrecededBy: Get Consent for New User
isStepOfPlan: Sign up process for New Users
hasLegalBasis: Legal Obligations

Stored Consent
type: NamedIndividual
type: ConsentAgreement
type: Given Consent
type: Entity
type: Variable
isInputVarOf: Consent Withdrawal Step
isOutputVarOf: Store new user's consent

Terms and Conditions
type: NamedIndividual
type: TermsAndConditions
type: Variable
isTermsAndConditionsForStep: Get Consent for New User
isInputVarOf: Get Consent for New User

Transfer data to backup servers
type: NamedIndividual
type: AutomatedStep
type: Data Step
type: DataTransferStep
type: Step
transfersDataToRegion: Backup Servers

User
type: NamedIndividual
type: Service User
type: Data Subject
type: Agent

Get data to be erased
type: NamedIndividual
type: UserInputStep
type: UserInteractionStep
type: Step
isPartOfProcess: Handle Right of Erasure
isStepOfPlan: Handle Right of Erasure

Get processes to be halted
type: NamedIndividual
type: UserInputStep
type: UserInteractionStep
type: Step
isPartOfProcess: Handle Right to Object to Processing
isStepOfPlan: Handle Right to Object to Processing

comment: TEST
comment: TEST2

comment: TEST
comment: TEST2

comment: An ontology for representing provenance traces pertainining to GDPR compliance. It uses concepts from GDPRtEXT along with extending PROV and P-Plan.

Anonymised
comment: Anonymised represents the Anonymisation level where the data cannot be de-anonymised to retrieve personally identifiable information.

DeAnonymised
comment: DeAnonymised represents the Anonymisation level where the data is completely de-anonymised and contains directly accessible personally identifiable information.

PseudoAnonymised
comment: PseudoAnonymised represents the Anonymisation level where the data is anonymised but cannot be de-anonymised without additional data which is NOT accessible to the data-holding organisation to retrieve personally identifiable information.

PseudoOrganisationalOrganised
comment: PseudoOrganisationalAnonymised represents the Anonymisation level where the data is anonymised but cannot be de-anonymised without additional data which is accessible to the data-holding organisation to recreate the de-anonymised information.

order
comment: The position that this OWL term should be listed within documentation. The scope of the documentation (e.g., among all terms, among terms within a prov:category, among properties applying to a particular class, etc.) is unspecified.