- From: Rigo Wenning <rigo@w3.org>
- Date: Wed, 02 May 2012 17:34:09 +0200
- To: Jonathan Mayer <jmayer@stanford.edu>
- Cc: ifette@google.com, Nicholas Doty <npdoty@w3.org>, public-tracking@w3.org
The legal solution that results in the right incentives is simple. Make the site responsible for the choice of services they make. We can at least write that assumption into the compliance Spec or in the "how-to". I don't believe we should go down the DRM - route and want to control every subservice of a subservice, neither technically nor legally. This is guaranteed to go wrong. We know that from DRM. It would also overcharge the DNT Specifications IMHO. Rigo On Monday 30 April 2012 16:09:51 Jonathan Mayer wrote: > 2) How does a website determine which third parties presently have an > exception? > > I agree that this is a non-trivial problem for websites with many third > parties, especially chained third parties. I disagree that it's a > particularly challenging problem, as I've explained several times in > other threads. Moreover, it's a problem that already exists for the > self-regulatory opt-out programs. At any rate, if local law allows, > those websites might choose to use a site-wide exception. Allowing > explicit-explicit exceptions doesn't make the problem any harder.
Received on Wednesday, 2 May 2012 15:34:38 UTC