W3C home > Mailing lists > Public > public-credentials@w3.org > July 2021

Re: VC-HTTP API Use Case for Audit / Notary

From: Mike Prorock <mprorock@mesur.io>
Date: Tue, 6 Jul 2021 10:43:21 -0400
Message-ID: <CAGJKSNTzFZdkfXGqHz+=ANpaqTwxYo-kxbaHA9QxL3sWFWu1BQ@mail.gmail.com>
To: Manu Sporny <msporny@digitalbazaar.com>
Cc: W3C Credentials CG <public-credentials@w3.org>
>
> I strongly suggest that we put it out of scope for the VC HTTP API for at
> least the next 6-9 months.

+1

Audit functionality is hugely important, but with current scope and state
of VC-HTTP-API I am not seeing it as something that we would want to tackle
as part of base VC-HTTP-API implementations on the mesur.io side for now.

Mike Prorock
CTO, Founder
https://mesur.io/



On Tue, Jul 6, 2021 at 10:36 AM Manu Sporny <msporny@digitalbazaar.com>
wrote:

> On 7/3/21 6:13 PM, Adrian Gropper wrote:
> > Audit should be in scope as we work on VC-related protocols.
>
> Yes, audit should be a consideration in the VC ecosystem.
>
> However, the diagram you provided doesn't seem to touch the VC HTTP API at
> all. Audit seems like it has nothing to do with the VC HTTP API at present,
> and we should keep it out of scope until we have the base layer of the API
> handled.
>
> It's going to be very difficult to argue that auditing is as foundational
> as
> issuing, holding, or verifying.
>
> I strongly suggest that we put it out of scope for the VC HTTP API for at
> least the next 6-9 months.
>
> -- 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 Tuesday, 6 July 2021 14:43:45 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:25:18 UTC