Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add information availability concepts #102

Closed
coolharsh55 opened this issue Aug 2, 2023 · 3 comments
Closed

Add information availability concepts #102

coolharsh55 opened this issue Aug 2, 2023 · 3 comments
Milestone

Comments

@coolharsh55
Copy link
Collaborator

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:

  1. 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.
  2. 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)
  3. dpv:NotApplicable - instance indicating context is not applicable
  4. 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
@coolharsh55 coolharsh55 added this to the DPV v1.1 milestone Aug 2, 2023
@ghurlbot
Copy link

Comment by @coolharsh55 via IRC channel #dpvcg on irc.w3.org

These concepts were discussed in today's meeting, and will be accepted.

@ghurlbot
Copy link

Comment by @coolharsh55 via IRC channel #dpvcg on irc.w3.org

concepts have been accepted in today's meeting

@coolharsh55 coolharsh55 modified the milestones: DPV v1.1, dpv v2 Apr 13, 2024
@coolharsh55
Copy link
Collaborator Author

Added concepts to context-status, review and close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants