Changes

* {{P|10}} - the points of data known to be collected/stored by this company.

* {{P|10}} - the points of data known to be collected/stored by this company.

** {{P|27}} - "alternative string name"

** {{P|27}} - "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 {{Q|1078}} in the {{P|10}} list but add {{P|27}} - '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. This is currently only used in Alex Bowyer's GDPR Generator ({User:Alexbfree/Code:GDPRMailAccess.js}). It is recommended this be merged to the Le Temps generator. Another use of this field is to convert the pronoun to the correct form for the letter - for example the stored data point might be "information about your journeys". You can add a {{P|27}} to change this to "information about my journeys" in the generated GDPR letter.  

*** 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 {{Q|1078}} in the {{P|10}} list but add {{P|27}} - '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. This is currently only used in Alex Bowyer's GDPR Generator ([[User:Alexbfree/Code:GDPRMailAccess.js]]). It is recommended this be merged to the Le Temps generator. Another use of this field is to convert the pronoun to the correct form for the letter - for example the stored data point might be "information about your journeys". You can add a {{P|27}} to change this to "information about my journeys" in the generated GDPR letter.  

** {{Q|1117}} - {{Q|29}} or {{Q|1117}} - {{Q|3732}}

** {{Q|1117}} - {{Q|29}} or {{Q|1117}} - {{Q|3732}}

*** This qualifier is especially important where other data points have already been added to the {{P|10}} 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 {{P|10}} items from the sources we want to use (which may differ per project).

*** This qualifier is especially important where other data points have already been added to the {{P|10}} 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 {{P|10}} items from the sources we want to use (which may differ per project).

** Currently all items in the {{P|122}} list will be included at the end of the GDPR letter as possible things that the data subject will provide to identify themself. We probably need to refine this - to differentiate between things that are needed to even identify a customer to kick off a request (account number, username etc.) vs things that may be asked for by the company after a GDPR request has started (e.g. security checks, copies of proof of address etc).  

** Currently all items in the {{P|122}} list will be included at the end of the GDPR letter as possible things that the data subject will provide to identify themself. We probably need to refine this - to differentiate between things that are needed to even identify a customer to kick off a request (account number, username etc.) vs things that may be asked for by the company after a GDPR request has started (e.g. security checks, copies of proof of address etc).  

** {{P|27}} - "alternative string name"

** {{P|27}} - "alternative string name"

*** In Alex Bowyer's GDPR Generator ({User:Alexbfree/Code:GDPRMailAccess.js}) this has been updated to make use of {{P|27}} as in the {{P|10}} list above. This is important to allow re-use of semantic concepts but with different names. It is recommended this be merged to the Le Temps generator.

*** In Alex Bowyer's GDPR Generator ([[User:Alexbfree/Code:GDPRMailAccess.js]]) this has been updated to make use of {{P|27}} as in the {{P|10}} list above. This is important to allow re-use of semantic concepts but with different names. It is recommended this be merged to the Le Temps generator.

===Issues/Clashes===

===Issues/Clashes===

* Use of {{Q|1048}} qualifier

* Use of {{Q|1048}} qualifier

** Currently the Le Temps GDPR generator ({MediaWiki:Access.js}) uses the {{Q|1048}} qualifier when attached to a {{P|10}} snak and prints that text in brackets after each data point in the generated GDPR letter. Originally Alex Bowyer's GDPR Generator {User:Alexbfree/Code:GDPRMailAccess.js} used {{Q|1048}} qualifier to contain a policy excerpt but these are being migrated to {{P|287}} as we do not want these printed in the letter (also many of them are too long and break the generator. Alex's generator has switched to never print the {{Q|1048}} and he would recommend Le Temps do the same. {{Q|1048}} should be free for use by wiki users to add detail about a snak. For example see the {{P10}} list usage in {{Q|281}}.

** Currently the Le Temps GDPR generator ([[MediaWiki:Access.js]]) uses the {{Q|1048}} qualifier when attached to a {{P|10}} snak and prints that text in brackets after each data point in the generated GDPR letter. Originally Alex Bowyer's GDPR Generator ([[User:Alexbfree/Code:GDPRMailAccess.js]]) used {{Q|1048}} qualifier to contain a policy excerpt but these are being migrated to {{P|287}} as we do not want these printed in the letter (also many of them are too long and break the generator. Alex's generator has switched to never print the {{Q|1048}} and he would recommend Le Temps do the same. {{Q|1048}} should be free for use by wiki users to add detail about a snak. For example see the {{P10}} list usage in {{Q|281}}.