- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Fri, 17 Oct 2025 15:46:11 -0400
- To: Joe Andrieu <joe@legreq.com>, Dmitri Zagidulin <dzagidulin@gmail.com>
- Cc: W3C Verifiable Credentials Working Group <public-vc-wg@w3.org>
Rough instructions to Editors for preparing a draft to publish as a FPWD: 1. Checkout the repo 2. Create a directory called /transitions/2025/FPWD 3. Change the front-matter of the spec: * specStatus: "FPWD" * publishDate: "2025-10-30" * Update Editors to be you and the others that are confirmed as Editors 4. Generate static copy by previewing spec in your browser, and clicking (top right of page): ReSpec -> Export... -> HTML 5. Copy downloaded file to /transitions/2025/FPWD/index.html 6. Upload index.html to the following W3C Checking tools: * https://validator.w3.org/#validate_by_upload * https://jigsaw.w3.org/css-validator/#validate_by_upload 7. If those pass, commit FPWD/index.html 8. Do linkchecker: https://validator.w3.org/checklink There is a way to run this locally, but you have to install Perl. Provide the published URL to the checklink website after the repo has deployed (wait 3 minutes for it to deploy, you can watch the Github Action execute in the repo if you want): https://w3c.github.io/vc-confidence-method/transitions/2025/FPWD/ Once that's done, do a PR to update the appropriate fields with @@@ in Ivan's PR: https://github.com/w3c/vc-wg/pull/2/files I think that's the rough list, I might have forgotten something... just ping me over the weekend and I can help if I'm around. Put aside 1-2 hours to get through all of it. The worst part is the checklink process if you have broken links. You can also ignore many of the errors because of robots.txt rules. You'll just need to make a judgement call. -- manu -- Manu Sporny - https://www.linkedin.com/in/manusporny/ Founder/CEO - Digital Bazaar, Inc. https://www.digitalbazaar.com/
Received on Friday, 17 October 2025 19:46:51 UTC