Re: tracking-ISSUE-184 (Walter van Holst): 3rd party dependencies in 1st party content [Tracking Definitions and Compliance] from Walter van Holst on 2012-10-24 (public-tracking@w3.org from October 2012)

From: Walter van Holst <walter.van.holst@xs4all.nl>
Date: Wed, 24 Oct 2012 23:33:41 +0200
To: public-tracking@w3.org
Message-ID: <50885EB5.7030801@xs4all.nl>

On 10/24/12 11:14 PM, Fred Andrews wrote:

> The DNT consent API may be creating the same problem by enabling nag-ware to
> just continue prompting the user for consent!

I think that can easily be prevented by treating any dependencies on 3rd
party content as a non-compliant expression of a 'same-party' status
object of the tracking status resource.

My understanding of the rationale, or at least a major rationale, for
the 1st vs 3rd party distinction is that in the current eco-system 1st
parties have relatively loose ties with 3rd parties, especially
advertisers who come and go on the fly through brokering platforms, and
that this group acknowledges this as a commercial fact.

If however the 1st party content is dependent on 3rd party content, I
think this practical rationale no longer applies.

Regards,

 Walter

Received on Wednesday, 24 October 2012 21:34:10 UTC