- From: Markus Sabadello <markus@danubetech.com>
- Date: Wed, 4 May 2022 21:51:23 +0200
- To: public-credentials@w3.org
- Message-ID: <6cd75c93-19b3-9919-0f68-dec558a9f163@danubetech.com>
Hello Julien, We (Danube Tech) have a "Universal Verifier" here: https://univerifier.io/ But I don't claim that it actually supports all the credential formats and signature suites in existence... Especially considering that at the last Internet Identity Workshop a lot of different formats were identified: https://docs.google.com/document/d/1aNHvPhFv85HHlG8Ry2etrw15KdY830oAL804rMFY9bY/ all the best, Markus On 04.05.22 20:01, Julien Fraichot wrote: > > Hi, > > I am wondering if similar to the Universal DID Resolver, a Universal > Signature Verifier exists? > > In my ideal world it’d be a service to which we can send a VC, and > where the pipeline decides to which Verification Suite to address that > document. Again, ideally most or all of the signature suites defined > here could be verifiable: https://w3c-ccg.github.io/security-vocab > > Maybe this is pretty naïve but it feels that way we could better > support the various signing possibilities, and would alleviate having > to integrate deterministically verification suites into our various > project specific libraries, or having to inject them for verification > (/a la/ vc.js). > > -- > > Julien Fraichot > > Developer – 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 Wednesday, 4 May 2022 19:51:38 UTC