Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify how VC API is different from OID4 #344

Open
msporny opened this issue Aug 29, 2023 · 3 comments
Open

Clarify how VC API is different from OID4 #344

msporny opened this issue Aug 29, 2023 · 3 comments
Assignees
Labels
ready for PR Issue ready to be resolved via a Pull Request

Comments

@msporny
Copy link
Contributor

msporny commented Aug 29, 2023

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 effort), capable of running OID4* protocols over its exchanges, and not needing existing OID4 infrastructure to operate. VC API defines "primitives behind the scenes" -- for components that can be swapped out for doing entire lifecycle of credential issuance and verification, not strictly focused on deliver/exchange of credentials, it provides components for that process. Delivery/exchange mechanisms are compatible w/ OID4 -- you can use OID4 on top of VC API Exchange to do actual delivery.

@msporny msporny added the ready for PR Issue ready to be resolved via a Pull Request label Aug 29, 2023
@TallTed
Copy link
Collaborator

TallTed commented Aug 29, 2023

Please replace "namely that it's" with "namely that VC API is", and "It defines" with "VP API defines", in the initial comment above.

The antecedent of each is unclear, as the comment stands.

@msporny
Copy link
Contributor Author

msporny commented Mar 12, 2024

The group discussed this on 2024-03-12.

For the PR, we want:

  • A new section titled "Relationship to OID4VCI and OID4VP"
  • The new section should mention that the VC API handles credential lifecycle tasks that issuers, holders, and verifiers need to do beyond just credential pickup and presentation (such as issuing, status list management, holding and deriving, and verification)
  • The VC API also supports OID4VCI and OID4VP, which can be build on top of the workflows and exchanges primitives provided by the VC API. That is OID4* (VCI + VP) are protocols that can be run on top of VC API exchanges, everything else the VC API provides communication between coordinators and services, etc. not communication between digital wallets and issuer/verifiers.

@wes-smith
Copy link
Collaborator

The group discussed this on 2024-04-30.

We noted the relationship to an open PR adding workflow and exchange support, and the PR to resolve this issue should contain a pointer to a section in the above PR explaining the power in VC API exchanges being agnostic to what delivery protocols run on top of them.

@wes-smith wes-smith self-assigned this Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready for PR Issue ready to be resolved via a Pull Request
Projects
None yet
Development

No branches or pull requests

3 participants