Glossary Terms #113
Closed
Glossary Terms #113
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
2byrds
reviewed
Dec 20, 2023
| @@ -55,6 +55,7 @@ | |||
| "merge-stream": "2.0.0", | |||
| "pkg-dir": "4.2.0", | |||
| "prismjs": ">=1.24.0", | |||
| "spec-up": "^0.10.6", | |||
There was a problem hiding this comment.
I don't have experience with spec-up so hopefully others can weigh-in
| * The following set of identifiers are from the current [ToIP Glossary](https://docs.google.com/document/d/1fZByfuSOwszDRkE7ARQLeElSYmVznoOyJK4sxRvJpyM/edit?usp=sharing) (Google Doc). These definitions need to be moved over to the (under development) ToIP Terms tool (aka TEv2). | ||
| * not all ToIP definitions are fully linked here. This whole section is more of an exemplar as of the time of writing. | ||
|
|
||
| [[def: autonomous identifier]] |
There was a problem hiding this comment.
Do you think it would be better to include this term in the list of terms for autonomic identifier (it includes AID, etc) in order to leverage that hover-over text and links.
| [[def: cryptographically verifiable]] | ||
| ~ A property of a data structure that has been digitally signed using a private key such that the digital signature can be verified using the public key. Verifiable data, verifiable messages, verifiable credentials, and verifiable data registries are all cryptographically verifiable. Cryptographic verifiability is a primary goal of the ToIP Technology Stack. | ||
|
|
||
| [[def: identifier]] |
There was a problem hiding this comment.
hard to know how general we want to go with the terms. there are pros and cons to creating a long/thorough list
daidoji
reviewed
Dec 21, 2023
Signed-off-by: 2byrds <2byrds@gmail.com> Signed-off-by: Darrell O'Donnell <darrell.odonnell@continuumloop.com>
Signed-off-by: 2byrds <2byrds@gmail.com> Signed-off-by: Darrell O'Donnell <darrell.odonnell@continuumloop.com>
Signed-off-by: 2byrds <2byrds@gmail.com> Signed-off-by: Darrell O'Donnell <darrell.odonnell@continuumloop.com>
Signed-off-by: 2byrds <2byrds@gmail.com> Signed-off-by: Darrell O'Donnell <darrell.odonnell@continuumloop.com>
Signed-off-by: Darrell O'Donnell <darrell.odonnell@continuumloop.com>
Signed-off-by: Darrell O'Donnell <darrell.odonnell@continuumloop.com>
Signed-off-by: Darrell O'Donnell <darrell.odonnell@continuumloop.com>
Signed-off-by: Darrell O'Donnell <darrell.odonnell@continuumloop.com>
Signed-off-by: Charles Lanahan <charles.lanahan@gmail.com> Signed-off-by: Darrell O'Donnell <darrell.odonnell@continuumloop.com>
Small grammatical changes. Signed-off-by: Charles Lanahan <charles.lanahan@gmail.com> Signed-off-by: Darrell O'Donnell <darrell.odonnell@continuumloop.com>
Small aesthetic changes to some wording. Changed URL for the first link to "DID Method" to reference the definition of did method from the did-core spec. Signed-off-by: Charles Lanahan <charles.lanahan@gmail.com> Signed-off-by: Darrell O'Donnell <darrell.odonnell@continuumloop.com>
Signed-off-by: 2byrds <2byrds@gmail.com> Signed-off-by: Darrell O'Donnell <darrell.odonnell@continuumloop.com>
Signed-off-by: 2byrds <2byrds@gmail.com> Signed-off-by: Darrell O'Donnell <darrell.odonnell@continuumloop.com>
Signed-off-by: Charles Lanahan <charles.lanahan@gmail.com> Signed-off-by: Darrell O'Donnell <darrell.odonnell@continuumloop.com>
darrellodonnell
force-pushed
the
main
branch
from
f22bd59
to
7a4c693
Compare
|
Updated to include DCO sign-off. |
darrellodonnell
commented
Dec 30, 2023
|
killing this PR off. Will rebase and create a new PR. |
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.
I am working to get some closure on definitions and terms that should help simplify a few things. The work is not complete, but this PR starts aims to show what needs to be done (and completes a few things).
One item that popped up as a surprise was that
spec-upwas added topackage.jsonandpackage-lock.json. I think that is ok, but I was surprised that it wasn't already there.