- From: Joe Andrieu <joe@legreq.com>
- Date: Sun, 19 Oct 2025 06:58:35 -0700
- To: Ivan Herman <ivan@w3.org>
- Cc: Manu Sporny <msporny@digitalbazaar.com>, Dmitri Zagidulin <dzagidulin@gmail.com>, W3C VC Working Group <public-vc-wg@w3.org>, denkenie@gmail.com
- Message-ID: <CAEOiD0HACatoof_3QrGOT0TvJii8kEQfwtDN+OX-A5rCsPLnmw@mail.gmail.com>
Ivan, All three issues have fixes in an updated FPWD at the same URL. I think it should be good to go from me. <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free.www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Sat, Oct 18, 2025 at 11:52 PM Ivan Herman <ivan@w3.org> wrote: > +cc explicitly to the other editor, Denken Chen > > Hi Joe, > > thanks. We are almost there… the draft version is now on the W3C site > > https://www.w3.org/TR/2025/WD-vc-confidence-method-20251030/ > > and I have run the pubrules' checker and link checker on it. There are > three minor issues. > > 1. As you say, the version number has to go to 1.0; I believe this is what > we agreed on. I changed it manually for now, but you should do that in the > sources as well. > > 2. The link checker does not find this fragment link: > > - https://www.w3.org/TR/vc-data-integrity/#verification-method (line > 762) > > I presume the right URL is this: > > - https://www.w3.org/TR/vc-data-integrity/#dfn-verification-method > > but this is something you have to decide. Please update this. > > 3. The w3cid value for Denken (in the header) is 158074. Please change > that; the current value is incorrect and the system complains. > > Also: > > However, I have two gaps: > > 1. The version in the FPWD is 1.0, but the version I have prepared is > still 0.9. I supposed I should update to 1.0, but that wasn't obvious from > the instructions. That's an easy fix. > > > See above. > > 2. I'm not sure how to complete the last request from Ivan, updating > https://github.com/w3c/vc-wg/pull/2/files > > > https://github.com/w3c/transitions/issues/@ISSUE1@ > > Transition approved in: > > > https://github.com/w3c/transitions/issues/@ISSUE1@#issuecomment-@@@@@@@ > > I don't know what to put here. > > > You can safely ignore that, this will be my job. The process is that I > will have to raise a github issue to trigger the approval process (I can > then fill @ISSUE1@) which, eventually, leads to an approval which is > signaled as a comment on that issue (that is the second link). These values > have to be forwarded to the webmaster to process with the final publishing. > None of these are your concern :-) > > Similarly, the sections on IPR commitments and known implementations are > beyond my understanding. Do we have IPR commitments or known > implementations? > > > I believe we agreed that Manu will provide those. > > Thanks! > > Ivan > > > > Please advise. > > On Fri, Oct 17, 2025 at 9:07 PM Ivan Herman <ivan@w3.org> wrote: > >> Thanks, Manu. Just minor adjustments >> >> On 17 Oct 2025, at 21:46, Manu Sporny <msporny@digitalbazaar.com> wrote: >> >> 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 >> >> >> If you have diagrams (SVG or images), please copy them as well. The >> …/FPWD directory must be self-standing, so to say. >> >> 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 >> >> >> There is nothing specifically for editors in that PR (I have changed the >> dated URL-s already). What is missing are the IPR and implementation >> information. >> >> >> 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. >> >> >> As soon as all this is ready, ping me, please. I will have to install a >> copy of your file to the W3C site, something that only W3C team members can >> do. >> >> If there are link errors that are o.k. in your view, please give me your >> arguments; I will have to forward them to the Webmaster in the publication >> request. One typical situation, b.t.w., is that some external URLs hide >> several hops of redirection that the link checker script cannot follow. (It >> does not execute scripts, for example.) One rule of thumb: if you manually >> copy a link to the browser bar, and it works properly, you are o.k. (just >> tell me). >> >> Ivan >> >> >> -- manu >> >> -- >> Manu Sporny - https://www.linkedin.com/in/manusporny/ >> Founder/CEO - Digital Bazaar, Inc. >> https://www.digitalbazaar.com/ >> >> >> >> ---- >> Ivan Herman, W3C >> Home: http://www.w3.org/People/Ivan/ >> mobile: +33 6 52 46 00 43 >> >> >> > > -- > Joe Andrieu > President > joe@legreq.com > +1(805)705-8651 > ------------------------------ > Legendary Requirements > https://legreq.com > > > > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > Virus-free.www.avg.com > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > > > > ---- > Ivan Herman, W3C > Home: http://www.w3.org/People/Ivan/ > mobile: +33 6 52 46 00 43 > > > -- Joe Andrieu President joe@legreq.com +1(805)705-8651 ------------------------------ Legendary Requirements https://legreq.com
Received on Sunday, 19 October 2025 13:58:52 UTC