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
Replace identifier registry with Verifiable data registry. Clarify … #214
Changes from 1 commit
ad99ea9
5b636ac
4d3de55
a19a8f6
4960fa0
9b50608
ba1bb70
2701313
933da47
ac4d89c
070ad77
97e4ea1
9fe7f2a
994abd3
286c8ab
6dea696
2358546
6afbf39
b2ad9cb
e338f5a
96ed437
4cdb01b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -254,11 +254,12 @@ <h3>Ecosystem Overview</h3> | |
<a>verifiable credentials</a> for processing. | ||
Examples of verifiers include employers, security personnel, and websites. | ||
</dd> | ||
<dt><a>identifier registry</a></dt> | ||
<dt><a>Verifiable data repository</a></dt> | ||
<dd> | ||
A role a system may perform by mediating the creation and verification of | ||
<a>subject</a> identifiers. Examples of identifier registries include | ||
corporate employee databases, government ID databases, and distributed ledgers. | ||
Mediates the creation and verification of <a>issuer</a> identifiers, keys and | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The registry is not only for issuers, it's for subjects in general of which issuers are a subtype. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fixed |
||
other relevant data (schemas) required to use verifiable credentials. Examples of | ||
such data repositories include trusted databases, decentralised databases, | ||
government ID databases, and distributed ledgers. | ||
</dd> | ||
</dl> | ||
|
||
|
@@ -580,19 +581,15 @@ <h1>Trust Model</h1> | |
risk assessment of the verifier. | ||
</li> | ||
<li> | ||
All entities trust the <a>identifier registry</a> to be un-corruptible and | ||
to be a correct record of which identifiers belong to which <a>entities</a>. | ||
All entities trust the <a>Verifiable data repository</a> to be un-corruptible and | ||
to be a correct record of which data is owned (and can be updated) by which | ||
<a>entities</a>. | ||
</li> | ||
<li> | ||
The <a>subject</a> trusts the <a>issuer</a> to issue true (i.e. not false) | ||
<a>credentials</a> about the subject, and to revoke them quickly when | ||
appropriate. | ||
</li> | ||
<li> | ||
The <a>holder</a> trusts the <a>repository</a> to store the | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This shouldn't be removed. This is talking about the holder's 'credential repository'... not the cryptographic material registry. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks, added back |
||
<a>credentials</a> securely, to not release them to anyone other than the | ||
<a>holder</a>, and to not corrupt or lose them whilst they are in its care. | ||
</li> | ||
</ol> | ||
|
||
<p> | ||
|
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 should be changed to something like "cryptographic material registry"
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 think schema is not a cryptographic material, neither are identifiers like a DID, do you agree? Can we call it public data regsitry so that it is clear that it contains no holder specific data
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.
@msporny Do you agree?
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.
Public data registry is too vague. Schemas are cryptographic material -- they are used as input to cryptographic functions to perform calculations. Specifically, schemas enable byte streams to be created in a deterministic fashion, so yes, I would classify schemas as cryptographic material for the purposes of the VC Data Model and ecosystem.
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 am re-inclining to Verifiable Data Repository. Verifiable communicates the intent, cryptographic seems like a blanket term. As an example, seed to a PRF is a cryptographic data but not something we want to put in the repository