[a11y-request] Issue: Controllers Documents v1.0 2024-06-02 > 2024-09-02 (#86) marked as REVIEW REQUESTED

msporny has just labeled an issue for https://github.com/w3c/a11y-request as "REVIEW REQUESTED":

== Controllers Documents v1.0 2024-06-02 > 2024-09-02 ==
The Verifiable Credentials Working Group is requesting a review of Controller Documents by the end of summer 2024 (ideally, sooner). Controller Documents are a generalization of DID Documents and some content from VC Data Integrity. All this to say, horizontal review has occurred for most of this content before when it was in DID Core, and then again when it was in  Verifiable Credential Data Integrity. The Working Group recently decided that it would rather have this content in a separate specification than embed it in DID Core or VC Data Integrity, and that specification is Controller Documents v1.0.

- name of spec to be reviewed: [Controller Documents v1.0](https://w3c.github.io/controller-document/)
- URL of spec: https://w3c.github.io/controller-document/

- What and when is your next expected transition?
  - September 2024 (Candidate Recommendation)
- What has changed since any previous review?
  - 90%+ of previous content in DID Core and Data Integrity remains the same. Almost every normative statement remains the same (some language needed to be changed since it's being transplanted from VC Data Integrity).
- Please point to the results of your own self-review
  - https://github.com/w3c/controller-document/issues/23
- Where and how to file issues arising?
  - https://github.com/w3c/controller-document/issues/
- Pointer to any explainer for the spec?
  - [DID Core Explainer](https://github.com/w3c/did-wg/blob/master/did-explainer.md)
  - [Data Integrity Explainer](https://github.com/w3c/vc-data-integrity/blob/main/EXPLAINER.md)
  - Let us know if you would like us to write another explainer for this spec: The spec is basically just "DID Documents, but you can now use other types of URLs in them (like HTTPS-based ones)". The spec exists so we can establish spec text, separate from DID Core and Data Integrity, that we can then normatively reference from other specs in the VCWG that don't have anything to do with DIDs, like generalized public key discovery algorithms.

Other comments:

It is unclear if a11y should spend much time on this specification since it's largely composed of text that has been reviewed by a11y multiple times over the past several years.

See https://github.com/w3c/a11y-request/issues/86


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 3 June 2024 02:00:38 UTC