taler-docs

commit 91c1be31d0b16e56794ee43750b470f9901025a6
parent f72ddb3b72cc13e6e065b7d2be7e6ca3027f958a
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
Date:   Thu, 14 Jan 2021 17:05:09 -0500

glossary: clarify ‘buyer’ vs ‘customer’ vs ‘user’

This is due to feedback from Stefan.

I am not exactly sure about the distinction between ‘buyer’ and ‘customer’,
however.  Perhaps those terms are actually synonyms?

Diffstat:
M
developers-manual.rst
 | 
11
+++++++++--

1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/developers-manual.rst b/developers-manual.rst
@@ -1211,6 +1211,10 @@ use when talking to end users or even system administrators.
   bank
     traditional financial service provider who offers wire :term:`transfers <transfer>` between accounts
 
+  buyer
+    individual in control of a Taler :term:`wallet`, usually using it to
+    :term:`spend` the :term:`coins` on :term:`contracts` (see also :term:`customer`).
+
   close
   closes
   closed
@@ -1221,8 +1225,7 @@ use when talking to end users or even system administrators.
     for closing
 
   customer
-    individual in control of a Taler :term:`wallet`, usually using it to
-    :term:`spend` the :term:`coins` on :term:`contracts`.
+    individual that directs the buyer (perhaps the same individual) to make a purchase
 
   coin
   coins
@@ -1461,6 +1464,10 @@ use when talking to end users or even system administrators.
   transaction
     method by which ownership is exclusively transferred from one entity
 
+  user
+    any individual using the Taler payment system
+    (see :term:`customer`, :term:`buyer`, :term:`merchant`).
+
   version
     Taler uses various forms of versioning. There is a database
     schema version (stored itself in the database, see \*-0000.sql) describing