- From: Kristina Yasuda <Kristina.Yasuda@microsoft.com>
- Date: Sun, 16 Apr 2023 04:05:12 +0000
- To: Orie Steele <orie@transmute.industries>, Ivan Herman <ivan@w3.org>
- CC: "public-vc-wg@w3c.org" <public-vc-wg@w3c.org>, W3C Chairs of VC WG <group-vc-wg-chairs@w3.org>
- Message-ID: <BN8PR00MB088464CB85AA10C6FF0A1DDDE59FA@BN8PR00MB0884.namprd00.prod.outlook.com>
Ivan, I am confused why the publication date cannot be this Thursday 20th, given there are no changes to the document needed and there is already a WG resolution? Thank you, Kristina ________________________________ From: Orie Steele <orie@transmute.industries> Sent: Saturday, April 15, 2023 10:21 PM To: Ivan Herman <ivan@w3.org> Cc: public-vc-wg@w3c.org <public-vc-wg@w3c.org>; W3C Chairs of VC WG <group-vc-wg-chairs@w3.org> Subject: Re: VC-JWT FPWD Inline: On Sat, Apr 15, 2023 at 2:13 AM Ivan Herman <ivan@w3.org<mailto:ivan@w3.org>> wrote: Orie, thanks. Two comments: 1) I am afraid Apr 20 as a publication date is not possible. Indeed, the process is as follows 1. The WG officially decides This has already happened, per the resolution https://www.w3.org/2017/vc/WG/Meetings/Minutes/2023-03-22-vcwg#resolution3 Regardless, I have gone ahead and made the change to the 27th as you have requested. 1. I push the copy of the document to www.w3.org/TR/2023/.<http://www.w3.org/TR/2023/>.. Your action, after the PR is merged? 1. I create an official publication request and submit it to the "Director" (using the term in the earlier incarnation of W3C, today it will have another name) 1. The "Director" (officially) approves 2. I send an official publication request to the w3c webmaster 3. The webmaster does the publication There are two time constraints in this workflow: * step (6) happens on Tuesdays and Thursdays. Personally, I prefer Thursdays because officially I am off on Mondays, and it is good if I am around if there are some last minutes' bushfires to take care of * on step (4) the "Director" (which means, these days, Philippe le Hégaret and Yves Lafon from the team) have their regular approval meetings on Fridays. Looking at the calendar this means the earliest possible publication date is the 25th, and the preferable (as far as I am concerned) is the 27th. 2) I hope that you did run the snapshot through the checker programs, namely: * https://www.w3.org/pubrules/ (Pub rules checker) * https://validator.w3.org/checklink (Link checkers) Yes, see the results: https://github.com/w3c/vc-jwt/pull/74#issuecomment-1509815598 Ideally, there should be no errors (warnings are fine). There are exceptions that may have to be discussed; e.g., the various references to the HTML spec may return a fragment error, but that is due to the peculiarities of the HTML spec. I fixed a few of these, just to avoid the conversation. Thanks Ivan ---- Ivan Herman, W3C Home: http://www.w3.org/People/Ivan/ mobile: +33 6 52 46 00 43 ORCID ID: https://orcid.org/0000-0003-0782-2704 On 15 Apr 2023 at 01:43 +0200, Orie Steele <orie@transmute.industries>, wrote: Hello, VC-JWT Editors discussed the current state of the document and we feel it is ready for FPWD. I have prepared this pull request: https://github.com/w3c/vc-jwt/pull/74 @Ivan Herman<mailto:ivan@w3.org> Is there anything else you need me to do? Regards, OS -- ORIE STEELE Chief Technical Officer www.transmute.industries [https://drive.google.com/a/transmute.industries/uc?id=1hbftCJoB5KdeV_kzj4eeyS28V3zS9d9c&export=download]<https://www.transmute.industries/> -- ORIE STEELE Chief Technical Officer www.transmute.industries [https://drive.google.com/a/transmute.industries/uc?id=1hbftCJoB5KdeV_kzj4eeyS28V3zS9d9c&export=download]<https://www.transmute.industries/>
Received on Sunday, 16 April 2023 04:05:32 UTC