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

Re: Merging vc-issuer and vc-verifier apis

From: Leonard Rosenthol <lrosenth@adobe.com>
Date: Tue, 14 Jul 2020 11:52:21 +0000
To: Kim Hamilton <kimdhamilton@gmail.com>, Manu Sporny <msporny@digitalbazaar.com>
CC: "W3C Credentials CG (Public List)" <public-credentials@w3.org>
Message-ID: <110BF7FD-68ED-4165-B690-C473F4BC287C@adobe.com>
Thanks to you and Manu for the clarification!

Leonard

From: Kim Hamilton <kimdhamilton@gmail.com>
Date: Monday, July 13, 2020 at 9:00 PM
To: Manu Sporny <msporny@digitalbazaar.com>
Cc: "W3C Credentials CG (Public List)" <public-credentials@w3.org>
Subject: Re: Merging vc-issuer and vc-verifier apis
Resent-From: <public-credentials@w3.org>
Resent-Date: Monday, July 13, 2020 at 8:58 PM

I meant to address this by #2 (saying that the baseline spec has those contents), but failed to mention it will be a ccg repo. I think the addition (in bold) gets it to the state I intended.

1. Combine vc-issuer-http-api[1] and vc-verifier-http-api[2] into 1 w3c-ccg repo called vc-http-api
2. Update new baseline spec to these contents: https://transmute-industries.github.io/vc-http-api/<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftransmute-industries.github.io%2Fvc-http-api%2F&data=02%7C01%7Clrosenth%40adobe.com%7C0d61667f58ff4aa3e17508d827915336%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302852421127685&sdata=H5v7QEstg6i%2BzxporpKYJqfkSilOFTtuimmPWMkf3s8%3D&reserved=0>
3. Update the accounting on the CCG work items page[3] to reflect 1 work item instead of 2.

On Mon, Jul 13, 2020 at 5:25 PM Manu Sporny <msporny@digitalbazaar.com<mailto:msporny@digitalbazaar.com>> wrote:
On 7/13/20 5:14 PM, Leonard Rosenthol wrote:
> Kim – will you be moving the newly combined work to a wc3-ccg page?
> Hosting it in some other repo seems wrong (and potentially
> problematic from an IP perspective).

Yes, I believe not mentioning that we'll move the repo at Transmute into
the W3C CCG's purview was an oversight. All official CCG work items end
up in the CCG's Github repo, usually sooner than later, and often when a
proposal to adopt/merge reaches consensus (which should happen after the
call tomorrow, unless someone objects).

-- manu

--
Manu Sporny - https://www.linkedin.com/in/manusporny/<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linkedin.com%2Fin%2Fmanusporny%2F&data=02%7C01%7Clrosenth%40adobe.com%7C0d61667f58ff4aa3e17508d827915336%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302852421137672&sdata=oyXfy1WsT8OdW3GeT3Aq5Wv3nccbtnl1IsBynOA%2BVW8%3D&reserved=0>
Founder/CEO - Digital Bazaar, Inc.
blog: Veres One Decentralized Identifier Blockchain Launches
https://tinyurl.com/veres-one-launches<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftinyurl.com%2Fveres-one-launches&data=02%7C01%7Clrosenth%40adobe.com%7C0d61667f58ff4aa3e17508d827915336%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302852421137672&sdata=d168ZZaGhyk%2FQ2rljmiVWMhCRqGFW83Dv3hZ2I9Xt%2Fo%3D&reserved=0>

Received on Tuesday, 14 July 2020 11:52:45 UTC

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