-
Notifications
You must be signed in to change notification settings - Fork 21
Add expires proof attribute #124
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
Conversation
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.
👍
Thanks for adding this, @Wind4Greg.
(I'm not sure whether we should go so far as to say SHOULD, but this is a step in the right direction).
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.
Agree with @dmitrizagidulin... this shouldn't be a SHOULD, too strong. Suggest that it's OPTIONAL.
Co-authored-by: Manu Sporny <msporny@digitalbazaar.com>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
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.
Note to myself: once #127 and this PR are merged, the new attribute has to be added to the vocabulary.
|
Normative, multiple reviews, changes requested and made, no objections, merging. |
This PR addresses issue #78 by adding the
expiresattribute to the definition of the proof. Note that this term is already defined in the data integrity context.Preview | Diff