vc-api
vc-api copied to clipboard
w3c-ccg
An HTTP API for performing credential lifecycle management for Verifiable Credentials.
Hi, I am curious if there is a reason why the `404 Not Found` response is not listed for example for https://w3c-ccg.github.io/vc-api/#continue-exchange endpoint at all? It would be a very...
Adding the `returnPresentation` option to presentation/verify. Implements #207 . In order to do this, separated out `VerifyPresentationOptions` and `VerifyCredentialResult` because credential has `verifiedCredential` and presentation has `verifiedPresentation`.
Updates all references from proving a presentations to become creating a presentations. Changes endpoint from POST `presentations/prove` to POST `presentations` *** Preview | Diff
TLDR; how can the vc-api distinct generic verification from verifier specific validations operations on a VC? A quick glance at the term verify could imply that there is a True...
I apologize if this topic has already been covered or if there are any misunderstandings, but I'm finding it a bit challenging to grasp the underlying reasoning behind the specifications...
It was raised that we would need to clarify why/how VC API is different from OID4, namely that it's largely used for back-end credential management, machine-to-machine/unattended server-to-server workflows (with some...
How should the current response format for the above endpoints `{checks, warnings, errors}` be restructured to contain some variant of `challengeVerificationMetadata: {uses, verified, firstVerified}`?
Can credential contain the proof property already when issuing a credential?
coming out of #373 Should we have a section that outlines how challenges are expired? some ideas discussed on the call: 1. We can have an expiry time returned at...
The Traceability work item has the concept of `/presentations/available` on a Verifier Coordinator, the group should explore if we the same concept should be adopted/generalized in the VC API. These...