- From: Orie Steele <orie@transmute.industries>
- Date: Thu, 21 Jul 2022 08:14:24 -0500
- To: Ivan Herman <ivan@w3.org>
- Cc: Manu Sporny <msporny@digitalbazaar.com>, W3C Verifiable Credentials Working Group <public-vc-wg@w3.org>, Dominique Hazaël-Massieux <dom@w3.org>, Ian Jacobs <ij@w3.org>
- Message-ID: <CAN8C-_JagOmBp-reY6=gb-nba1Yep4Rdx=39Vxo9gMKGym-+Lw@mail.gmail.com>
PR for lds-jws2020 - https://github.com/w3c/cg-reports/pull/1 Another first for the W3C! OS On Thu, Jul 21, 2022 at 1:13 AM Ivan Herman <ivan@w3.org> wrote: > Manu, > > W3C has recently set up a process exactly for what you are asking for, ie, > to publish final CG reports at a stable, and easy-to-find place. Here is > what you should look at: > > https://github.com/w3c/cg-reports > > It is, so to say, a TR space for CG reports, with a simple process that > you can follow without the staff contact’s help: you should prepare a PR > for that repo using a naming convention and, once the PR is accepted and > merged, you are done… > > The report will then be published under the URL > > > https://www.w3.org/community/reports/ccg/CG-FINAL-data-integrity-2022-07-22/ > > Please CC me when you do the PR (I am not automatically watching that > repo) . I copy this mail to Dominique and Ian, who have set up this report. > > Cheers, > > Ivan > > P.S. it seems that we will be the guinea pigs for the new setup, but we > seem to have been in such positions for a while, ie, we are getting used to > it… 😀 > > —— > Ivan Herman > +33 652 46 00 43 > > (Written on my iPad. Excuses for brevity and misspellings...) > > On 20 Jul 2022, at 20:03, Manu Sporny <msporny@digitalbazaar.com> wrote: > > Hi all, > > Based on a resolution in the W3C Credentials CG yesterday: > > https://w3c-ccg.github.io/meetings/2022-07-19/#63 > > RESOLUTION: Move forward with Final Community Group Specification > publications > by the Work Item Editors and Transfer all input documents listed in the > VCWG > 2.0 Charter to the VCWG. > > ... I have prepared the W3C Credentials CG FCGS for the Data Integrity > specification: > > https://w3c-ccg.github.io/data-integrity-spec/FCGS/2022-07-22/ > > It looks like every other CCG FCGS specification was published at a > date-stamped URL under W3C-space by W3C Staff: > > https://www.w3.org/2017/05/vc-use-cases/CGFR/2017-05-01/ > https://www.w3.org/2017/05/vc-data-model/CGFR/2017-05-01/ > https://www.w3.org/2019/08/did-20190828/ > > So, we'll need our W3C Staff contact to create one for the data integrity > spec. It looks like the appropriate pattern might be: > > https://www.w3.org/2022/07/data-integrity-20220720/ > > Ivan, the source document can be found here: > > https://github.com/w3c-ccg/data-integrity-spec/tree/main/FCGS/2022-07-22 > > Once that's moved into place, we can push the buttons in the CCG to get the > final IPR commitments from the CCG. > > -- manu > > -- > Manu Sporny - https://www.linkedin.com/in/manusporny/ > Founder/CEO - Digital Bazaar, Inc. > News: Digital Bazaar Announces New Case Studies (2021) > https://www.digitalbazaar.com/ > > > -- *ORIE STEELE* Chief Technical Officer www.transmute.industries <https://www.transmute.industries>
Received on Thursday, 21 July 2022 13:14:49 UTC