-
Notifications
You must be signed in to change notification settings - Fork 33
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
Started glossary #74
base: main
Are you sure you want to change the base?
Started glossary #74
Conversation
The table format is great but I worry about introducing an extra set of terms for the common functionality. Since the keys aren't actually used in precisely the same way in each scheme, I think that there's not a precise definition of what each of the new terms are, which makes me worried about introducing them. But the functionality is clearly analogous, so maybe just not including the first column of the table would highlight the similarity without having to define new terms? |
I'm fine with that. I think it would help to be able to refer to it from the high level blocks, so just a numbering for that column? |
Some additional terms
|
Maybe this column should be renamed to "description/definition" and moved to the right side? |
Should we say Token, or Pseudorandom Identifier in the building blocks, to be sufficiently general? |
Maybe "rolling beacon key" is sufficiently non-ambiguous? Why not just use the TCN term, temporary contact number? What's the essence of this term?
Some other ideas:
|
Google has renamed to |
No description provided.