VC HTTP API Scoping Proposal (starting point)

During the last VC HTTP API call, the group seemed to indicate[1] that it
would like to have a more in-depth scoping discussion during the call this
coming week.

Here is a document that elaborates upon all of the endpoints that are
currently defined, the ones that are likely to become in scope, and the ones
that seemed to have strong agreement to be out of scope (also attached as PDF
and CSV):

https://docs.google.com/spreadsheets/d/1hlevKRxCXsJBWvJTkL30nZVp8cpF26aY3PJqzuHtIZE/edit

These were derived from the use cases document:

https://docs.google.com/document/d/1-u0_Ub6feiX6DH3jXFJFjt6n3CwKGpkmC3VISqDkWL4/edit#heading=h.t03jb3hhyhc2

... the architecture diagrams:

https://w3c-ccg.github.io/vc-http-api/#architecture-overview

... and the current VC HTTP API specification:

https://w3c-ccg.github.io/vc-http-api/issuer.html
https://w3c-ccg.github.io/vc-http-api/holder.html
https://w3c-ccg.github.io/vc-http-api/verifier.html

Here's a concrete proposal:

PROPOSAL: As a starting point, adopt the "In Scope" and "Out of Scope"
classifications for each action listed in
https://docs.google.com/spreadsheets/d/1hlevKRxCXsJBWvJTkL30nZVp8cpF26aY3PJqzuHtIZE/edit
for the VC HTTP API work item. Additional items can be discussed and put in
scope or out of scope on a case-by-case basis.

That this concrete proposal exists shouldn't stop others from making their own
proposals for in scope vs. out of scope features for the VC HTTP API.

-- manu

[1]https://w3c-ccg.github.io/meetings/2021-08-03-vchttpapi/#40

-- 
Manu Sporny - https://www.linkedin.com/in/manusporny/
Founder/CEO - Digital Bazaar, Inc.
News: Digital Bazaar Announces New Case Studies (2021)
https://www.digitalbazaar.com/