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

Re: VC HTTP API specification structure

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Sat, 1 May 2021 22:52:28 -0400
To: W3C Credentials CG <public-credentials@w3.org>
Message-ID: <3fe5b91e-21cc-3d57-2864-c65dd9789e93@digitalbazaar.com>
On 5/1/21 9:48 AM, Adrian Gropper wrote:
> 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.

GNAP and the healthcare use cases you push for have, as far as I can tell,
always been welcome as discussion points in this community...

>> I took Manu's lead (and some slides) to suggest how we might approach SSI
>> protocol design.

Thank you for doing that, Adrian, putting thoughts to paper/presentation is
always helpful.

Having reviewed everything you've sent to the mailing list, and having known
your use cases for quite some time, it is very difficult for me to draw any
coherent line to the proposal under consideration. That is:

PROPOSAL: Create 1 ReSpec specification in addition to separating the existing
OAS files into modular components.

Your arguments are to contemplate certain healthcare use cases (we should),
power dynamics (we should), and philosophies (we should), etc. They have a
part to play in the conversation over the next several months. However, as far
as I can see it, they don't relate to the question at hand in any sort of
direct and actionable way.

Can you please explain to the group how any of what you have shared has to do
with the physical structure of the document that the Editors will need to work
with? Please put these in the form of concrete counter-proposals to the
proposal above. From the slides, what I can gather is:

PROPOSAL: Adopt IETF GNAP terminology for the roles in the VC HTTP API.

PROPOSAL: Define the VC HTTP API as a special case of GNAP.

... but those have almost nothing to do with the structure of the
specification and how we divvy up work.

Please help me understand, as I expect others in the discussion might be
wondering how these things relate to one another.

-- manu

Manu Sporny - https://www.linkedin.com/in/manusporny/
Founder/CEO - Digital Bazaar, Inc.
blog: Veres One Decentralized Identifier Blockchain Launches
Received on Sunday, 2 May 2021 02:52:45 UTC

This archive was generated by hypermail 2.4.0 : Sunday, 2 May 2021 02:52:45 UTC