-
Notifications
You must be signed in to change notification settings - Fork 109
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
Vocabulary fixes — replacement of #1241 #1253
Conversation
This PR does not include the correction to credential graph. A credential graph is not a credential. |
The vocabulary file on the
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@iherman should this include w3c/vc-json-schema#206 as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@iherman can you please update the label for this section of the vocabulary? That is the change that is not carried over from the previous PR
Similarly for the credential graph label... The labels should distinguish the concepts. It's not helpful to call everything simply a "verifiable credential"... When it could be a set of separate credential graphs or a Verifiable Credential that is not a Verifiable Credential Graph. |
Oops, sorry. I mixed it up. Done. |
I do not understand what you want to say. Is there a change you propose in the vocab file? If so, can you put that explicitly in the comment? |
@@ -163,7 +171,7 @@ property: | |||
|
|||
- id: verifiableCredential | |||
defined_by: https://www.w3.org/TR/vc-data-model-2.0/#defn-verifiableCredential | |||
label: Verifiable credential | |||
label: Verifiable credential graph |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this was the change I was looking for.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@iherman I was doing code reviews from my phone, its possible I missed this in your original PR.
The general comment was to address the labels and try to provide unique language that distinguished all the various "verifiable credential" labels.
It seems like my feedback has been addressed.
I agree with the discussion in the 2023-08-22 meeting that this PR is substantially similar to @iherman's earlier PR and so should inherit that PR's approvals. |
Normative, multiple reviews, changes requested and made, no objections, merging. |
This is actually a replacement of #1241 : it includes all the changes in there, plus the missing pieces in #1241 (comment).
Making PR on top of #1241 would have led to problems because, in the meantime, the main branch has changed too much (e.g., the diagrams have been added), so it was simpler to create a PR on top of
main
rather thanfix/vocab-issues