-
Notifications
You must be signed in to change notification settings - Fork 110
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
Should we bundle contexts for credentialSchema and credentialStatus int he v2 core context? #1134
Comments
(Meta comment.) This issue seems to refer to the same underlying question than, for example, issues #1091 or #1090 (I did not do an exhaustive search). That question can be formulated as:
To make it clear, the current context is based on the answer "no". If the answer is "yes", then the v2 context should be significantly pruned, removing the terms listed in the issue title, the terms that are currently defined in other specs or vocabulary, like DI, ODRL, or schema.org specs, and would also lead to the removal of the Note that the question is also closely related to #1103. I would propose to close this issue and open an issue with that question instead. That would also makes it easy to handle #1091 and #1090 (and possibly others). |
Noting the current vc json schema does not require context bundling, see https://w3c.github.io/vc-json-schema/ |
@decentralgabe you are volunteered for this. |
Does bundling context meaning adding term definitions for |
The issue was discussed in a meeting on 2023-06-28
View the transcript2.9. Should we bundle contexts for credentialSchema and credentialStatus int he v2 core context? (issue vc-data-model#1134)See github issue vc-data-model#1134. Brent Zundel: #1134 - orie? Orie Steele: have already merged pull request to merge RDF classes to Manu Sporny: should bundle this. This will make developer lives easier. Brent Zundel: looks like this is before CR.
Orie Steele: volunteers Gabe ;-). Gabe Cohen: will be take it on. |
@decentralgabe yes, assume W3C will define the URLs for them, same as it did for "VerifiableCredential". |
The argument for doing so is that they are used by data integrity proofs, and this would make things easier for developers.
If we don't do this, we should make sure to include normative guidance on adding context values to the context array when these features are used, to avoid confusion regarding term definitions.
The text was updated successfully, but these errors were encountered: