-
Notifications
You must be signed in to change notification settings - Fork 106
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
Migrate Section 6.3.1 JSON Web Token to separate normative specification #880
Comments
PR is up here: w3c/vc-jose-cose#1 |
suggest closing this one once a PR in vc-jwt repository is merged |
The issue was discussed in a meeting on 2022-08-03
View the transcript5.10. Migrate Section 6.3.1 JSON Web Token to separate normative specification (issue vc-data-model#880)See github issue vc-data-model#880. Kristina Yasuda: Not sure if it's done already. Manu Sporny: +1 to that. I think Kristina suggested as much in the last comment on the issue. Michael Jones: I think this is being accomplished by VC-JWT PR 1. Brent Zundel: I will take off the vc-jwt? label. Michael Jones: Maybe reference VC-JWT pull-request 1. See github pull request vc-jwt#1. Brent Zundel: looks like that's in the comment from Orie.
Brent Zundel: After the meeting, anything still labeled "vc-jwt?" will be moved to the vc-jwt repo.. |
This issue should be closed. |
The associated PR has been merged, closing |
The VC2WG is focusing on standardizing a variety of cryptosuites. The VC2WG charter specifically calls out "Cryptosuites for VC-JSON Web Token (JWT)". We should migrate Section 6.3.1 JSON Web Token to a separate normative specification and reduce the section on proof formats to a series of links to the other normative cryptosuite specifications.
The text was updated successfully, but these errors were encountered: