The General Data Protection Regulations (GDPR) imposes greater restrictions on obtaining valid user consents involving the use of personal data. A semantic model of consent can make the concepts of consent explicit, estab- lish a common understanding and enable re-use of consent. Therefore, forming a semantic model of consent will satisfy the GDPR requirements of specificity and unambiguity and is an important step towards ensuring compliance. In this paper, we discuss obtaining an open vocabulary of expressing consent leverag- ing existing semantic models of provenance, processes, permission and obliga- tions. We also present a reference architecture for the management of data pro- cessing according to consent permission. This data management model utilizes the open vocabulary of consent and incorporates the change of context into the data processing activity. By identifying and incorporating changes to the rela- tional context between data controllers and data subjects into the data pro- cessing model, it aims to improve the integration of data management across different information systems specifically adhering to the GDPR and helping controllers to demonstrate compliance.
The consent ontology presents a way to define and describe consent in terms relevant to the GDPR.
'action' is used to identify what action is permitted by the consent.
'action' defines what action is permitted by the consent.
This term 'activity' is used to define what to do when some 'event' occures related to consent. For example, when the consent expires (event), then re-solicit consent (activity) or when the consent is revoked (event) then stop processing (activity).
'Activity' defines what activiy is required to do when an event occures due to Consent Obligation has an event and an activity. When that even occures that activity is required to be executed by the 'Consent Obligation'
'aggregated analysis' is a subtype of 'purpose'. It means the data are allowed for analysis and the analysis can aggregated data from other sources as well.
'Allowed party' is used to indicate who the party (person or organisation) is that is allowed (or denied )to perform certain action on the particular data by this consent.
'Allowed party' defines the party (person or organisation) that is allowed (or denied )to perform certain action on the particular data by this consent.
It identifies if the consent is taken in the form of mobile application.
It defines if the consent is taken in the form of mobile application.
It is used to identify if the consent is taken in the form of audio.
It identifies if the consent is taken in the form of audio.
'audio data' defines the format of data is audio.
'business type' indicates the type of business the data is permitted to share by this consent.
'business type' defines with what type of business the data is permitted to share by this consent.
'category' identifies the category of data such as personal data (sensitive or non sensitive) / non personal data etc.
'category' defines the category of data on which this consent applies.
'collect' indicates the action to collect data. This is used to identify if data collection is allowed by the consent's permission.
'collect' defines the action to collect data.
'condition' is used to mention if there is any condition based on which the permission mentioned in the consent will be applicable. In other words the permission mentioned in the consent is applicable only when the conditions are met.
'condition' defines based on what condition the permission is applicable.
consent of the data subject means any freely given, specific, informed and unambiguous indication of the data subject's wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her;
It is used to record at what format the consent was obtained.
'consent format' defines the format was used to obtain the consent.
Obligations are the actions to be performated when an event occures. 'consent obligation' defines the obligation related to consent, i.e. it defines what action to perform when an event related to consent occures. For example, when the consent expires (event), then re-solicit consent (activity) or when the consent is revoked (event) then stop processing (activity).
'consenting party' is the person who is giving the consent.
Context is used to keep track of the contextual information while giving, modifying or revoking consent.
It defines at what context the consent was given.
'data' identifies to what data this consent is applicable.
'data' defines what data is premitted by this consent.
'data format' identifies the format data for which this consent is applicable.
'data format' defines the format of data for which this consent is applicable.
'data subject' is the person who is identified by the personal data or the data is about that person.
'data subject's representative' is the person who is consenting on behalf of the data subject.
'denied action' indicates the action that is denied by the consent.
'denied action' defines what action is denied by the consent.
'email marketing' is a subtype of purpose 'marketing.'
'event' defines the event based on which an activity is required to do. Consent Obligation has an event and an activity. When that even occures that activity is required to be executed by the 'Consent Obligation'
'for profit' defines the business type of the organisation with whom the data is permitted to share is for profit.
'genetic data' is a subtype of 'personal data'.
'genetic data' identifies the of 'category' of data applicable by this consent is genetic data.
'granting context' says at what context the consent was given.
'granting context' defines at what context the consent was given.
'health data' identifies the of 'category' of data applicable by this consent is health data.
'health data' is a subtype of 'personal data'.
'information exchanged' says what information was provided while the consent was given.
'information exchanged' is used to note the information that was provided while the consent was given.
'legal representative of data subject' is the person who is legally consenting on behalf of the data subject.
'location' says where the consent is given.
'location' defines the context of where the consent is given.
'phone marketing' is a subtype of purpose 'marketing.'
'marketing by post' is a subtype of purpose marketing.
'marketing by text' is a subtype of purpose marketing.
'mixed format data' indicates if the data being consented has a mixed format i.e. the data comtains various format. An example of mixed format data can be a combination of both audio and text format of data.
'mixed format data' defines if the data being consented has a mixed format. mixed format data combines the data of various format.
'modification context' is used to indicate at what context the consent is modified.
'modification context' defines at what context the consent is modified.
'non personal data' is a subtype of 'category' of data.
'non personal data' identifies that the of 'category' of data applicable by this consent is not personal data.
'non profit' defines the business type of the organisation with whom the data is permitted to share is non profit.
It identifies if the consent is taken in the form of an online form.
It identifies if the consent is taken as an online opt-in option.
'organisation' identifies the organisation with whom the data is permitted to share.
'organisation's location' identifies the location of the organisation that is permitted by the consent.
'organisation's name' identifies the name of the organisation that is permitted by the consent.
It identifies if the consent is taken on paper.
'parent of data subject' is the person who is the parent of data subject and consenting on behalf of the data subject where the data subject is a child.
'permission' is used to identify the authorisation granted by the consent.
'permission' defines the authorisation granted by the consent.
'permitted action' indicates the action that is allowed by the consent.
'permitted action' defines the action that is allowed by the consent.
'personal data' is a subtype of 'category' of data.
'personal data' identifies the of 'category' of data applicable by this consent is personal data.
'picture data' defines the format of data is image.
'purpose' indicates for what purpose the action is allowed by the consent on the data
'revoking context' is used to indicate at what context the consent is revoked.
'revoking context' defines at what context the consent is revoked.
'scientific purpose' is a subtype of purpose.
'share with' identifies who is allowed to share the data with by the consent.
'share with' defines with whom the consent permits to share data.
'singe format data' indicates if the data being consented has a single format. An example of mixed format data can be a combination of data of either audio and text format of data, not a combination of these.
'single format data' defines if the data being consented has a single format.
'solo analysis' is a subtype of 'purpose'. It means the data are allowed for analysis from this single source only, it can not be agreegate with data from other sources.
'store' indicates the action to store data. This is used to identify if data storage is allowed by the consent's permission.
'store' defines the action to store data.
'text data' defines the format of data is text.
'time' defines the context of when the consent is given.
'use' indicates the action to use data. This is used to identify if data use is allowed by the consent's permission.
'validity time' defines the validity time of consent. The consent is valid only within this validity time.
It identifies if the consent is taken in the form of video.
'video data' defines the format of data is video.