New CAIP - Community-Powered Assessment of Trust in Discrete Resources (Split of former: Community-powered trust assessment in software components) #271
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
Update Specification, Add Test Cases, Security Considerations and Privacy Considerations
Co-authored-by: Mircea Nistor <[email protected]>
Change DID specification in order to accommodate any key par based identifier for peers
Setting DIDs for each IDs prevents a malicious actor from "injecting" into the trust computer a credential with a matching ID but referring to something completely different.
Co-authored-by: Mircea Nistor <[email protected]>
Co-authored-by: Mircea Nistor <[email protected]>
…ite-to-generalize Chain agnostic editorial/pr 261 rewrite to generalize
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.
Initial proposal for a data framework to represent assertions for evaluating discrete resources.
This proposal emerges from the division of the original CAIP, specifically CAIP Community-powered trust assessment in software components, into three separate CAIPs for more focused discussions and development:
Feedback and comments from the original discussion on CAIP-261 have been considered and addressed in the development of this new proposal.