- From: caribouW3 via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Jun 2021 14:08:44 +0000
- To: public-privacy@w3.org
caribouW3 has just labeled an issue for https://github.com/w3cping/privacy-request as "REVIEW REQUESTED": == Document_name 2021-mm-dd > 2021-mm-dd == - name of spec to be reviewed: Resource Timing - URL of spec: https://w3c.github.io/resource-timing/ - What and when is your next expected transition? https://github.com/w3c/transitions/issues/337#issuecomment-850633515 Wide review was done in 2017. The Director is requesting a formal wide review with the most recent horizontal review process. - What has changed since any previous review? In comparison to previously published "level 1" (in CR), changes are mainly the addition of the size attributes, better buffering algorithms and Fetch integration. We plan to drop levels and use a living standard development model (from process2020). In comparison to previously published "level 1" (in CR), changes are mainly the addition of the size attributes, better buffering algorithms and Fetch integration. - Does your document have an in-line Privacy Considerations section, separate from Security Considerations? If not, corrrect that before proceeding further. https://w3c.github.io/resource-timing/#sec-privacy-security - Please point to the results of your own self-review (see https://w3ctag.github.io/security-questionnaire/ , https://w3c.github.io/fingerprinting-guidance/, https://tools.ietf.org/html/rfc6973) https://w3c.github.io/perf-security-privacy/ - Where and how to file issues arising? https://github.com/w3c/resource-timing/issues/ - Pointer to any explainer for the spec? https://w3c.github.io/resource-timing/#introduction Other comments: See https://github.com/w3cping/privacy-request/issues/42 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 June 2021 14:09:13 UTC