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

Re: VC HTTP API specification structure

From: Adrian Gropper <agropper@healthurl.com>
Date: Fri, 30 Apr 2021 17:42:32 -0400
Message-ID: <CANYRo8jWV2KyWCiRhj+5PTh3O8XV5nsv7ZSFbf+pQ5z-rgn2tQ@mail.gmail.com>
To: Manu Sporny <msporny@digitalbazaar.com>
Cc: W3C Credentials CG <public-credentials@w3.org>

My apologies for missing yesterday's call but I was at 37,000 ft at the
time. I don't see a recording at https://w3c-ccg.github.io/meetings/ - is
there one?

I plan to plead my case in this thread over the next couple of days. For
those that want to get a head start on my perspective, you can see
https://blog.fimbault.com/managing-authorization-grants-beyond-oauth-2 that
briefly mentions the health care use case. Also, the very very drafty
https://github.com/HIEofOne/Trustee-Community/wiki is what I'm hoping to
implement if I can get sufficient help.

FWIW, I have also reached out to the CCG chairs to consider how to discuss
authorization protocols as equally or more important than our focus on


On Fri, Apr 30, 2021 at 5:02 PM Manu Sporny <msporny@digitalbazaar.com>

> Hey Adrian G.,
> A request, please read on...
> The VC HTTP API Task Force has attempted to take up the following
> proposal[1]
> on the last two calls:
> PROPOSAL: Create 1 ReSpec specification in addition to separating the
> existing
> OAS files into modular components.
> You objected the first time, you were not present the second time (so we
> didn't press on since you were the only detractor on the proposal and it
> would
> have been bad form to make a decision when you weren't there). Instead, we
> considered the counter-proposal, which was to split the specification, and
> that resulted in a large and insurmountable number of disapprovals.
> The people that are doing work on this specification need a decision to
> make
> progress.
> To be clear, the details of the proposal are something along these lines:
> There will be a single VC HTTP API specification. The specification will be
> split into a number of sections (by functionality -- issuing, verification,
> etc.), each with a primary Editor in charge of moving that part of the
> specification along. The OAS files will be split up among the same sort of
> lines. We will use ReSpec and automatic processing logic to construct the
> pieces into one whole.
> The VC HTTP API group will be picking up this proposal for the final time
> on
> the next call. We would like explicit agreement or continuing dissent from
> you
> before proceeding. If your response is dissent, the group needs an
> alternative
> proposal that would address your concerns.
> You had requested that whatever the new structure is, that it support your
> healthcare prescription and/or referral use cases. I believe that whatever
> the
> construction of the specification, that those use cases will be possible.
> We
> cannot be certain of it until we have a specification to have a discussion
> around.
> Could you please let us know your current thoughts on the proposal above
> with
> an explicit decision to take back to the group?
> -- manu
> [1]https://w3c-ccg.github.io/meetings/2021-04-22-vchttpapi/#120
> --
> Manu Sporny - https://www.linkedin.com/in/manusporny/
> Founder/CEO - Digital Bazaar, Inc.
> blog: Veres One Decentralized Identifier Blockchain Launches
> https://tinyurl.com/veres-one-launches
Received on Friday, 30 April 2021 21:42:56 UTC

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