- From: Michael Kleber via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 May 2022 19:33:40 +0000
- To: public-patcg@w3.org
@eriktaubeneck I'm fully supportive of this group's approach of starting with a more limited first standardization effort. But the prerequisite is being confident that we are picking the _right_ limited-scope API to work on. I believe there is widespread agreement on the ad tech side that the "optimization" (ML training) use case is _important_. But on the browser engineering side, this group has only spent 10 minutes on what that use case actually _is_. That means we're not even in a position to answer fundamental questions like "Are we trying to design an API that can support both the measurement and optimization in the future, or would those be two different APIs?" We don't want to wait until after we've painted ourselves into a corner to ask the question that helps us pick which corner we should paint towards. Yes on scoping down, but in a fully informed way. -- GitHub Notification of comment by michaelkleber Please view or discuss this issue at https://github.com/patcg/meetings/issues/51#issuecomment-1129242219 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:33:42 UTC