- From: Manu Sporny via GitHub <sysbot+gh@w3.org>
- Date: Sun, 21 Jan 2024 22:35:19 +0000
- To: public-web-security@w3.org
msporny has just labeled an issue for https://github.com/w3c/security-request as "REVIEW REQUESTED": == Bitstring Status List v1.0 2024-01-21 > 2023-02-13 == - Name of spec to be reviewed: - Bitstring Status List v1.0 - URL of spec: - https://w3c.github.io/vc-bitstring-status-list/ - Does your document have an in-line Security Considerations section, ideally one separate from the Privacy Considerations? - Yes - What and when is your next expected transition? - Candidate Recommendation, February 2024 - What has changed since any previous review? - This is the first review performed by your group - Please point to the results of your own self-review (see https://w3ctag.github.io/security-questionnaire/) - https://github.com/w3c/vc-bitstring-status-list/issues/77 - Where and how to file issues arising? - https://github.com/w3c/vc-bitstring-status-list/issues - Pointer to any explainer for the spec? - https://github.com/w3c/vc-bitstring-status-list/blob/main/explainer.md ### Other comments: Our apologies, we thought we had submitted this review when we [submitted the TAG review request](https://github.com/w3ctag/design-reviews/issues/874), and when [we did the security and privacy self-review](https://github.com/w3c/vc-bitstring-status-list/issues/77), but we failed to do so. We were hoping to enter CR next month, but are gated by this review (the WG believes it is done enough to enter CR). See https://github.com/w3c/security-request/issues/62 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 21 January 2024 22:35:21 UTC