Skip to content
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

Propose RFC 0428: Prerequisites to Issue Rich Credential #428

Merged
merged 24 commits into from Jun 2, 2020

Conversation

brentzundel
Copy link
Member

Rich schema prerequisites for issuance of credentials.
Signed-off-by: Brent brent.zundel@gmail.com

@brentzundel
Copy link
Member Author

@ashcherbakov please let us know what you think of this.

Signed-off-by: Brent <brent.zundel@gmail.com>
Signed-off-by: Brent <brent.zundel@gmail.com>
features/0428-prepare-issue-rich-credential/README.md Outdated Show resolved Hide resolved
is already present.
1. If not, the issuer checks the ledger to see if the schemas he wants to
use are already present.
1. If not, anchor the context used by each schema to the ledger.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we clarify what we mean by anchoring here? Is it writing the full schema/mapping's content to the ledger, or just an anchor/digital_fingerprint/hash of the full content?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think whether the full contents of the schema/mapping should be on the ledger versus a digital hash is determined by the user's trust model, so both should be allowed. I think using the more generic term anchor allows for either interpretation.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree as we are talking about an Aries RFC here.
Once we write a ledger-specific RFC (Indy HIPE for example), then we may need to clarify the anchoring term in terms of supported transactions there.

brentzundel and others added 16 commits February 24, 2020 15:03
Co-Authored-By: ashcherbakov <alexander.sherbakov@dsr-company.com>
Signed-off-by: Brent <brent.zundel@gmail.com>
Signed-off-by: ashcherbakov <alexander.sherbakov@dsr-corporation.com>
Signed-off-by: ashcherbakov <alexander.sherbakov@dsr-corporation.com>
Signed-off-by: ashcherbakov <alexander.sherbakov@dsr-corporation.com>
Signed-off-by: ashcherbakov <alexander.sherbakov@dsr-corporation.com>
Signed-off-by: ashcherbakov <alexander.sherbakov@dsr-corporation.com>
Signed-off-by: ashcherbakov <alexander.sherbakov@dsr-corporation.com>
Signed-off-by: ashcherbakov <alexander.sherbakov@dsr-corporation.com>
Signed-off-by: ashcherbakov <alexander.sherbakov@dsr-corporation.com>
Signed-off-by: ashcherbakov <alexander.sherbakov@dsr-corporation.com>
Signed-off-by: Timo Glastra <timo@glastra.me>
Signed-off-by: Timo Glastra <timo@glastra.me>
Signed-off-by: Timo Glastra <timo@glastra.me>
Signed-off-by: Timo Glastra <timo@glastra.me>
Signed-off-by: Timo Glastra <timo@glastra.me>
Signed-off-by: ashcherbakov <alexander.sherbakov@dsr-corporation.com>
Signed-off-by: Daniel Hardman <daniel.hardman@gmail.com>
@dhh1128 dhh1128 merged commit 01ee66d into hyperledger:master Jun 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants