-
Notifications
You must be signed in to change notification settings - Fork 9
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
[WIP] Streamlined Scope #10
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.
This PR is awesome, I left some comments, none of my comments are blocking as this is DIF not W3C or IETF.
Thank you @OR13, this is some excellent feedback! I've got some work to do incorporating it, which might take me a week or so since I'll be out most of this coming week. |
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.
I believe that this PR moves us forward, and so should be merged. That said, I'm fine with another commit being added to address some of the comments made in the PR beforehand.
h/t @OR13 Co-authored-by: Orie Steele <orie@or13.io>
@OR13 I think I've either made some improvements or filed/linked issues for all the feedback and points you raised, if I missed any I'm happy to keep refining too. |
|
||
All of these follow the same pattern of taking multiple claims (a.k.a., "attributes" or "messages" in the literature) and binding them together into an issued credential. These are then later securely one-way transformed into a presentation, revealing potentially only a subset of the original claims as required. | ||
All of these follow the same pattern of taking multiple claims (a.k.a., "attributes" or "messages" in the literature) and binding them together into an issued credential. These are then later securely one-way transformed into a presentation that reveals potentially only a subset of the original claims, predicate proofs of the claim values, or only proofs of knowledge of the claims. |
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.
like this change.
Thanks all for the feedback! |
There are two significant things to note in this PR:
derive
step and "derivation" to theprove
step and generating proofs, to be more consistent with the usage of "proofs" elsewhere in the draft.The result is a simpler spec that focuses strictly on the cryptographic container with pluggable proof algorithms.