- From: Kerri Lemoie <klemoie@concentricsky.com>
- Date: Fri, 7 Jan 2022 10:53:13 -0500
- To: Julien Fraichot <Julien.Fraichot@hyland.com>
- Cc: "W3C Credentials CG (Public List)" <public-credentials@w3.org>
- Message-Id: <3540CE84-36F6-477A-994A-35B63EE7A856@concentricsky.com>
Hi Julien, You may be interested in this thread: https://lists.w3.org/Archives/Public/public-credentials/2021Dec/0021.html <https://lists.w3.org/Archives/Public/public-credentials/2021Dec/0021.html> K. -------- Kerri Lemoie, PhD Director, Digital Credentials Research & Innovation badgr.com <https://info.badgr.com/> | concentricsky.com <https://concentricsky.com/> she/her/hers > On Jan 7, 2022, at 9:15 AM, Julien Fraichot <Julien.Fraichot@hyland.com> wrote: > > Hi, > > I started exploring options to handle revocation list, and I would like to ideally follow something that has chances to become interoperable (at least on the verification side). > > I am aware of this draft https://w3c-ccg.github.io/vc-status-list-2021/ <https://w3c-ccg.github.io/vc-status-list-2021/> but I am curious if it’s still being worked on and has chances to become an official recommendation? > I see that this draft leaves aside the CRUD aspect of the file, am I then correct to assume that this aspect is left to the implementer to decide? > > Are there other efforts that are/will be researched/pursued on revocation lists? I know some companies/people in this group are also implementing cryptographic accumulators to handle revocation, is that something that could become a recommendation? > > And finally what about more decentralized approaches, ie: smart contract, ipns, etc? Here the question is more generic but are those options that can be considered in relation to the broader VC ecosystem? > > Thanks > > -- > > Julien Fraichot > Developer 4 – Hyland Credentials > > ----------------------------------------- Please consider the environment before printing this e-mail ----------------------------------------- > > CONFIDENTIALITY NOTICE: This message and any attached documents may contain confidential information from Hyland Software, Inc. The information is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or an employee or agent responsible for the delivery of this message to the intended recipient, the reader is hereby notified that any dissemination, distribution or copying of this message or of any attached documents, or the taking of any action or omission to take any action in reliance on the contents of this message or of any attached documents, is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail or telephone, at +1 (440) 788-5000, and delete the original message immediately. Thank you.
Received on Friday, 7 January 2022 15:53:28 UTC