Seppe Vansteelant: Why is GivenConsent a specialisation of Consent? Isn't this a attribute?

[michaelgeamanu]

No description provided.

[GeertThijs]

• Apparantly GivenConsent is the only status of Consent that can justify the Processing of the PersonalData in some case of PersonalDataHandling. All the other statusses (Expired, Invalidated, Refused, Requested etc) make Processing invalid. So that's why it was modelled as a seperate class by GConsent and consequently bij OSLO Consent. It is slightly more efficient than having to follow the Consent.consentStatus relation to check if the Consent is given.
• However, only this one status is hardwired in the model. They can also be reached via the Consent.status attribute. This is also provided in GConsent and in a similar manner in DPV (where GivenConsent is indeed one of the possible values of the status attribute, it is not a class). Main difference with DPV is that there Consent is subtyped according to wether the Consent is Informed or Uninformed and if Informed wether it is Expressed or Implied. In GConsent al this is mixed in one enumeration.

[GeertThijs]

REMARK: see issue #45 for more info on ConsentStatus in general.