-
Notifications
You must be signed in to change notification settings - Fork 6
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
Editorial changes all through the specification #42
Conversation
Co-authored-by: Orie Steele <orie@or13.io>
|
||
the figure below illustrates the process by which a Wallet Instance |
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.
the figure below illustrates the process by which a Wallet Instance | |
The figure below illustrates the process by which a Wallet Instance |
6. **Real-time validation**: OAuth Status Lists provide the possibility | ||
to do real-time validation of the Digital Credential status. To support |
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.
6. **Real-time validation**: OAuth Status Lists provide the possibility | |
to do real-time validation of the Digital Credential status. To support | |
6. **Real-time validation**: To support |
While this specification does not prescribe any additional methods | ||
for the proof of possession of the Credential, it aims to offer | ||
guidance for concrete implementations utilizing common proof of | ||
possession mechanisms. This includes, but is not limited to: | ||
|
||
1. Having the digital representation of the credential (the bytes). |
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 does not provide a proof of possession. It is only a necessary condition but not sufficient
No description provided.