Add normative dependency on VC Data Integrity. #993
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
msporny
requested review from
brentzundel,
dlongley,
iherman,
mprorock,
OR13,
peacekeeper and
Sakurann
iherman
approved these changes
Dec 12, 2022
dlongley
approved these changes
Dec 12, 2022
brentzundel
approved these changes
Dec 12, 2022
OR13
approved these changes
Dec 14, 2022
|
The issue was discussed in a meeting on 2022-12-14
View the transcript3.4. Add normative dependency on VC Data Integrity. (pr vc-data-model#993)See github pull request vc-data-model#993. Manu Sporny: PR993 add normative dependency on VC Data Integrity - oks there.. |
|
Normative, multiple reviews, no changes requested, no objections, merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses issue #912 by adding a normative dependency on the VC Data Integrity specification (as requested by @Sebastian-Elfors-IDnow) and adding a line to the revision history for the specification (as requested by @Sakurann). The normative references from the Proof section were added a while ago.
This PR should address issue #912 in its entirety.
Preview | Diff