[w3ctag/design-reviews] Reporting (#585)

HIQaH! QaH! TAG!

I'm requesting a TAG review of the Reporting API.

The Reporting API is a mechanism for web servers to tell browsers where to send errors and other information about a browsing session.

  - Explainer¹ (minimally containing user needs and example code): https://github.com/w3c/reporting/blob/master/EXPLAINER.md

  - Specification URL: https://w3c.github.io/reporting/

  - Tests: [Generic tests](https://wpt.fyi/results/reporting?label=experimental&label=master&aligned), but also [feature integration tests](https://wpt.fyi/results/permissions-policy/reporting?label=experimental&label=master&aligned)
  - Security and Privacy self-review²: https://github.com/w3c/reporting/blob/master/security-and-privacy-questionnaire.md

  - GitHub repo (if you prefer feedback filed there): https://github.com/w3c/reporting/

  - Primary contacts (and their relationship to the specification):
      - Ian Clelland (@clelland), Google (Editor)
      - Douglas Creager (@dcreager), GitHub (Editor)
      - Mike West (@mikewest), Google (Editor)
      - Ilya Grigorik (@igrigorik), Google (Group Chair)
      - Nic Jansma (@nicjansma), Akamai (Group Chair)
      - Yoav Weiss (@yoavweiss), Google (Group Chair)

  - Organization(s)/project(s) driving the specification: Google
  - Key pieces of existing multi-stakeholder review or discussion of this specification: 
The Reporting API has been discussed within WebPerfWG several times; [TPAC 2019 minutes](https://docs.google.com/document/d/1-xMvUHAjqhQdegNqupxlqsLbfPHWq5MJ0iySg9Z1KBs/edit#heading=h.kryll0txlacb), [TPAC 2020 minutes](https://docs.google.com/document/d/1inejuvPONXPOLKTCcUzOBhPh6QOckMcltnR-E3xyZVQ/edit?ts=5fa98a72&pli=1#heading=h.6na6dc1pssqh), as well as issues such as https://github.com/w3c/reporting/issues/158 and https://github.com/w3c/reporting/issues/169, which have resulted in a reduced scope for the specification and changes to the header.
  - External status/issue trackers for this specification (publicly visible, e.g. Chrome Status):
    - [Chrome Platform Status](https://www.chromestatus.com/feature/4672626140119040)
    - [Mozilla Standards Position](https://github.com/mozilla/standards-positions/issues/104)

Further details:

  - [x] I have reviewed the TAG's [API Design Principles](https://w3ctag.github.io/design-principles/)
  - Relevant time constraints or deadlines: Chrome is preparing to ship changes to the API based on feedback from other browser vendors in https://github.com/w3c/reporting/issues/158, hoping to land those with Chrome 89 soon.
  - The group where the work on this specification is currently being done: WebPerfWG
  - The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): WebPerfWG
  - Major unresolved issues with or opposition to this specification:
  - This work is being funded by: Google

You should also know that, while the Reporting API has shipped in Chrome for some time, and several features have integrated with it, and ReportingObserver has been reviewed by TAG, the API as a whole was never reviewed. This is relevant now as changes have been made to the scope of the API, as well as the header used and its syntax, which Chrome is looking to ship.

We'd prefer the TAG provide feedback as (please delete all but the desired option):

  🐛 open issues in our GitHub repo for **each point of feedback**

² A Security and Privacy questionnaire helps us understand potential security and privacy issues and mitigations for your design, and can save us asking redundant questions. See https://www.w3.org/TR/security-privacy-questionnaire/.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/585