- From: Bosko Milekic via GitHub <sysbot+gh@w3.org>
- Date: Sun, 13 Feb 2022 16:20:11 +0000
- To: public-patcg@w3.org
> > Finally, I propose that we consider privacy and security separately to utility. > > I'm not clear what you are suggesting here, can you expand on it a little? Sure, and apologies for the lack of clarity. What I meant is that I think that it's easier to analyze the proposals in terms of utility that each provides, without thinking too much about their privacy and security characteristics. This does not mean that the privacy and security principles and characteristics are unimportant or that we should not consider them, just that they can be looked at and discussed in parallel. I initially created this issue because when I looked at @csharrison [attribution reporting design space tradeoffs and considerations slides](https://github.com/patcg/meetings/blob/main/2022/02/09-telecon/attribution-tradeoffs-goog.pdf), the third slide "Privacy vs Utility" lists "timely, fine-grained, accurate" as examples of utility, and I thought it would be good to expand on those three points further, to get a more detailed view of how the proposals compare w.r.t. utility provided. As one example, if we consider "Cross Browser / Cross Device Measurement" as being useful and highly desirable for advertisers, which of the current proposals provide a way to achieve it? From reading the Mozilla/Meta IPA proposal, it seems that cross-device attribution measurement will be possible within the described framework, assuming match key providers participate at scale. How about with the other proposals? Note that I'm not trying to claim that in and of itself "Cross Browser / Cross Device Measurement" is imperative to have on day 1, but I think that looking at the proposals side by side and comparing them in terms of supported capabilities (i.e., utility) will help us understand and compare them along that dimension better. Hope that helps! -- GitHub Notification of comment by bmilekic Please view or discuss this issue at https://github.com/patcg/meetings/issues/25#issuecomment-1038227884 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 13 February 2022 16:20:13 UTC