How to make progress on optional fields for TSR

Hi Folks,

during the last call, we agreed that there is one scenario where
information in TSR is key to satisfying the "information" requirement
set out in the EU regulations (and also common sense).

In an ad auction with potentially unknown bidders, the site does not
know what bidders may later "pop up" out of an auction.

This causes two problems:
- The user needs to consent to an auction (being aware that the list of
bidders and the highest bidder is not known a priori)
- The auction needs to constrain data disclosure to the highest bidder
only (loosing bidders need to forget what they learned).
- The user needs to learn about the identity and the compliance regime
of the highest bidder.

Rob volunteered to document this case in detail and make a suggestion
what minimal set of flags (qualifier in header) and one additional TSR
field could make this work from a compliance point of view.

We did not identify any other scenarios that potentially require new fields.

This substantially narrows our scope and is a big step towards a resolution.

Regards,
matthias

Received on Wednesday, 5 April 2017 08:30:03 UTC