[meetings] Agenda Request - what is the right scope for functionality that should be supported in the first iteration of the joint measurement effort? (#56)

marianapr has just created a new issue for https://github.com/patcg/meetings:

== Agenda Request -  what is the right scope for functionality that should be supported in the first iteration of the joint measurement effort? ==
In the sessions dedicated to measurement use-cases deep dive and requirements Charlie presented several applications and their importance. We started a discussion what subset of these applications should be supported in the first design version of the measurement effort. Most of this discussion was focused on whether optimization should be a requirement. I also want to add here the question whether we should require support for attributions outside the user device, this will enable cross-device attribution but will come with complexities related to the joining. Is it worth starting with a solution based on the current instantiations of the PPM standardization effort in IETF (one advantage of this is that such solutions have been deployed and are still running in practice for other aggregation applications such as the Exposure Notifications Private Aggregation, https://github.com/google/exposure-notifications-android/blob/master/doc/enexpress-analytics-faq.md) 

It will be great to continue this discussion here and get opinions from more people about what are the minimum functionality capabilities that will make the outcome of the first iteration of the measurement design useful for them.

Please view or discuss this issue at https://github.com/patcg/meetings/issues/56 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 20 May 2022 02:13:48 UTC