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

Add examples of validating VC-JWT and Linked Data Proof credentials #143

Open
decentralgabe opened this issue May 12, 2023 · 2 comments
Open
Assignees
Labels

Comments

@decentralgabe
Copy link
Collaborator

See title

@iherman
Copy link
Member

iherman commented Jan 29, 2025

The issue was discussed in a meeting on 2025-01-29

  • no resolutions were taken
View the transcript

2.11. Add examples of validating VC-JWT and Linked Data Proof credentials (issue vc-json-schema#143)

See github issue vc-json-schema#143.

Brent Zundel: We are currently in CR with this.
… Currently assigned to someone not actively participating. Hopefully Mahmoud can pick this up.
… Post-CR is now. Future is for another group in the future.

Ivan Herman: +1 for one of each.

Dave Longley: +1 to one of each being sufficient.

Brent Zundel: When this was raised, we weren't fully stable with VC-JWT and Linked Data Proofs. They are now stable, and so this becomes actionable.

Mahmoud Alkhraishi: How do we find the keys used?

Brent Zundel: I'm not aware of any ways of finding these keys. So using your own setup is fine.

Ivan Herman: +1.

Brent Zundel: Thank you Mahmoud for stepping forward to work on this.

Mahmoud Alkhraishi: thank you!

@iherman
Copy link
Member

iherman commented Feb 19, 2025

The issue was discussed in a meeting on 2025-02-19

  • no resolutions were taken
View the transcript

1.6. VC JSON SCHEMA.

Brent Zundel: been finished for a long time now. Two PRs are maintenance ones, and a single issue (143) that should have a PR raised ASAP.

See github issue vc-json-schema#143.

Brent Zundel: but the PR should be only editorial.

Dave Longley: +1 to mark as future.

Brent Zundel: or I can mark the issue as Future.

Manu Sporny: please mark it is Future now.

Brent Zundel: the implementation report is completely empty, so this is a major problem. Means we cannot transition this doc to PR.

Ivan Herman: we can publish this doc later if we find implementations later. Unlike JOSE-COSE which is more critical to the whole group of specs.

Manu Sporny: +1 to delay transition to Proposed Recommendation for VC JSON Schema... we can always do it later, not pushing it to Proposed Rec it isn't going to blow anything up, AFAICT.

Dave Longley: +1 to delay and transition with the other specs later.

Brent Zundel: proposal is to remove JSON schema from transition request.
… since no objections this is what we will do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants