-
Notifications
You must be signed in to change notification settings - Fork 8
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
Add guidance on when to use each type #190
Conversation
<li>Who is the author of this schema? (provided by the <code>issuer</code> property)</li> | ||
<li>Why should the author be trusted for providing this schema? (provided by the <code>evidence</code> property)</li> | ||
<li>Is it schema still in use? (provided by the <code>validFrom</code>, <code>validUntil</code>, and <code>credentialStatus</code> properties)</li> | ||
<li>Has the schema been tampered with? (provided by [[VC-DATA-INTEGRITY]] or [[VC-JWT]])</li> |
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.
Better to refer to the vc specs dir directly.
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.
here? https://w3c.github.io/vc-specs-dir/#proof
I don't see vc-cose-jose
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.
because this has not been merged: w3c/vc-extensions#14
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.
it would be nice to have a single 'securing mechanism' section but I understand why it's not like that
as an alternative could wait until #191 is merged and then link here to the new content integrity protection section
index.html
Outdated
leverage features of the [[VC-DATA-MODEL-2]], answering questions such as: | ||
<ul> | ||
<li>Who is the author of this schema? (provided by the <code>issuer</code> property)</li> | ||
<li>Why should the author be trusted for providing this schema? (provided by the <code>evidence</code> property)</li> |
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.
Do you have an example of using evidence for this?
If not, please remove the evidence link.
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.
removed
index.html
Outdated
<ul> | ||
<li>Who is the author of this schema? (provided by the <code>issuer</code> property)</li> | ||
<li>Why should the author be trusted for providing this schema? (provided by the <code>evidence</code> property)</li> | ||
<li>Is it schema still in use? (provided by the <code>validFrom</code>, <code>validUntil</code>, and <code>credentialStatus</code> properties)</li> |
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.
<li>Is it schema still in use? (provided by the <code>validFrom</code>, <code>validUntil</code>, and <code>credentialStatus</code> properties)</li> | |
<li>Is this schema still valid? (provided by the <code>validFrom</code>, <code>validUntil</code>, and <code>credentialStatus</code> properties)</li> |
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.
done
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.
Assuming some version of change suggestions are applied
fix #173
Preview | Diff