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

@LeaVerou, @plinss and myself looked at our "Kronos" virtual f2f. It would great to have the following issues addressed:

- Can you provide an explicit list of the types of reports we are evaluating for?
- Given this feature could be sending PII through such reports, can you please complete the Privacy & Security questionnaire?
- Some of the report endpoints have to be sent by definition to different servers. That would mean we're exposing information to a 3rd party by design. Are we reading the proposal correctly? 
- What would the list of all types of endpoints be?
- [Would an event be more appropriate?](https://w3ctag.github.io/design-principles/#events-vs-observers)
- Using such reporting mechanism, do you expect to have user-generated events part of the same reports?
- The current design suggests the use of a queue that would require pulling. Could this be a callback instead? That would make it easier to decide between an event and observer.
- Should all reports be visible to script?
- Currently the JSON object includes keys in both underscore case (`user_agent`) and camelCase (`lineNumber`). For consistency, it would be best to use [underscore case](https://w3ctag.github.io/design-principles/#casing-rules) only.

-- 
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#issuecomment-767707969