Re: Bikeshed: Renaming the VC HTTP API

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