Meeting minutes
Meeting minutes: https://
purl for this meeting: https://
Github admin
confirmed that we will be using the dev folder to show work in progress in the master branch (with the dev branch for experimental stuff)
harsh: re-organised the github issues - closed stale issues, create labels to reflect the specs e.g. labels for gdpr, ai act, and highlighted some issues as simple enough for beginners
harsh: going ahead, more of our work will be reflected on github issues so that we can use it to keep track of discussions and decisions made
harsh: created templates for issues - see https://
harsh: a notice has been added to the PRs which states that if the PR is only for the output parts (e.g. DPV HTML), then it will not be accepted, and to instead open an issue first or ask what is the best way to contribute
harsh: the issue and PR template are as per github and are stored in .github folder in the repo
Diagrams
<ghurlbot> Issue 166 Update diagrams for v2 (by coolharsh55)
harsh: the primer has been reduced in size (40 pages) as it was far too long (150 pages) and the content has been moved/consolidated with the main DPV spec
hasrh: updated various diagrams across the specs, for GDPR was not sure about how to represent concepts as the extension is quite large. Favour instead only representing an overview of the extension e.g. as a mindmap
julian: worked on GDPR diagrams - created overview diagrams showing ontology using UML notation, and then specific diagrams for each of the sections. Diagram gets complex with more concepts.
TallTed: format of diagrams should be svg as it is possible to put links in the document and put the name of the concept in the diagram tied to the context e.g. eu-gdpr:DataProtectionAuthority and dpv:DataProtectionAuthority
harsh: overview to keep it simple and introduction to the vocabulary, and details with classes and properties are good to have in sections
georg: diagrams are useful, will use them in slides and presentations
julian: that's a good guideline that the diagram should not be too complex - should be enough to introduce and talk about the concepts in a slide in presentation
Lawfulness concepts
<ghurlbot> Issue 2 Formulate a notion of compliance in the scope of the CG (by coolharsh55)
harsh: I closed the issue as we have added lawfulness concepts in DPV and GDPR. Beatriz raised the point that we would need to add similar concepts for other laws. At the moment, we have DGA, AI Act, and NIS2 - none of which have authorities set up who can specify what forms the compliance will take e.g. will it be a common EU wide status like GDPR, or will there be specific country-wise compliance e.g. for NIS2. So the idea is to add these to the next version.
beatriz: this is fine as it will be needed in the future.
Next Meeting
The next meeting will be in 1 week. We changed the time to accommodate harsh's, beatriz's, and julian's schedules. The meeting will take place on TUE 16 JUL 13:30 WEST / 14:30 CEST. Agenda will consist of going through the 2.1 milestone work and any other updates on the mailing list.