report: applications: remove references to unimplemented apps

If I end up having enough time im September, sure, I can implement it,
but if not that's too much that's fine too.

doc/report/applications.tex

 \section{Applications}\label{sec:applications}
 
-With programming endpoints in place, we can now query the data set containing
-both Isabelle and Coq exports stored in {GraphDB}. We experimented with
-various queries and applications:
+With programming endpoints in place, we can now query the data set
+containing both Isabelle and Coq exports stored in {GraphDB}. We
+experimented with two kinds of applications thatt take advantage
+of our GraphDB endpoint.
 
 \begin{itemize}
     \item Exploring which ULO predicates are actually used in the
@@ -14,17 +15,10 @@ various queries and applications:
       system into a larger tetrapodal search system. While some
       organizational queries have obvious canonical solutions others
       introduce questions on how organizational knowledge should be
-      organized (Section~\ref{sec:tetraq}).
-
-    \item We also experimented with various other more general queries
-      for organizational data recommended in literature
-      (Section~\ref{sec:miscq}).
-
-    \item Finally we built a small web front end that takes visualizes
-      the ULO data set (Section~\ref{sec:webq}).
+      structured (Section~\ref{sec:tetraq}).
 \end{itemize}
 
-\noindent Each application will now be discussed in a dedicated section.
+\noindent Both applications will now be discussed in a dedicated section.
 
 \subsection{Exploring Existing Data Sets}\label{sec:expl}
 
@@ -269,10 +263,3 @@ contain very little information about authorship. This underlines
 the observations made in Section~\ref{sec:expl}, developers writing
 applications that query ULO storage need to be aware of the fact that
 existing exports have ``holes''.
-
-\subsection{Organizational Queries}\label{sec:miscq}
-
-Other organizational queries for organizational data sets have
-previously been proposed~\cite{adl}. Here we implement some of them.
-
-\subsection{Experience with Building a Web Frontend}\label{sec:webq}