report: implementation: sketch out implementation section

doc/report/implementation.tex

@@ -52,13 +52,27 @@ way of making RDF files ready for use with applications. We will now
 take a look at the actual implementation created for
 \emph{ulo-storage}.
 
-\subsection{Collecter}\label{sec:collecter}
+\subsection{Collecter and Importer}\label{sec:collecter}
 
-\emph{here be dragons}
+(1) Collecter and Importer are one piece of Golang software
 
-\subsection{Importer}\label{sec:importer}
+(2) Collecter has different sources: File system and Git
+repositories. Easy to extend to HTTP downloads or other sources. We
+expect XML data, but different formats exist.
 
-\emph{here be dragons}
+(3) Collecter forwards streams to Importer which imports data into
+{GraphDB}. Importer speaks GraphDB HTTP protocol for importing files.
+
+(4) GraphDB was chosen because of {REASONS}.
+
+(5) Import jobs not to be scheduled. Everything is handled by a
+collectlib. (TODO: can we do everything w/o web interface?)
+
+(6) On top of command line utilities we provide a web user interface
+for managing these import jobs.
+
+(7) Golang proved to be a good choice for this task as really
+it's just about sending stuff around on the web.
 
 \subsection{Endpoints}\label{sec:endpoints}