Rename "claim" to "credentialSubject" #277
Merged
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
|
I am happy for either term to be used, either subject or credentialSubject, because the semantics of both are clear to me |
dlongley
approved these changes
Nov 15, 2018
There was a problem hiding this comment.
I think this is a good change (as explained in #207). I would prefer consistency so that we either use issuer and subject in the JSON or credentialIssuer and credentialSubject, with a slight preference for the shorter variant, but otherwise no complaints from me. Approving -- as we can bikeshed names later.
Closed
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 renames
claimtocredentialSubjectand removes the@graphcontainer from claim.Preview | Diff