-
Notifications
You must be signed in to change notification settings - Fork 27
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
DPV releases should contain only the vocabulary #40
Comments
The script 801_generate_releases.sh will create zips in base/releases. Some items are WIP (i.e. CSV, JSON), others are deactivated due to empty folders (guides, examples).
The script 801_generate_releases.sh will create zips in base/releases. Some items are WIP (i.e. CSV, JSON), others are deactivated due to empty folders (guides, examples).
Additions: - #40 script for creating releases (see script 803) - risk extension at /dpv/risk - rights extension at /dpv/rights, currently only provides EU's Charter of Fundamental Rights at dpv/rights/eu - DPIA concepts in DPV-GDPR - Better modularisation of concepts, Context -> Status, ProcessingContext -> ProcessingScale, LegalBasis -> special category personal data, data transfer - Adds OWL-Manchester syntax output for DPV-OWL Fixes: - Fixes #37 Fixes #41 Adds property domains/ranges in HTML - Fixes #44 dpv-tech properties incorrect domain/range - Fixes label consistency (dct:title -> skos:prefLabel or rdfs:label) - Remove SKOS concepts from DPV-OWL
Update: as of |
AFAIK, this is done, other than the XLSX or CSV document structuring. If someone needs this, please open a specific new issue for that with requirements. If there are no more actions for this discussion, I will mark it as resolved on OCT-15. |
We discussed in today's meeting and are okay with the current list, closing as completed. |
Currently the DPV release mechanism is based on GitHub taking the entire repo and putting it in a zip file. Anyone downloading this will find the entire catalogue of DPV related resources, including different 'flavours' and the documentation generator also bundled into it. Instead, only the relevant files should be provided as clearly separated as is feasible. For example, each release could provide separate zips for:
The text was updated successfully, but these errors were encountered: