Closed msporny closed 1 month ago
Manu, is this a step toward a later subset of DID Extensions that includes those that are widely implemented (i.e., show serious adoption, or are otherwise demonstrably well tested)?
+1 to VC Extensions
The issue was discussed in a meeting on 2024-08-21
@longpd wrote:
Manu, is this a step toward a later subset of DID Extensions that includes those that are widely implemented (i.e., show serious adoption, or are otherwise demonstrably well tested)?
Hrm, no, I don't think so. DID Extensions and VC Extensions are two different lists of specifications with no expectation of overlap.
Done in 20da204b0b6474fe478be76ae68560d267fe52a6.
I'm going to leave this PR open until the full rename/redirect happens.
@iherman I've also renamed everything I can in https://github.com/w3c/vc-extensions ... please set up the appropriate /TR/ redirects.
+1 to this change
The issue was discussed in a meeting on 2024-08-28
@msporny,
Done in 20da204.
I'm going to leave this PR open until the full rename/redirect happens.
@iherman I've also renamed everything I can in https://github.com/w3c/vc-extensions ... please set up the appropriate /TR/ redirects.
I cannot set up such redirections in /TR. I believe what this requires is a new formal publication of the NOTE as if it was a new one, and noting in the republication request that this is, in fact, an old Note renamed. (I suspect there is a need for a formal request because this means a new short name for a TR document.) The Webmaster has the right and the tools to do the redirections at the time of the publication. @deniak, is that correct, or can you simply publish a new version without the formal decision of PlH and Yves involved?
Note, however, that with that change, the reference to the old editor's draft (https://w3c.github.io/vc-specs-dir/) has become a 404; I am not sure whether something can be done about that. We could have chosen to leave the GitHub repository name intact. But I guess that is too late.
I have prepared a publication request admin text in https://github.com/w3c/verifiable-credentials/blob/main/admin/NOTE-vc-extensions-Sep-2024/Approval_request.md; please check it whether it is all right (if it is necessary, that is).
To follow traditions, you should also create and store in the repository the final, static version of the document that I could put to our server. Do not forget to run the document through pubrules' and link checker. Hopefully the date of next Tuesday will work (these formal W3C decisions are usually taken on Fridays).
cc-ing @deniak to see if I miss something.
The issue was discussed in a meeting on 2024-09-11
@iherman wrote:
I have prepared a publication request admin text in https://github.com/w3c/verifiable-credentials/blob/main/admin/NOTE-vc-extensions-Sep-2024/Approval_request.md; please check it whether it is all right (if it is necessary, that is).
I have reviewed the request, it looks good to me.
To follow traditions, you should also create and store in the repository the final, static version of the document that I could put to our server.
Done:
https://github.com/w3c/vc-extensions/tree/main/NOTE/2024-09-17
Alas! :-(
We have gone through that nightmare before, I just realized, and it is even more complicated than that: https://github.com/w3c/vc-jose-cose/pull/126#issuecomment-1638135172. Sorry for missing that:
All this cannot be done this week. As I told you on the call, this is to be done after TPAC. Also, you should not use directories with exact dates in the repository, those dates almost never go the first round...
P.S. Let us try to avoid such repository/short name changes. It is an admin nightmare!
All is well that ends well:-) The approval for the new short name came quicker than expected, and the publication for the new document has also been speeded up. The only remaining step is to set up echidna for the new repository, see https://github.com/w3c/vc-extensions/pull/40. Once that PR is merged, this issue can be closed.
The PR to update Echidna (https://github.com/w3c/vc-extensions/pull/40) has been merged.
https://www.w3.org/TR/vc-extensions/ is now live and healthy.
Hooray!
Thank you @iherman and @deniak!
Closing as resolved.
The DID WG recently resolved to rename the "DID Specifications Registries" to "DID Extensions". This group should consider renaming the "VC Specifications Directory" to "VC Extensions". Doing so avoids the "registry vs. directory" debate and makes it more apparent what the document is about. We would, of course, keep the notion that the list of extension specifiations are not some sort of "official" list but rather, just a collection of extensions that specification authors have decided to include in the list of extensions.