-
Notifications
You must be signed in to change notification settings - Fork 118
Define v2 context #904
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
Comments
I think the v2 context should look like this to start: {
"@context": {
"@version": 1.1,
"@protected": true,
"id": "@id",
"type": "@type",
"@vocab": "https://www.w3.org/2018/credentials#"
}
} |
The issue was discussed in a meeting on 2022-08-10
View the transcript4.4. Define v2 context (issue vc-data-model#755)See github issue vc-data-model#755.
Kristina Yasuda: I think the previous WG didn't do this because it was a normative change. Orie Steele: We definitely need to start a new version of the context file, so we can make changes to it.. Kristina Yasuda: Is this the right issue to do that?.
Orie Steele: I'm requesting we have a v2 context file. This issue asks the question if we have permission to do that..
Manu Sporny: Short answer is yes we can create a v2 context. We should close the issue since it's misleading what it's asking for. v2 context will happen naturally. If we need an issue for that, we should open a new issue dedicated to this.. See github issue vc-data-model#904. |
Raised PR #905 to address this issue. |
PR #905 has been merged, there is now a base v2 context. Closing. |
What should be in it?
The text was updated successfully, but these errors were encountered: