-
Notifications
You must be signed in to change notification settings - Fork 22
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
Jargon from VCDM and crypto #62
Comments
Could you point out the other terms that are confusing / jargony? |
You're right Tzviya - I'll take an action to go through and challenge these. I admit I have no idea what pairwise-pseudonymous means. |
@philarcher and I both need to do a full review, keeping this in mind, among other considerations. Some of @TzviyaSiegman's concerns may already have been addressed, but we will look at how to do more. |
@TzviyaSiegman We believe that as this doc has evolved, your initial comment has been addressed. A lot of those jargon words that you rightly pointed out, have been removed or explained. We'll be seeking full review of the doc by the WG imminently so there's ample opportunity for comment and improvement, should you wish to do so. Otherwise, we'll close this issue next week. |
There having been no further comment and, as flagged, the document is now ready for final review by the WG, I'm closing this issue. |
There is A LOT of jargon in this document that comes from the Verifiable Claims Data Model and will be incomprehensible to a layperson. (verifiable credential, issuer, etc). Likewise, there is the assumption that the reader knows enough about cryptography to make sense of terms like "pairwise-pseudonymous". There is a delicate balance between writing use cases that define the spec and writing use cases that convince people who are not yet adopters that they should be. I find the focal use cases especially difficult to parse.
The text was updated successfully, but these errors were encountered: