W3C home > Mailing lists > Public > public-credentials@w3.org > May 2022

Universal signature verifier

From: Julien Fraichot <Julien.Fraichot@hyland.com>
Date: Wed, 4 May 2022 18:01:29 +0000
To: "W3C Credentials CG (Public List)" <public-credentials@w3.org>
Message-ID: <SA1PR13MB5636F01A0803CC868F929C2A90C39@SA1PR13MB5636.namprd13.prod.outlook.com>

I am wondering if similar to the Universal DID Resolver, a Universal Signature Verifier exists?

In my ideal world itd 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 nave 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 18:01:48 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 4 May 2022 18:01:50 UTC