Re: VC HTTP API Renaming Choices (was: Re: Bikeshed: Renaming the VC HTTP API)

For this naming process to be effective/useful, I believe it's important (maybe it isn't) to have a strong mutual understanding of the "thing" we're trying to name. I don't think we have this consensus.

For example, I haven't seen a answer to the scope of this protocol ...e.g agent-to-storage, agent-to-agent, etc. Note: in the context of this discussion, an HTTP endpoint is a form of agent.

Michael

Get Outlook for Android<https://aka.ms/AAb9ysg>

________________________________
From: Manu Sporny <msporny@digitalbazaar.com>
Sent: Sunday, August 1, 2021 2:37:03 PM
To: public-credentials@w3.org <public-credentials@w3.org>
Subject: VC HTTP API Renaming Choices (was: Re: Bikeshed: Renaming the VC HTTP API)

On 7/20/21 6:27 PM, Mike Varley wrote:
> This vc-wapi is interfering with my waci but not my fapi, gets along pretty
> well with chapi but now I need a gnap. Rar.

Hi all, I've scanned the thread and extracted all the suggestions that I saw:

https://docs.google.com/document/d/10BIb91NgoL_eu3a-4d8FZLcJjtfIg--oRq3VYq1hfK4/edit#

I'm sure I missed a few, please add them to the list. We'll collect more
options for another week and then run a ranked choice vote poll to gather some
data on the community's preferred direction.

If the outcome is something like "Veri McCredentialFace", we'll have to
regroup (and question each of our life choices that led us to that moment).

Please submit any other VC HTTP API renaming options before August 7th 2021 in
the document listed above.

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