Meeting minutes
DPV v1 prep
We discussed pending issues on GitHub and resolved all open issues for v1.
The collection of issues is at - https://
Specify conditions, constraints, or restrictions e.g. for purpose or data category #18 - resolved as we have Rules now.
<Github> https://
Add/Expand Purpose Categories #22 - resolved as we have refined the purposes recently and identify no major issues.
<Github> https://
Adding Safeguards to DPV #23 - resolved as we went through the list and have confirmed the safeguards are present in DPV.
<Github> https://
DPV releases should contain only the vocabulary #40 - resolved as code has been implemented.
<Github> https://
List of concepts, documentation, and other things to be provided in DPV v1.0.0 #38 - resolved as we have agreed on v1 concepts and future work.
<Github> https://
Adding PII as a concept
We discussed whether to add PII as a concept as it is used in several use-cases and jurisdictions.
The issue is the exact definition of PII and its relation with PersonalData. There are several different iterations, and while providing PII may be of value, if it is the exact same as PersonalData, then there is no need to provide a concept separately.
Instead, if PII is a subtype of PersonalData, then this should be made explicitly clear through the definition.
We have decided for now to keep the issue open and discuss it later.
Indicating PII i.e. Personally Identifiable data category or categories in combination #14
<Github> https://
(relevant issue)
Sensitivity of Data
Express 'sensitivity' of data #11 - relevant issue
<Github> https://
We discussed whether we should provide sensitivity of data as a concept/relation to indicate how sensitive the data is (on a scale).
Harsh's proposal is to reuse Severity instead of creating a separate scale, since the use of severity is tied to risk/impact which uses levels and severities.
Paul disagrees that such use is compantible, and that severity reflects association with impact, whereas severity is a concept applicable before use.
We have decided to keep the issue open for this discussion to continue later.
Pending tasks
Documentation Style Guide #39 - harsh will create a wiki page with some collected requirements
<Github> https://
Diagrams #24 #65 - Georg and Delaram are working on this
<Github> https://
<Github> https://
Use-Cases and Examples showing how vocab can be used #12 - harsh and beatriz are editing these
<Github> https://
georg has suggested to not use new concepts (~ex:Concept~) in the examples as it causes confusion as to where those concepts are in DPV. Or, to provide textual description that these concepts have been created to show how DPV's concepts can be extended.
Machine-readable requests to execute rights #4 Rights Exercise - will be integrated in v1, needs textual description
<Github> https://
Next Meeting
We will meet again in 1 week, on WED NOV-30 13:00 WET / 14:00 CET
Other than textual descriptions to be added to the specification, and the diagrams, no other issues have urgency.
The guides, use-cases, examples, and refinements will continue to happen post v1 release.