Add note specifying that issuer might be different for status lists. #103
Conversation
This file contains 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
davidlehn,
dlongley,
jandrieu,
longpd,
iherman,
dmitrizagidulin,
andresuribe87,
TallTed,
David-Chadwick,
decentralgabe,
brentzundel,
KDean-GS1 and
seabass-labrax
dlongley
approved these changes
Dec 27, 2023
David-Chadwick
approved these changes
Dec 28, 2023
longpd
approved these changes
Dec 28, 2023
Co-authored-by: David Chadwick <[email protected]>
TallTed
reviewed
Dec 28, 2023
Co-authored-by: Ted Thibodeau Jr <[email protected]>
TallTed
reviewed
Dec 28, 2023
index.html
Outdated
Comment on lines
760
to
764
| before utilizing the information contained in either credential for further | ||
| decision making purposes. Implementers are advised that the issuers of these | ||
| credential might be different in use cases where the original issuer of the | ||
| <a>verifiable credential</a> does not maintain a record of its validity. | ||
| </p> |
There was a problem hiding this comment.
Suggested change
| before utilizing the information contained in either credential for further | |
| decision making purposes. Implementers are advised that the issuers of these | |
| credential might be different in use cases where the original issuer of the | |
| <a>verifiable credential</a> does not maintain a record of its validity. | |
| </p> | |
| before using the information contained in either credential for further | |
| decision making purposes. Implementers are advised that the issuers of these | |
| credentials might differ, such as when the original issuer of the | |
| <a>verifiable credential</a> does not maintain a record of its validity. | |
| </p> |
KDean-GS1
approved these changes
Jan 3, 2024
|
Editorial, multiple reviews, changes requested and made, 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 attempts to address issue #7 by stating that the issuer of the original VC and the issuer of the status list VC might not be the same entity.
Preview | Diff