aboutsummaryrefslogtreecommitdiff
path: root/archive/2022-01-18-proposal-author-reader-terminology
diff options
context:
space:
mode:
authorRasmus Dahlberg <rasmus@mullvad.net>2022-01-31 15:36:29 +0100
committerRasmus Dahlberg <rasmus@mullvad.net>2022-01-31 15:36:29 +0100
commitf8d61a93109656e89cbbdeae56ca778127a0eafe (patch)
treed1f935122336a93254fc869ebf63c7636a7d56ba /archive/2022-01-18-proposal-author-reader-terminology
parent9d5eee35a5fd7f145916043de3e94e14044946a7 (diff)
moved some persisted pads to proposal directory
See doc/proposals/2022-01-how-to-use-proposal-folder for details.
Diffstat (limited to 'archive/2022-01-18-proposal-author-reader-terminology')
-rw-r--r--archive/2022-01-18-proposal-author-reader-terminology41
1 files changed, 0 insertions, 41 deletions
diff --git a/archive/2022-01-18-proposal-author-reader-terminology b/archive/2022-01-18-proposal-author-reader-terminology
deleted file mode 100644
index fb447d2..0000000
--- a/archive/2022-01-18-proposal-author-reader-terminology
+++ /dev/null
@@ -1,41 +0,0 @@
-Start using the terminology "author" and "reader" proposal
-
-Background
----
-Figure 1 in doc/design.md refers to
-
- a) the party producing a signed checksum as "Signer", and
- b) the party verifying a signed checksum as "Verifier".
-
-This is fine in isolation, but less appropriate when looking at it from a
-broader Sigsum perspective. For example, a "Signer" may also be a "Submitter".
-It seems like we are mixing terminology for roles and concrete actors here.
-
-The above is also ambiguous. For example, logs and witnesses sign things;
-witnesses and monitors verify things.
-
-Proposal
----
-1) Replace "Signer" with "Author" when we are talking about a concrete party.
-
-According to Wikipedia's definition (https://en.wikipedia.org/wiki/Author), an
-'author is "the person who originated or gave existence to anything" and whose
-authorship determines responsibility for what was created'. This seems
-appropriate for us.
-
-The term "author" has been used in academic litterature before us for similar
-purposes:
- * "In the setting of transparency logging [18] as depicted in Fig. 1, the
- author generates events intended for recipients that describe data
- processing by the author as it takes place"
- * Link to paper: https://link.springer.com/chapter/10.1007/978-3-319-45741-3_7
-
-2) Replace "Verifier" with "Reader" when we are talking about a concrete party.
-
-According to Wikipedia's definition (https://en.wikipedia.org/wiki/Reading),
-"[r]eading is the process of taking in the sense or meaning of letters, symbols,
-etc., especially by sight or touch". Although the latter is not a perfect
-description for us, the first part is quite close and we could argue that we are
-in the "etc" category.
-
-The main idea here is that it should feel intuitive that an author has readers.