Issues: w3c-ccg/vc-api
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Update OAS to latest version
ready for PR
Issue ready to be resolved via a Pull Request
#385
opened May 14, 2024 by
msporny
proposition to follow rfc9457 for API errors
ready for PR
Issue ready to be resolved via a Pull Request
#383
opened May 14, 2024 by
lemoustachiste
Change Issue ready to be resolved via a Pull Request
verifiedCredential
to credential
for symmetry
ready for PR
#381
opened Apr 16, 2024 by
dlongley
Update issue end point to support selective disclosure mandatory option
#364
opened Jan 30, 2024 by
Wind4Greg
Update derive endpoint for compatibility with current selective disclosure specifications
#363
opened Jan 30, 2024 by
Wind4Greg
Clarify how VC API is different from OID4
ready for PR
Issue ready to be resolved via a Pull Request
#344
opened Aug 29, 2023 by
msporny
Clarification on endpoints style for issuance , verification and derivation
ready for PR
Issue ready to be resolved via a Pull Request
#343
opened Aug 16, 2023 by
jruizaranguren
Clarify error response code design in spec
ready for PR
Issue ready to be resolved via a Pull Request
#340
opened Mar 21, 2023 by
msporny
Add clarifying statements about VC API Workflows (and exchanges)
ready for PR
Issue ready to be resolved via a Pull Request
#338
opened Mar 14, 2023 by
msporny
Can issue credential request credential proof property
ready for PR
Issue ready to be resolved via a Pull Request
#337
opened Feb 24, 2023 by
acarnagey
Define extensibility rules for VC API endpoint options
ready for PR
Issue ready to be resolved via a Pull Request
#335
opened Jan 31, 2023 by
msporny
Specify how error details are returned
ready for PR
Issue ready to be resolved via a Pull Request
#331
opened Jan 10, 2023 by
msporny
Question about IssueCredentialOptions and VerifyOptions
ready for PR
Issue ready to be resolved via a Pull Request
#318
opened Oct 21, 2022 by
tsnyder-gs1us
Ensure exchanges payloads use top-level JSON properties and use POST method
ready for PR
Issue ready to be resolved via a Pull Request
#311
opened Oct 18, 2022 by
dlongley
Clarification of Issue ready to be resolved via a Pull Request
GET /credentials
endpoint
ready for PR
#302
opened Aug 31, 2022 by
kezike
What does the Exchanger Service do and who uses it?
ready for PR
Issue ready to be resolved via a Pull Request
#298
opened Jul 18, 2022 by
msporny
Should the VC API support callbacks?
ready for PR
Issue ready to be resolved via a Pull Request
#295
opened Jul 11, 2022 by
msporny
API endpoints MUST specify the component (Issuer App, Issuer Service, etc.)
ready for PR
Issue ready to be resolved via a Pull Request
#285
opened Apr 14, 2022 by
jandrieu
Does verifying a presentation include verifying its VCs?
ready for PR
Issue ready to be resolved via a Pull Request
#284
opened Apr 14, 2022 by
jandrieu
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.