Predefined values for addPrivacyInfo?

[janwinkler]

Hi,

from
https://github.com/labadserver/Adplayer/wiki/Adplayer-Creation-Process-and-Hierarchy
the example call is:
adPlayer.addPrivacyInfo('ADTECH', 'Message to pass.', 'http://optout.com');

The question here is if the Lizenzstelle/meinecookies/BVDW/whoever will define the texts we can use or if anybody can post its own texts?

For multilanguage it might be better if we do not submit text but integers. the player may use the int's to create it's own text in the language of the user. that way, every icon will have the same texts and it will be much smarter to the users to understand.

example:
adPlayer.addPrivacyInfo('ADTECH', 1&2&4, 'http://optout.com');

will give an example text like “Anbieter sammelt Daten für Retargeting (1), Behavorial Targeting (2), Markstudien (4).”.

Best,
Jan

[chrissancho]

Hi Jan,

Concept and Implementation is being changed in our new milestone. So this approach will slightly be deprecated.

With that said, anyone in the chain is able to define their own text. I can imagine it being difficult to define an integer for every piece of text since messages are unique. Furthermore, this will require a new branch of standardization for this implementation that is slightly off topic from the initial goal of the AdPlayer.

Alas, all hope is not lost. The new implementation involves a server side script with a method "registerPrivacyInfo" that passes oba information to the target player. If localization is intended for your own goals, adjustments can be easily made here.

More details to follow, but I will add this to our milestone as a backlog for future reference and consideration.

[andreasberenz]

Hi Jan,

I think there should be predefined functions to retrieve uniform textphrases for standard cases translated to the current user language.

But I don't like to build up a domain specific language as described in your proposal. I think it would be better to use "constants" in a convention like that:

var text = $ADP.PrivacyTextpool.get($ADP.PrivacyTextpool.USECASE_DESC);

...addPrivacyInfo('ADITION',text,optout);

Should be done similar in our new implementation by using $ADP.Registry

Regards

Am 04.05.2012 um 11:16 schrieb janwinkler reply@reply.github.com:

Hi,

from
https://github.com/labadserver/Adplayer/wiki/Adplayer-Creation-Process-and-Hierarchy
the example call is:
adPlayer.addPrivacyInfo('ADTECH', 'Message to pass.', 'http://optout.com');

The question here is if the Lizenzstelle/meinecookies/BVDW/whoever will define the texts we can use or if anybody can post its own texts?

For multilanguage it might be better if we do not submit text but integers. the player may use the int's to create it's own text in the language of the user. that way, every icon will have the same texts and it will be much smarter to the users to understand.

example:
adPlayer.addPrivacyInfo('ADTECH', 1&2&4, 'http://optout.com');

will give an example text like “Anbieter sammelt Daten für Retargeting (1), Behavorial Targeting (2), Markstudien (4).”.

Best,
Jan

---

Reply to this email directly or view it on GitHub:
#58

[andreasberenz]

I wanted to say, that the concatination of the messages should not be done by addPrivacyInfo by splitting a string and retrieving information by its pieces.

:)

Am 04.05.2012 um 11:16 schrieb janwinkler reply@reply.github.com:

Hi,

from
https://github.com/labadserver/Adplayer/wiki/Adplayer-Creation-Process-and-Hierarchy
the example call is:
adPlayer.addPrivacyInfo('ADTECH', 'Message to pass.', 'http://optout.com');

The question here is if the Lizenzstelle/meinecookies/BVDW/whoever will define the texts we can use or if anybody can post its own texts?

For multilanguage it might be better if we do not submit text but integers. the player may use the int's to create it's own text in the language of the user. that way, every icon will have the same texts and it will be much smarter to the users to understand.

example:
adPlayer.addPrivacyInfo('ADTECH', 1&2&4, 'http://optout.com');

will give an example text like “Anbieter sammelt Daten für Retargeting (1), Behavorial Targeting (2), Markstudien (4).”.

Best,
Jan

---

Reply to this email directly or view it on GitHub:
#58

[AParsonsADITION]

I would suggest that if we want to build in multilanguage support that the language should be set by the publisher and language identifier is then pushed with the id and can be requested from the registration object. The translated text can then be provided by the parties creating the privacy messages.

If there is a set of standard header, footer, descriptions and click messages that are to be defined then it would make sense to create a translation library/function to house these standard messages that can be used to retrieve the correct translation of the required standard message for the current selected language.

[dhellmuth]

• useful feature
• not in v1.0
• to work on for v2.0

[dhellmuth]

Telco 26.06.: no action, results of tests should be awaited

[dhellmuth]

Telco 26.11.: remains in backlog, waiting if feature will be asked by users