Re: New Work Item Proposal: VC HTTP API

Hey Orie,

+1 to having both APIs in a single repository.

Just from a process perspective, I just checked, and while the CCG list
of work
<https://github.com/w3c-ccg/community/blob/master/work_items.md>items
<https://github.com/w3c-ccg/community/blob/master/work_items.md> shows
the two current repositories separately, the original proposal
<https://github.com/w3c-ccg/community/issues/102> was for a single work
item.

So I'm simply wondering if we need to formally propose a new CCG work
item and go through that process, or if we could "just do it" and merge
the repos within the existing CCG work item. Joe? Kim? Christopher?

Markus

On 5/5/20 6:58 PM, Orie Steele wrote:
> We propose to merge:
>
> https://github.com/w3c-ccg/vc-verifier-http-api/blob/master/CODEOWNERS
> https://github.com/w3c-ccg/vc-issuer-http-api/blob/master/CODEOWNERS
>
> Into a single repo, modeled
> after: https://github.com/transmute-industries/vc-http-api
>
> We would then move the tests to the repo, which are currently
> here: https://github.com/w3c-ccg/vc-examples/tree/master/plugfest-2020
>
> This is an organization change, to enable us to handle versioning,
> issues, pull requests and contributions faster.
>
> A reminder about these API Specs:
> These APIs are not meant to be consumed directly, they are focused on
> demonstrating interoperability, and implementations need not implement
> all of them in a single server.
> There is a plan to support JWT and ZKPs, in future versions.
> The specifics of how these APIs are supported behind the HTTP
> interface / Authorization are out of scope, and remain out of scope.
>
> Regards,
>
> OS
>
> -- 
> *ORIE STEELE*
> Chief Technical Officer
> www.transmute.industries
>
> <https://www.transmute.industries>