Re: [meetings] Agenda Request - Measurement use-cases deep dive and requirements (#51)

@csharrison that makes sense, and I agree this is a use case we will want to work towards support. That said, there is obviously a big tradeoff between a system which supports a bunch of the sub-use cases, and working towards a first standard that has more limited scope.

I think the most important outcome from this meeting is getting consensus on the first use case we want to solve for, and establishing that as the starting effort for the Working Group. I know I've heard calls for starting with a first standard that is somewhat limited in scope, so that we can make progress and build momentum towards solving more of the sub-use cases within measurement, as well as entirely other use cases.

I do think it's important to understand all the sub-use cases (e.g. attribution reporting, reach and frequency reporting, optimization, etc), and to consider the compatibility of those within the standard that ends up being developed. It would be great if we build a standard for one sub-use case, but with an approach that would be reasonably compatible for other sub-use case. For example, I would say that both the Aggregate Attribution Reporting API and IPA, if standardized for reporting, could be done in optimization compatible way.



-- 
GitHub Notification of comment by eriktaubeneck
Please view or discuss this issue at https://github.com/patcg/meetings/issues/51#issuecomment-1129199319 using your GitHub account


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

Received on Tuesday, 17 May 2022 18:42:25 UTC