Hi Mike, Thanks for flagging. We will make sure the TAG review status is updated to "declined" going forward.
And regarding the Explainer and Spec links, we have landed the changes and I have linked to the exact Explainer section below (we will make sure to link the exact sections going forward as well): - Explainer: https://github.com/WICG/attribution-reporting-api/blob/main/AGGREGATE.md#optional-named-budgets Thanks, Akash On Wednesday, November 6, 2024 at 6:22:06 AM UTC-8 Mike Taylor wrote: > > On 11/5/24 3:33 PM, 'Akash Nadan' via blink-dev wrote: > > Contact emails > > akash...@google.com, lin...@chromium.org, john...@chromium.org > > Explainer > > Attribution Reporting with event-level reports > <https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md> > > Attribution Reporting API with Aggregatable Reports > <https://github.com/WICG/attribution-reporting-api/blob/main/AGGREGATE.md> > > Aggregation Service for the Attribution Reporting API > <https://github.com/WICG/attribution-reporting-api/blob/main/AGGREGATION_SERVICE_TEE.md> > > Specification > > https://wicg.github.io/attribution-reporting-api/ > > Blink component > > Internals > AttributionReporting > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Internals%3EAttributionReporting> > > TAG review > > Still under review <https://github.com/w3ctag/design-reviews/issues/724> > under the original I2S for the Attribution Reporting API > > > TAG review status > > Pending > > This should be updated to "declined" (as well as the ar_debug intent), at > least in prose (seems chromestatus doesn't support that particular > resolution). > > > Summary > > We are landing the following change to the Attribution Reporting API > focused on: > > - > > Making it easier to predefine contribution budget allocation for > aggregate reports > > > This change is based on API caller feedback and the need for more control > over the contribution budget allocation. > > Currently the API has a concept of “L1 contribution budget.” This budget > limits the total amount of information that can be attributed to any single > ad impression (i.e. an ad click or view). The current L1 contribution > budget is 65,536 and API callers can use this budget across various > conversion events based on their own allocation choice. > > This change makes it easier for API callers to pre-allocate how much of > the L1 contribution budget they would like to allow for measuring different > types of events. With this change API callers can specify the maximum > amount of L1 contribution budget they would like to allow for any given > type of conversion event, directly addressing API caller feedback. > > Explainer/Spec changes > > 1. > > Explainer & Spec: > https://github.com/WICG/attribution-reporting-api/pull/1422 > > Reading diffs isn't a great experience for reviewing - could you please > put together a minimal explainer or provide hyperlinks to the spec and > explainer bits that have landed? That would be great for any future intents > as well. > > > Risks > Interoperability and Compatibility > > This is a fully backwards compatible change and an optional feature that > requires API callers to set new fields in order to use the feature. This > feature does not break any pre-existing API or web functionality. > > Gecko: No signal (Original request: > https://github.com/mozilla/standards-positions/issues/791) > > WebKit: No signal (Original request: > https://github.com/WebKit/standards-positions/issues/180) > > > WebView application risks > > Does this intent deprecate or change behavior of existing APIs, such that > it has potentially high risk for Android WebView-based applications? > > No > > > Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, Chrome OS, Android, and Android WebView)? > > The attribution reporting feature will be supported on all platforms with > the exception of Android WebView > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ? > > No, currently the behavior around aggregatable named budgets is not > covered in WPT due to difficulty of adding significant coverage for the > feature because of API-mandated delays and noise. However, the feature is > covered by comprehensive integration tests (commonly referred to as > “interop tests”) that are also reusable by other implementations. > > Estimated milestones > > This feature is anticipated to ship as part of Chrome 132 > <https://chromiumdash.appspot.com/schedule>. > > Link to entry on the Chrome Platform Status > > https://chromestatus.com/feature/5325966648541184 > > Links to previous Intent discussions > > Previous I2S: > > Intent to Ship: Attribution Reporting API > <https://groups.google.com/a/chromium.org/g/blink-dev/c/2Rmj5V6FSaY> > > Intent to Ship: Attribution Reporting features M117 > <https://groups.google.com/a/chromium.org/g/blink-dev/c/nWF61c8xu-M/m/uMmH1ewcAQAJ> > > Intent to Ship: Attribution Reporting features M118 > <https://groups.google.com/a/chromium.org/g/blink-dev/c/Mh-mJiyJZFk/m/HlgzpphYBQAJ> > > Intent to Ship: Attribution Reporting features M119 > <https://groups.google.com/a/chromium.org/g/blink-dev/c/6e44SBtEtcQ> > > Intent to Ship: Attribution Reporting features M120 > <https://groups.google.com/a/chromium.org/g/blink-dev/c/jSk3xpNPzGQ/m/VZPsdYgGCAAJ> > > Intent to Ship: Attribution Reporting features M121 > <https://groups.google.com/a/chromium.org/g/blink-dev/c/g9KiC6Rg_mA/m/V679WcWuAQAJ> > > Intent to Ship: Attribution Reporting features M123 > <https://groups.google.com/a/chromium.org/g/blink-dev/c/NE7VGke1Bjc/m/bIX00t4CAAAJ> > > Intent to Ship: Attribution Reporting features M124 > <https://groups.google.com/a/chromium.org/g/blink-dev/c/aregp1li6xk/m/IhBB2z8tBQAJ> > > Intent to Ship: Attribution Reporting features M125 > <https://groups.google.com/a/chromium.org/g/blink-dev/c/9UyhI6SRyxM/m/zgWWckgWAQAJ> > > Intent to Ship: Attribution Reporting features M126 > <https://groups.google.com/a/chromium.org/g/blink-dev/c/7UQR2lPn5KE/m/q_kL6ZiJDgAJ> > > Intent to Ship: Attribution Reporting features M127 > <https://groups.google.com/a/chromium.org/g/blink-dev/c/LAgnyPsJyJg?pli=1> > > Intent to Ship: Attribution Reporting features M128 (1) > <https://groups.google.com/a/chromium.org/g/blink-dev/c/qlsv7fn0zRE/m/SK8upePCCAAJ> > > Intent to Ship: Attribution Reporting features M128 (2) > <https://groups.google.com/a/chromium.org/g/blink-dev/c/VKGn41wMYlg/m/VsNXktqvCAAJ> > > Intent to Ship: Attribution Reporting feature M130 > <https://groups.google.com/a/chromium.org/g/blink-dev/c/-K2xDYuvmmA/m/Fhp564I7AgAJ> > > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+...@chromium.org. > To view this discussion visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/4a1a03ee-0a34-4131-8754-7694635cf5f4n%40chromium.org > > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/4a1a03ee-0a34-4131-8754-7694635cf5f4n%40chromium.org?utm_medium=email&utm_source=footer> > . > > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/d51fce3d-e7dd-4b17-ba91-fb4dac1507e8n%40chromium.org.
