Re: [PROPOSED WORK ITEM] Verifiable Issuers and Verifiers

On Fri, Dec 16, 2022 at 4:30 PM Michael Herman (Trusted Digital Web) wrote:
> Manu, what is your working definition of a Verifier?

It's the definition that's specified here:

https://www.w3.org/TR/vc-data-model/#dfn-verifier

Which has been identified as "needing work":

https://github.com/w3c/vc-data-model/issues/983
https://github.com/w3c/vc-data-model/issues/984

> a) A Requesting entity to wants to verify the authenticity of a VC (or VP) it has received? .

Yes, closer to this one above ^^^ than the one below vvv

> b) A Verification Services entity that performs verification services at the request of a Requesting entity?

> The current VC spec is vague/confusing in this regard (and hence, so is this proposed work item).  Often a Bank is used as an example of a Verifier but it is a poor example because a Bank can belong to either or both of the above roles at the same time.

A Bank is a good example of a Verifier, however:

* A Bank might outsource that role to another entity that's acting on
behalf of the bank.

* A Bank might utilize a Verifier Service (as defined by the VC API)
to do the cryptographic verification on the Verifiable Presentation.

* A Bank might utilize a Verifier Coordinator software component to
perform both cryptographic verification and then application of
business rules for the purposes of validation.

So, yes, we should improve the terminology in the VC Data Model
specification, and I believe Reiks will be making a few attempts at
that over the next couple of months. The challenge will be that we
have LOTS of people in the WG now, and so finding a definition that
works for everyone might be challenging.

Hope the above helps.

-- 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/

Received on Friday, 16 December 2022 21:42:52 UTC