aboutsummaryrefslogtreecommitdiff
path: root/doc/proposals/2022-02-end-user-terminology.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/proposals/2022-02-end-user-terminology.md')
-rw-r--r--doc/proposals/2022-02-end-user-terminology.md21
1 files changed, 21 insertions, 0 deletions
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.