Difference between revisions of "Project:Vocabulary/GDPR"

Revision as of 15:24, 10 February 2020

Use cases

The Ontology need to be suitable for data entries and the usages of those data. We need to identify use case and test the ontology against those.

Examples

Core snaks

instance of (P3) - data controller (Q96)
e-mail address (P17) - "mailto:johnny@example.com"
- for (Q1062) - data controller (Q96)
- qualifier is not currently checked but it should be, as there may be a general support email as well as a data protection officer specific email address.
contact page (P282) - "https://company/privacy/contact"
- This is necessary where there is no known email address for contacting the data protection officer, only a form. In these cases you probably still need to add e-mail address (P17) but with a dummy email address (and a comment qualifier making clear it is not a real address). The generated email then has to be manually pasted into the contact form for submission. For example see Apple (Q3424)
collects (P10) - the points of data known to be collected/stored by this company.
- named as (P27) - "alternative string name"
  - This qualifier allows existing items to be re-used. The idea is that the 'named as' value is the display name that is used in the GDPR request letter. So if we already have 'location' but want to include 'geolocation info' because that is the term used for this concept from the company's privacy policy, we can include location (Q1078) in the collects (P10) list but add named as (P27) - 'geolocation info' as a qualifier. This is important to allow the eventual unification of different data concepts into one model despite companies describing them differently.
- source (Q1117) - privacy policy (Q29) or source (Q1117) - privacy hub (Q3732)
  - This qualifier is especially important where other data points have already been added to the collects (P10) list from different sources. This is used to distinguish things we have learnt from different sources. We should update our GDPR generators to only include the collects (P10) items from the sources we want to use (which may differ per project).
- policy excerpt (P287) - "Extract from privacy policy which shows why this data point is believed to be stored."
  - Add more than once if a long extract is needed. Take care to remove spaces from end of string or you will get a `Malformed text` error.
official website (P15) - URL (optional really)
states compliance (P32) - privacy policy (Q29)
- reference URL (Q467) - 'https://companyname.com/privacy/policy.html'
- This snak and qualifier are the standard way to specify the company's privacy policy URL. Note this should be added as a qualifier not a reference.

FAQ

Q: how do we refer to privacy policy? there are a few different ways to do it.

A: The correct one is privacy policy (Q29) though we have previously used Q3405 and some usages of this still need to be migrated. Q3667 and Q173 are erroneous and should be deleted.

Data rights snaks

Multiple choice between different options

References

PREFIX pdio: <https://wiki.personaldata.io/entity/>
PREFIX pdiot: <https://wiki.personaldata.io/prop/direct/>
PREFIX pdiop: <https://wiki.personaldata.io/prop/>
PREFIX pdiops: <https://wiki.personaldata.io/prop/statement/>
PREFIX pdiopq: <https://wiki.personaldata.io/prop/qualifier/>
SELECT ?item ?itemLabel ?link WHERE {
  ?item pdiot:P110 pdio:Q3006. #P110 <-concerns Q3006 <-ontology model	
  OPTIONAL {?item pdiot:P15 ?link.}
  SERVICE wikibase:label {
    bd:serviceParam wikibase:language "en" . 
  }
}
LIMIT 100

sources on (GDPR) ontology modeling (embedded)

@@ Line 20: / Line 20: @@
 ** qualifier is not currently checked but it should be, as there may be a general support email as well as a data protection officer specific email address.
 * {{P|282}} - "https://company/privacy/contact"
-* This is necessary where there is no known email address for contacting the data protection officer, only a form. In these cases you probably still need to add {{P|17}} but with a dummy email address (and a comment qualifier making clear it is not a real address). The generated email then has to be manually pasted into the contact form for submission. For example see {{Q|3424}}
+** This is necessary where there is no known email address for contacting the data protection officer, only a form. In these cases you probably still need to add {{P|17}} but with a dummy email address (and a comment qualifier making clear it is not a real address). The generated email then has to be manually pasted into the contact form for submission. For example see {{Q|3424}}
 * {{P|10}} - the points of data known to be collected/stored by this company.
 ** {{P|27}} - "alternative string name"