-
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
Fix media type registration language #1052
Comments
Keep in mind that we might have an
|
I've said things like this elsewhere, but those seem to be closing with this to track the ongoing, so... I'm fine with one media type being used for both Verifiable and UNverifiable Credentials, and that or another single media type being used for both Verifiable and UNverifiable Presentations. Whether the media type(s) is(are) branded "Verifable" or not, the specified structure should allow for the presence or lack of the proof(s) necessary for that verifiability, which presence or lack is what determines whether the data contained in the structure is or is not verifiable. |
IIRC this has been done, and can be closed. |
The issue was discussed in a meeting on 2023-06-06
View the transcript1.11. Fix media type registration language (issue vc-data-model#1052)See github issue vc-data-model#1052.
Brent Zundel: This looks like it has been addressed, pending close? all: No objections. |
No objections raised since marked |
The media type registration language in the current specification is a bit wonky. It says:
We should be clear if we're talking about "Credentials", "Verifiable Credentials", or "the Verifiable Credential Data Model".
The text was updated successfully, but these errors were encountered: