Project:Vocabulary/GDPR - Revision history

Podehaye: /* Issues/Clashes */

2020-02-11T22:45:44Z

Issues/Clashes

Alexbfree: /* Issues/Clashes */

2020-02-11T10:36:39Z

Issues/Clashes

Alexbfree at 10:36, 11 February 2020

2020-02-11T10:36:01Z

Alexbfree at 10:35, 11 February 2020

2020-02-11T10:35:17Z

Alexbfree at 10:35, 11 February 2020

2020-02-11T10:35:00Z

Alexbfree at 10:33, 11 February 2020

2020-02-11T10:33:12Z

Alexbfree at 10:32, 11 February 2020

2020-02-11T10:32:31Z

Alexbfree at 10:19, 11 February 2020

2020-02-11T10:19:23Z

Alexbfree: /* Issues/Clashes */

2020-02-11T10:18:27Z

Issues/Clashes

Alexbfree at 10:14, 11 February 2020

2020-02-11T10:14:38Z

@@ Line 40: / Line 40: @@
 ===Issues/Clashes===
 * 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 {{P|10}} list usage in {{Q|281}}.
 * Figuring out how to display a {{P|10}} item's {{P|27}} string if it has one, or its main {{P|10}} item text otherwise.
 ** This is a future To Do for @alexbfree or anyone else who wants to have a go. @podehaye has provided an idea for this, detailed here:

@@ Line 61: / Line 61: @@
 |}
-* Until this is done, the current workaround is to show <pre><named as> / <collects-text></pre> if there is a {{P|27}}, or <pre><collects-text></pre> otherwise. The latter part can be manually deleted from the generated letter on {{P|27}} items.
+* Until this is done, the current workaround in Alex Bowyer's GDPR Generator ([[User:Alexbfree/Code:GDPRMailAccess.js]]) is to show <pre><named as> / <collects-text></pre> if there is a {{P|27}}, or <pre><collects-text></pre> otherwise. The latter part can be manually deleted from the generated letter on {{P|27}} items.
 ===FAQ===

@@ Line 61: / Line 61: @@
 |}
-** Until this is done, the current workaround is to show <pre><named as> / <collects-text></pre> if there is a {{P|27}}, or <pre><collects-text></pre> otherwise. The latter part can be manually deleted from the generated letter on {{P|27}} items.
+* Until this is done, the current workaround is to show <pre><named as> / <collects-text></pre> if there is a {{P|27}}, or <pre><collects-text></pre> otherwise. The latter part can be manually deleted from the generated letter on {{P|27}} items.
 ===FAQ===

@@ Line 60: / Line 60: @@
 | it would be awesome if you managed to duplicate and modify <nowiki>Module:For</nowiki> into <nowiki>Module:TwoVariableFor</nowiki>
 |}
 ** Until this is done, the current workaround is to show <pre><named as> / <collects-text></pre> if there is a {{P|27}}, or <pre><collects-text></pre> otherwise. The latter part can be manually deleted from the generated letter on {{P|27}} items.

@@ Line 60: / Line 60: @@
 | it would be awesome if you managed to duplicate and modify <nowiki>Module:For</nowiki> into <nowiki>Module:TwoVariableFor</nowiki>
 |}
 ===FAQ===

@@ Line 43: / Line 43: @@
 * Figuring out how to display a {{P|10}} item's {{P|27}} string if it has one, or its main {{P|10}} item text otherwise.
 ** This is a future To Do for @alexbfree or anyone else who wants to have a go. @podehaye has provided an idea for this, detailed here:
-{| class="wikitable" style="margin-left: 20px;|-
+{| class="wikitable" style="margin-left: 50px;|-
 | [[https://wiki.personaldata.io/wiki/Template:For Template:For]] is a template that essentially applies one template in succession to a bunch of parameters, with a separator (ignore the named variables)
 |-

@@ Line 41: / Line 41: @@
 * 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}}.
-* Figuring out how to display a {{P|10}} item's {{P|27}} string if it has one, or its main {{P|10}} item text otherwise. @podehaye has provided an idea for this, detailed here. This is a future To Do for @alexbfree or anyone else who wants to have a go.
+* Figuring out how to display a {{P|10}} item's {{P|27}} string if it has one, or its main {{P|10}} item text otherwise.
-<blockquote>
+** This is a future To Do for @alexbfree or anyone else who wants to have a go. @podehaye has provided an idea for this, detailed here:
-* https://wiki.personaldata.io/wiki/Template:For is a template that essentially applies one template in succession to a bunch of parameters, with a separator (ignore the named variables)
+{| class="wikitable" style="margin-left: 20px;|-
-* this is based on the module For https://wiki.personaldata.io/w/index.php?title=Module:For
+| [[https://wiki.personaldata.io/wiki/Template:For Template:For]] is a template that essentially applies one template in succession to a bunch of parameters, with a separator (ignore the named variables)
-* do you understand why the template is limited to five named parameters while Module:For does not explicitly implement such limitation?
+|-
-* in any case what you want to solve your problem is a module TwoVariableFor, which takes a bunch of parameters and feeds them two at a time into a rendering function that takes a pair of arguments, the second one being possibly empty
+| this is based on the module [[https://wiki.personaldata.io/w/index.php?title=Module:For Module:For]]
-* then you want to have something like {{#invoke:TwoVariableFor|call=MyRenderingTemplateInPairs|firstitem|firstqualifier|seconditem||thirditem|thirdqualifier}} (if for instance the second qualifier was missing)
+|-
-* now the question is how you generate the list of parameters, but you can use an invoke:Wd for this
+| do you understand why the template is limited to five named parameters while Module:For does not explicitly implement such limitation?
-* so: {{#invoke:TwoVariableFor|call=MyRenderingTemplateInPairs|{{#invoke:wd|...what you already know how to do...}}}}
+|-
-* it would be awesome if you managed to duplicate and modify Module:For into Module:TwoVariableFor
+| in any case what you want to solve your problem is a module TwoVariableFor, which takes a bunch of parameters and feeds them two at a time into a rendering function that takes a pair of arguments, the second one being possibly empty
-</blockquote>
+|-
 ===FAQ===

@@ Line 24: / Line 24: @@
 * {{P|10}} - the points of data known to be collected/stored by this company.
 ** {{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}}
 *** 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).
@@ Line 36: / Line 36: @@
 ** 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"
-*** 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===
 * 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}}.