-
Notifications
You must be signed in to change notification settings - Fork 13
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
Glossary Terms #113
Glossary Terms #113
Conversation
@@ -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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hard to know how general we want to go with the terms. there are pros and cons to creating a long/thorough list
Signed-off-by: 2byrds <[email protected]> Signed-off-by: Darrell O'Donnell <[email protected]>
Signed-off-by: 2byrds <[email protected]> Signed-off-by: Darrell O'Donnell <[email protected]>
Signed-off-by: 2byrds <[email protected]> Signed-off-by: Darrell O'Donnell <[email protected]>
Signed-off-by: 2byrds <[email protected]> Signed-off-by: Darrell O'Donnell <[email protected]>
Signed-off-by: Darrell O'Donnell <[email protected]>
Signed-off-by: Darrell O'Donnell <[email protected]>
Signed-off-by: Darrell O'Donnell <[email protected]>
Signed-off-by: Darrell O'Donnell <[email protected]>
Signed-off-by: Charles Lanahan <[email protected]> Signed-off-by: Darrell O'Donnell <[email protected]>
Small grammatical changes. Signed-off-by: Charles Lanahan <[email protected]> Signed-off-by: Darrell O'Donnell <[email protected]>
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 <[email protected]> Signed-off-by: Darrell O'Donnell <[email protected]>
Signed-off-by: 2byrds <[email protected]> Signed-off-by: Darrell O'Donnell <[email protected]>
Signed-off-by: 2byrds <[email protected]> Signed-off-by: Darrell O'Donnell <[email protected]>
Signed-off-by: Charles Lanahan <[email protected]> Signed-off-by: Darrell O'Donnell <[email protected]>
f22bd59
to
7a4c693
Compare
Updated to include DCO sign-off. |
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 has agied out enough that there are substantial conflicts with ongoing work. I will create a new PR.
killing this PR off. Will rebase and create a new PR. |
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-up
was added topackage.json
andpackage-lock.json
. I think that is ok, but I was surprised that it wasn't already there.