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

Re: Bikeshed: Renaming the VC HTTP API

From: Wayne Chang <wyc@fastmail.fm>
Date: Tue, 20 Jul 2021 18:51:24 -0400
Message-Id: <0eff46ec-7f5c-4e6b-a47c-e681e4f2d3d2@www.fastmail.com>
To: "=Drummond Reed" <drummond.reed@evernym.com>, "Mike Varley" <mike.varley@securekey.com>
Cc: "Mahmoud Alkhraishi" <mahmoud@mavennet.com>, "Mike Prorock" <mprorock@mesur.io>, "Ted Thibodeau Jr" <tthibodeau@openlinksw.com>, "W3C Credentials CG" <public-credentials@w3.org>
+1 to HAPIness, just because this is a bikeshed thread.

On Tue, Jul 20, 2021, at 6:48 PM, Drummond Reed wrote:
> Beside the credit Mike gets for the most creative sentence in this thread so far, I must admit that "VC-HAPI" is easy to see, say, and spell. And it's technically accurate to boot.
> 
> =Drummond 
> 
> On Tue, Jul 20, 2021 at 3:29 PM Mike Varley <mike.varley@securekey.com> wrote:
>> Instead of HTTP, how about “Web”? VC-WAPI (vic-wapi)____
>> Or we can drop the ‘ttp’ and go for VC-HAPI – (vc-happy)____
>> __ __
>> 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.____
>> __ __
>> MV____
>> __ __
>> *From: *Mahmoud Alkhraishi <mahmoud@mavennet.com>
>> *Date: *Tuesday, July 20, 2021 at 10:08 AM
>> *To: *Mike Prorock <mprorock@mesur.io>, Ted Thibodeau Jr <tthibodeau@openlinksw.com>
>> *Cc: *W3C Credentials CG <public-credentials@w3.org>
>> *Subject: *Re: Bikeshed: Renaming the VC HTTP API____
>> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.____
>> __ __
>> I agree with Michael's point about the audience, this IMO is intended for a technical audience and should therefore make sense to devs.____
>> __ __
>> On the proposed names so far:____
>> __ __
>> +0.8 to VC API --> Nice and simple and wouldn't mind it.
>> +0.7 to VC Storage and Transport API --> No real issues with it it just seems hard to say VCSTAPI doesn't roll of the tongue.____
>> __ __
>> + 1 to VC Exchange ( and to answer Manu's earlier question I think cross-trust boundary exchange would be in scope) --> I personally think this is by far the best name.____
>> __ __
>> Not at all a fan of VC Delivery or including HTTP in the name. we can easily place the restriction to HTTP only in the spec itself.____
>> __ __
>> __ __
>> Regards, ____
>> Mahmoud Alkhraishi____
>> Lead Developer____
>> P: (647) 447-2151____
>> ____
>> 
>> ____
>> 
>> ____
>> 
>> *From:* Mike Prorock <mprorock@mesur.io>
>> *Sent:* Tuesday, July 20, 2021 9:56 AM
>> *To:* Ted Thibodeau Jr <tthibodeau@openlinksw.com>
>> *Cc:* W3C Credentials CG <public-credentials@w3.org>
>> *Subject:* Re: Bikeshed: Renaming the VC HTTP API ____
>>  ____
>> Good points by Ted.  Redundancy in naming is rather irritating. ____
>> __ __
>> Variants of:____
>> "Verified Credentials API"____
>> or____
>> "VC Storage and Transport API"____
>> make sense to me.  ____
>> __ __
>> Non technical decision makers we typically deal with (including in non-tech markets such as Ag) are familiar with the term API as a way for programs to communicate, and if we are specifying an API I am hesitant to remove API from the name, unless we do something like:____
>> __ __
>> "Verifiable Credential Interchange" or "Verifiable Credential Exchange" ____
>> __ __
>> which also seem sane and descriptive to me____
>> ____
>> Mike Prorock ____
>> CTO, Founder____
>> https://mesur.io/____
>> __ __
>> __ __
>> __ __
>> On Tue, Jul 20, 2021 at 9:49 AM Ted Thibodeau Jr <tthibodeau@openlinksw.com> wrote:____
>>> 
>>> On Jul 17, 2021, at 11:45 AM, Manu Sporny <msporny@digitalbazaar.com> wrote:
>>> > Not many are enthused by the name "VC HTTP API"; it doesn't exactly roll off of the tongue. The catch-all term is also confusing debates (again, see the most recent perma-thread about the VC HTTP API).
>>> 
>>> 
>>> As I suggested the other day (https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0111.html) --
>>> 
>>>    VC Storage and Transfer API
>>> 
>>> -- seems appropriate since folks are talking about VCs going 
>>> into Wallets (and similar) as well as VCs being passed from 
>>> Issuer to Holder to Holder to Verifier.
>>> 
>>> For those who like shorter names, VC-STAPI (vee-see-stappy)
>>> doesn't seem bad.
>>> 
>>> 
>>> I also want to discourage any name that combines HTTP with 
>>> Protocol.  It's important to remember that every acronym 
>>> must be expanded at some point, and the "HyperText Transfer 
>>> Protocol ... Protocol" will be sure to get a fair bit of 
>>> notice from the Department of Redundancy Department.  :-)
>>> 
>>> Be seeing you,
>>> 
>>> Ted
>>> 
>>> 
>>> 
>>> 
>>> 
>>> --
>>> A: Yes.                          http://www.idallen.com/topposting.html
>>> | Q: Are you sure?           
>>> | | A: Because it reverses the logical flow of conversation.
>>> | | | Q: Why is top posting frowned upon?
>>> 
>>> Ted Thibodeau, Jr.           //               voice +1-781-273-0900 x32
>>> Senior Support & Evangelism  //        mailto:tthibodeau@openlinksw.com
>>>                              //              http://twitter.com/TallTed
>>> OpenLink Software, Inc.      //              http://www.openlinksw.com/
>>>          20 Burlington Mall Road, Suite 322, Burlington MA 01803
>>>      Weblog    -- http://www.openlinksw.com/blogs/
>>>      Community -- https://community.openlinksw.com/
>>>      LinkedIn  -- http://www.linkedin.com/company/openlink-software/
>>>      Twitter   -- http://twitter.com/OpenLink
>>>      Facebook  -- http://www.facebook.com/OpenLinkSoftware
>>> Universal Data Access, Integration, and Management Technology Providers
>>> 
>>> 
>>> ____
>>> 
>> This email and any attachments are for the sole use of the intended recipients and may be privileged, confidential or otherwise exempt from disclosure under law. Any distribution, printing or other use by anyone other than the intended recipient is prohibited. If you are not an intended recipient, please contact the sender immediately, and permanently delete this email and its attachments.
>> 
Received on Tuesday, 20 July 2021 22:51:59 UTC

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