simplify language a little bit #189
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gvelez17
commented
Oct 27, 2023
| @@ -1,5 +1,5 @@ | |||
| # Verifiable Credentials | |||
| Verifiable Credentials are a common feature used by development teams to fulfill a need for tamper-evident claims that can be cryptographically proven to reliably reveal who issued the claim, who (if anyone) is the recipient, the content of the claim itself, and more. | |||
| Verifiable Credentials are a W3C standard used by development teams to fulfill a need for tamper-evident claims that can be cryptographically proven to reliably reveal who issued the claim, who (if anyone) is the recipient, the content of the claim itself, and more. | |||
There was a problem hiding this comment.
not religious about this just thought maybe bring it way up to the top
gvelez17
commented
Oct 27, 2023
| @@ -24,7 +27,7 @@ Since Verifiable Credentials are flexible enough to describe a seemingly limitle | |||
|
|
|||
| **Self-Sovereign Identity (SSI)** | |||
|
|
|||
| Verifiable Credentials contribute to self-sovereign identity in a major way by allowing users to easily prove their identity and share credentials without delegating factors of their identity to some central authority. Developers who allow their users to store their credentials on Ceramic enable their users to retain control and ownership of their data. Since streams in the Ceramic Network can only have one controlling account, each credential saved to Ceramic can only be edited or changed in the future by the users themselves. | |||
| Verifiable Credentials contribute to self-sovereign identity in a major way by allowing users to easily prove their identity and share credentials without delegating factors of their identity to some central authority. Developers who allow their users to store their credentials on Ceramic enable their users to retain control and ownership of their data. Since streams in the Ceramic Network can only be modified by permission of the controller, each credential saved to Ceramic can only be edited or changed in the future by the users themselves. | |||
There was a problem hiding this comment.
bc we do have CACAOs, so the controller can grant permission to someone...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Just wanted to avoid getting dragged into like deep verifiable credential definition discussions, so simplified the explanation of them - see notes