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

I definitely think it's very important to get the use cases nailed
down. Once we've done that, we can try to figure out how many
different technical approaches we are going to need. As I see
it, the current situation is:

1. We have a set of somewhat clearly defined "conversion measurement"
   use cases that is what IPA, the Aggregate Measurement API,
   and PCM are targeting.

2. We have a less well defined (because we haven't talked about
   it, not to say that someone doesn't have it well defined)
   optimization use case that is what the Event Conversion
   Measurement API is targeting.


My best case scenario for this meeting would be:

1. Clearly flesh out the conversion measurement use cases
   and where the existing proposals fall short.
2. Improve our understanding of the optimization use cases.
3. Work out whether we want to try to build one solution
   that covers both or two solutions.
4. (Stretch goal) Figure out the most promising technical
   directions and what we would need to do to actually
   pick a starting point.


In terms of meeting time, I think it would be good to have
sessions on:

- Getting the exhaustive description of the conversion measurement
  use case.
- Gap analysis between IPA/AMAPI/PCM and that use case
- Introduction to the optimization use case
- Discussion of next steps

As I think I've said earlier, I would actually vote to punt everything
that's not this, unless people don't feel ready to have these discussions.
 


   


-- 
GitHub Notification of comment by ekr
Please view or discuss this issue at https://github.com/patcg/meetings/issues/51#issuecomment-1129263587 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 19:59:15 UTC