Add section on implementation

Signed-off-by: Matthias Beyer <mail@beyermatthias.de>

1 files changed, 33 insertions, 0 deletions

diff --git a/doc/paper/main.tex b/doc/paper/main.tex
index 89643d0..8d6f168 100644
--- a/doc/paper/main.tex
+++ b/doc/paper/main.tex
@@ -92,6 +92,39 @@ mail@beyermatthias.de}
 % Possibilities how the block chain model could be optimized
 
 
+\section{Implementation}
+% Intro for architecture description
+
+\subsection{Architecture}
+% Description of the general architecture
+
+\subsection{Backend}
+% Interfacing with IPFS and providing an abstraction to
+% interact with "blocks" and "profiles", using either
+% - a REST interface to be run as a (possibly network-local) server, or
+% - a library API for embedding into a "fat" application
+
+
+\subsection{Middleware}
+% Middleware library, providing
+% - interfaces for working with a backend (either REST or library)
+% - public-private-key crypto interfaces for IPNS name publishing
+
+% Itself providing either a REST interface via a webserver or
+% a library API for embedding into a "fat" application
+
+
+\subsection{Frontend}
+% Frontend implementation, abstract over the middleware implementation, which
+% needs to be trusted.
+%
+% A frontend impl could be started on a embedded device where no public-private
+% key crypto is possible, so the middleware runs on a better-suited device
+%
+% The frontend could also embedd the middleware and implement a desktop client
+% using a CLI, TUI, GUI or WUI.
+
+
 \section{Future work}
 % What could be implemented on top of this idea