report: add summary at the end of sections

doc/report/applications.tex

@@ -340,7 +340,7 @@ ULO~triplets. More advanced queries could look at the interlinks
 between authors and even uncover ``citation cartels'' as was done
 previously with similar approaches~\cite{citcart}.
 
-\subsubsection{Summarizing $\mathcal{Q}_1$ to $\mathcal{Q}_3$}
+\subsection{Summary}
 
 Experimenting with $\mathcal{Q}_1$ to $\mathcal{Q}_3$ provided us with
 some insight into ULO and existing ULO exports. $\mathcal{Q}_1$ shows

doc/report/implementation.tex

@@ -314,12 +314,23 @@ code for Collector and Importer is available in the
 deployment files, that is Docker Compose configuration and additional
 Dockerfiles are stored in a separate repository~\cite{dockerfilerepo}.
 
+\subsection{Summary}
+
 With this, we conclude our discussion of the implementation developed
 for the \emph{ulo-storage} project. We designed a system based around
 (1)~a Collector which collects RDF triplets from third party sources,
 (2)~an Importer which imports these triplets into a GraphDB database
 and (3)~looked at different ways of querying a GraphDB Endpoint. All
-of this is easy to deploy using a single Docker Compose file. With
-this stack ready for use, we will now continue with a look at some
+of this is easy to deploy using a single Docker Compose file.
+
+Our concrete implementation is useful in so far as that we can use it
+to experiment with ULO data sets. But development also provided
+insight about (1)~which components this class of systems requires and
+(2)~which problems need to be solved. One topic we discussed at large
+is version management. It is easy to dismiss this in these early
+stages of development, but no question it is something to keep in
+mind.
+
+With our stack ready for use, we will now continue with a look at some
 interesting applications and queries built on top of this
 infrastructure.