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
Global Terminology Overhaul & Some Text Issues #15
Comments
Signed-off-by: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
Here is my opinion: |
It would help to be able to read the document given the changes proposed here. But due to the make errors documented in #6 I haven't yet succeeded in doing so. Does the build infrastructure automatically build documents for other branches? Or can someone else build and publish the document based on this branch? |
Editor's version build via github actions for #16 is located here: https://ietf-wg-scitt.github.io/draft-ietf-scitt-architecture/core-terms/draft-ietf-scitt-architecture.html |
…tf-wg-scitt#16 and ietf-wg-scitt#8 Signed-off-by: steve lasker <stevenlasker@hotmail.com>
Payload and Statement seem to be used intermixed in the text. I tried to disambiguate the via "Statement payload". If that does not work, please provide a counter proposal.
The term Claim sometimes seem to have meant Signed Statement and sometimes Transparent Statement. Using our interim terminology, that became a selection process for me. Please check, if I made the correct choice in all occurrences (sometimes I had to guess the intent).
Consistent Capitalization was a mess. I hope I fixed most of that. Please check.
There is still no consistent use of "Registry" vs. "log" vs. "ledger" vs. "Transparency Service", I think. Please check.
Please check every use of the term "Evidence" and if an alternative expression could be used.
Please check every occurrence of the term "guarantee" or "proof" and if an alternative expression could be used.
Privacy Considerations and Security Considerations texts require significant improvement.
The text was updated successfully, but these errors were encountered: