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.

Sign up for GitHub

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

Jump to bottom

[Concept]: Add Fee concept to DPV, remove it from RISK #185

Open
coolharsh55 opened this issue Aug 28, 2024 · 2 comments
Open

[Concept]: Add Fee concept to DPV, remove it from RISK #185

coolharsh55 opened this issue Aug 28, 2024 · 2 comments
Labels
eu-gdpr risk WIP
Milestone
dpv v2.1

Comments

@coolharsh55
Copy link
Collaborator

Specs

DPV, RISK

New Concept(s)

Move concept Fee from RISK to DPV.

Changed Concept(s)

No response
@coolharsh55 coolharsh55 added this to the dpv v2.1 milestone Aug 28, 2024
coolharsh55 added a commit that referenced this issue Aug 30, 2024
@coolharsh55
DPV: adds contract types and legal basis statuses
f4f8831 
- #111 adds contract types, statuses, clause types, fulfilment status,
  and controls to DPV legal basis (but as separate modules)
- #111 adds status types for other legal bases - legitimate interest,
  legal obligation, official authority, public and vital interests
- The documentation for these concepts is NOT included in this concept
  and should be implemented after agreement on the concept structuring
- #185 adds Fee concept as `FeeRequired` in DPV. The concept is to be
  removed from the RISK extension (not implemented in this commit)
@coolharsh55
Copy link
Collaborator Author

Added FeeRequirement with FeeRequired and FeeNotRequired as concepts for representing fees. The amount and conditions of the fee should be expressed as annotations or relations over instances of FeeRequired. Live version: https://dev.dpvcg.org/2.1-dev/dpv/#vocab-context-duration-frequency (this is in duration, but it will get its own subsection later)

TODO: Accompanying HTML documentation with examples of how to use these concepts.

@coolharsh55
Copy link
Collaborator Author

In meeting SEP-10 the group accepted the proposed concepts for modelling fees in DPV as described above.

@coolharsh55 coolharsh55 moved this to In progress in dpv 2.1 planning Sep 18, 2024
coolharsh55 added a commit that referenced this issue Oct 1, 2024
@coolharsh55
adds consolidated RISK taxonomy #181
361bf21 
- creates a new structuring/organisation of RISK taxonomy related to
  risk sources, risks, consequences, and impacts where each concept can
  take on different roles depending on the use-case
- to express this, each concept is created as an instance of new
  concepts e.g. `PotentialRiskSource` or `PotentialImpact`
- the concepts are now provided in a module `risk_taxonomy` instead of
  `risk_consequences` (which has been deleted)
- the HTML documentation provides new sections for each of the
  `Potential...` concept along with an overview table for roles
- the HTML documentation does NOT provide description of the new model
  or examples, this is TODO
- this work is with thanks to discussions with @DelaramGlp and Rob
  Brennan
- #182 added bias concepts
- #185 removed risk:Fee as it has been added to DPV as dpv:FeeRequirement
- #190 added discrimination concepts
- #184 added rights impact concepts in RISK
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
eu-gdpr risk WIP
Projects
None yet
Milestone
dpv v2.1
Development

No branches or pull requests
1 participant
@coolharsh55