-
Notifications
You must be signed in to change notification settings - Fork 26
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-TECH properties have incorrect domain/range #44
Comments
Updated the source spreadsheet to fix this. The next generation of code and docs should fix this - nothing more to do except verify before publishing next release. |
dpv:hasEntity
instead of dpv:hasEntity
DPV-TECH properties have incorrect domain
|
The ranges now reflect the specific Technology Actor roles.
|
The properties related to technology actors (provision, developer, user, subject) have their domain set to `dpv:Technology` and the respective `TechnologyActor` from dpv-tech extension.
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
No description provided.
The text was updated successfully, but these errors were encountered: