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

Re: Attempting to block work (was: Re: VC HTTP Authorization Conversation)

From: Brian Richter <brian@aviary.tech>
Date: Sat, 12 Jun 2021 01:21:44 -0700
Message-ID: <CAPUZd8vTtRyZNm=9BDa3xtpvZ7KehKx3vsS0Ust-DpSN-_na8A@mail.gmail.com>
To: David Chadwick <d.w.chadwick@verifiablecredentials.info>
Cc: "W3C Credentials CG (Public List)" <public-credentials@w3.org>
There aren't that many endpoints in the current spec, let's enumerate them.

Hi, I am Ivan the Issuer, I have 2 endpoints:

   - I will issue a VC
   - I will update a VC

What authorization mechanism do I use?

Hi, I am Veronica the Verifier, I have 2 endpoints:

   - I will verify a VC
   - I will verify a VP

What authorization mechanism do I use?

Hi, I am Hagrid the Holder, I have 4 endpoints:

   - I will derive you a credential
   - I will prove a presentation
   - Tell me a presentation is ready for me
   - Provide me a presentation to store

What authorization mechanism do I use?

I would be interested in implementers answers to the above questions.

- Brian

On Sat, Jun 12, 2021 at 1:05 AM David Chadwick <
d.w.chadwick@verifiablecredentials.info> wrote:

> On 11/06/2021 21:54, Orie Steele wrote:
> The process certainly does not appear to be going super well on this work
> item, but I think a more rigid issue / PR review on calls and more
> debate on email can help with that.
> Perhaps that is because issuer, holder and verifier APIs are all rolled
> into one  HTTP API. If we clearly separate the API services (and
> discussion) into those appertaining to the issuer, holder and verifer APIs,
> then I believe the discussions will be easier to handle.
> Kind regards
> David
Received on Saturday, 12 June 2021 08:23:19 UTC

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