From 670618095e3f29a81ecf0d30d6058a7cfe3c93ac Mon Sep 17 00:00:00 2001 From: Rasmus Dahlberg Date: Tue, 8 Feb 2022 14:15:50 +0100 Subject: persisted pads from meeting minutes --- doc/proposals/2022-02-end-user-terminology.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 doc/proposals/2022-02-end-user-terminology.md (limited to 'doc/proposals') diff --git a/doc/proposals/2022-02-end-user-terminology.md b/doc/proposals/2022-02-end-user-terminology.md new file mode 100644 index 0000000..9b6df79 --- /dev/null +++ b/doc/proposals/2022-02-end-user-terminology.md @@ -0,0 +1,21 @@ +# Background +We are not entirely happy with the terminology "signer" and "verifier", see +[earlier proposal][] and [meeting minutes][]. At a first glance "author" seemed +like a good abstract description. More work was needed to replace "verifier". + +[earlier proposal]: https://git.sigsum.org/sigsum/tree/doc/proposals/2022-01-author-reader-terminology +[meeting minutes]: https://git.sigsum.org/sigsum/tree/archive/2022-01-18--meeting-minutes + +# Proposal +1. Keep the terminology "signer". +2. Replace "verifier" with "end-user" + +The motivation for keeping "signer" is that it feels natural when we have +conversations about Sigsum. The other natural term for the party which will use +the signed data in the end is "user". We often say "end-user" for emphasis. + +# Notes +Signer will continue to be overloaded. We should be upfront about this where +there is risk for confusion (logs and witnesses are also signers of tree heads). + +Not introducing abstract terminology unless it is needed is likely a win. -- cgit v1.2.3