-
Notifications
You must be signed in to change notification settings - Fork 44
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
Consider allowing a client to request information about an exchange via non-empty post body
#387
opened May 28, 2024 by
dlongley
Require implementations to throw errors if options (post bodies generally) are not understood
#386
opened May 28, 2024 by
dlongley
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
signing VC in sd-jwt format
ready for PR
Issue ready to be resolved via a Pull Request
#357
opened Dec 13, 2023 by
ThierryThevenet
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
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
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
Why don't we just say this API is external and start designing it as such?
ready for PR
Issue ready to be resolved via a Pull Request
#282
opened Apr 8, 2022 by
brianorwhatever
Do the Issue ready to be resolved via a Pull Request
/exchanges/*
endpoints need authz?
ready for PR
#279
opened Mar 30, 2022 by
msporny
Document Instance Configuration in the VC API
ready for PR
Issue ready to be resolved via a Pull Request
#267
opened Feb 23, 2022 by
OR13
The Verification Method of a Revocation List Credential MUST match the issuer of a Revocable Verifiable Credential
blocked-lack-of-get-apis
ready for PR
Issue ready to be resolved via a Pull Request
#264
opened Feb 22, 2022 by
OR13
Should this API define how to host revocation lists?
ready for PR
Issue ready to be resolved via a Pull Request
#232
opened Sep 13, 2021 by
OR13
Define credentialStatus correctly in YAML
ready for PR
Issue ready to be resolved via a Pull Request
#225
opened Aug 3, 2021 by
OR13
Previous Next
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.