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
Terminology: Registry & Transparency Service #7
Comments
Please look at the existing terminology section before proposing global substitutions. |
The substitution of TS to Transparency Services was due to comments that highlighted a possible confusion with Timestamp that might be not intuitive to the generic reader. Maybe let us split that decision out to the list and then fix this with a %s/foo/bar/g? |
IMO a "Transparency Service" operates a SCITT Registry that contains authenticated statements expressing trust in an artifact. A SCITT Registry may employ multiple technologies to provide its services, i.e. blockchain ledger, relational database, evidence locker, REST API to query the Registry for statements, API's to submit new statements and evidence, etc. The operator of a Transparency Service serves as the Registry Gatekeeper to ensure the integrity of the Registry. |
Adding a link to a higher level overview @raylutz |
Assigning to @raylutz for confirmation and update. |
Copied over from: ietf-scitt/draft-birkholz-scitt-architecture#38
The architecture I-D, and other docs use Registry and Transparency Service (TS) interchangeably.
This issue is about consistent naming, and what we should use for an implementation that hosts the SCITT standards.
As we've discussed various terms, I'm pasting a "thousand words" to highlight conceptual components.
How do we finish this sentence:
The user will submit a signed statement/claim (see issue #34) to the ___
This issue is to discuss what we call (1)
Please "vote" with a comment, representing a number, and any supporting thoughts:
The text was updated successfully, but these errors were encountered: