[FIX]: some DPAs are defined as dpv:DataProtectionAuthority rather than eu-gdpr:DataProtectionAuthority
#192
Comments
coolharsh55
added a commit
that referenced
this issue
Oct 22, 2024
- The GDPR DPAs i.e. DPAs in EU/EEA member states are defined as instances of eu-gdpr:DataProtectionAuthority instead of dpv:DataProtectionAuthority - This allows these DPAs to be correctly used to represent which authorities enforce the GDPR in LEGAL HTML documentation
coolharsh55
added a commit
that referenced
this issue
Nov 13, 2024
- the GDPR implementing DPAs were listed as enforcing GDPR via `dpv:hasApplicableLaw`, but the inverse triple stating GDPR is being enforced by the DPAs through `dpv:hasAuthority` was missing - this triple is automatically generated by the hook presented in `vocab_management.py` which was configured to only run for specific extensions which had lots of jurisdictions missing - the fix was to add all the legal jurisdictions presented under `/legal/` in this variable and then rerun `200` RDF generation and `300` HTML generation steps - in the future, the issue will arise again if the variables are not updated for new legal jurisdictions added
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Specs
LEGAL (e.g. IE, US), EU-GDPR
Errors
Fix by declaring DPAs under GDPR as
eu-gdpr:DataProtectionAuthority(this applies to jurisdiction extensions for countries)The text was updated successfully, but these errors were encountered: