Re: Merging vc-issuer and vc-verifier apis

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/
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>
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/
> Founder/CEO - Digital Bazaar, Inc.
> blog: Veres One Decentralized Identifier Blockchain Launches
> https://tinyurl.com/veres-one-launches
>
>
>