You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Security reporting requires strict and clear information i.e. to be explicit in cases where something is or isn't applicable. Due to the open world assumption of semantic web, where if information is not specified then it can mean it is not applicable or not available or something else - this ambiguity is problematic for cases such as data breach reporting. To assist with this, we should add special instances in DPV to assist with explicitly indicating information and to address the ambiguity arising from "open world" assumptions.
These following concepts can be used anywhere:
Applicability as the parent concept representing an indication of where the information is applicable or (not) available. If the information is available, it should be used directly and this concept will not apply.
dpv:UnknownApplicability - indicating information is unknown i.e. it is not known if the information exists or is applicable and therefore statements about its availability cannot be made (yet)
dpv:NotApplicable - instance indicating context is not applicable
dpv:NotAvailable - instance indicating the information is applicable but is not yet available
For example, given a relation hasImpactAssessment representing a field for impact assessments in a reporting form, the values would mean the following:
UnknownApplicability: unknown whether an impact assessment is needed or exists, which means a process should identify which of the below two concepts apply
NotApplicable: impact assessment is not needed
NotAvailable: impact assessment is needed but is not available yet, which means a process should complete or retrieve the assessment
The text was updated successfully, but these errors were encountered:
Security reporting requires strict and clear information i.e. to be explicit in cases where something is or isn't applicable. Due to the open world assumption of semantic web, where if information is not specified then it can mean it is not applicable or not available or something else - this ambiguity is problematic for cases such as data breach reporting. To assist with this, we should add special instances in DPV to assist with explicitly indicating information and to address the ambiguity arising from "open world" assumptions.
These following concepts can be used anywhere:
Applicability
as the parent concept representing an indication of where the information is applicable or (not) available. If the information is available, it should be used directly and this concept will not apply.dpv:UnknownApplicability
- indicating information is unknown i.e. it is not known if the information exists or is applicable and therefore statements about its availability cannot be made (yet)dpv:NotApplicable
- instance indicating context is not applicabledpv:NotAvailable
- instance indicating the information is applicable but is not yet availableFor example, given a relation
hasImpactAssessment
representing a field for impact assessments in a reporting form, the values would mean the following:UnknownApplicability
: unknown whether an impact assessment is needed or exists, which means a process should identify which of the below two concepts applyNotApplicable
: impact assessment is not neededNotAvailable
: impact assessment is needed but is not available yet, which means a process should complete or retrieve the assessmentThe text was updated successfully, but these errors were encountered: