- From: Manu Sporny via GitHub <sysbot+gh@w3.org>
- Date: Sat, 27 May 2023 19:03:19 +0000
- To: public-apa@w3.org
msporny has just labeled an issue for https://github.com/w3c/a11y-request as "REVIEW REQUESTED": == VC Data Integrity (and vc-di-eddsa and vc-di-ecdsa) 2023-05-27 -> 2023-07-31 == - Name of specs to be reviewed: * [Verifiable Credential Data Integrity](https://www.w3.org/TR/vc-data-integrity/) * [EdDSA Cryptosuite v2022](https://www.w3.org/TR/vc-di-eddsa/) * [ECDSA Cryptosuite v2019](https://www.w3.org/TR/vc-di-ecdsa/) - URL of specs: * [Verifiable Credential Data Integrity](https://www.w3.org/TR/vc-data-integrity/) * [EdDSA Cryptosuite v2022](https://www.w3.org/TR/vc-di-eddsa/) * [ECDSA Cryptosuite v2019](https://www.w3.org/TR/vc-di-ecdsa/) - What and when is your next expected transition? - Transition to Candidate Recommendation in September 2023 (at W3C TPAC) - What has changed since any previous review? - There has bee no previous review of these specifications - Please point to the results of your own self-review (see https://w3c.github.io/apa/fast/checklist.html) - https://github.com/w3c/vc-data-integrity/issues/97 - Where and how to file issues arising? - https://github.com/w3c/vc-data-integrity/issues - Pointer to any explainer for the spec? - https://www.w3.org/TR/vc-data-integrity/#introduction Other comments: The three specifications listed above are cryptographic message securing mechanisms and thus do not contain text, visuals, audio, or haptic data that will be experienced directly by a human being. The one exception for this is possibly software developers, who might encounter error messages when using software libraries that implement the specification above. The errors have specific codes, which are internationalizable, but whose internationalization characteristics are up to each implementer. We believe that these specifications, in general, do not create accessibility concerns, but are curious to know if we have overlooked some aspect of how these technologies will be used that will create accessibility issues. See https://github.com/w3c/a11y-request/issues/61 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 27 May 2023 19:03:21 UTC