4.0

doc/report/applications.tex

@@ -5,11 +5,16 @@ both Isabelle and Coq exports stored in {GraphDB}. We experimented with
 various queries and applications:
 
 \begin{itemize}
-    \item Exploring which ULO predicates are actually used and which
-      remain unused (Section~\ref{sec:expl}).
+    \item Exploring which ULO predicates are actually used in the
+      existing Coq and Isabelle exports.  We find that more than two
+      thirds of existing ULO predicates were not taken advantage of
+      (Section~\ref{sec:expl}).
 
-    \item We ran some queries that were suggested as building blocks
-      of a larger tetrapodal search system (Section~\ref{sec:tetraq}).
+    \item We investigated queries that could be used to extend the
+      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
@@ -19,9 +24,7 @@ various queries and applications:
       the ULO data set (Section~\ref{sec:webq}).
 \end{itemize}
 
-For each example query or application, we try to describe how to
-implement it, what results we observed and if possible we conclude
-with some recommendations for future development of {ULO}.
+\noindent Each application will now be discussed in a dedicated section.
 
 \subsection{Exploring Existing Data Sets}\label{sec:expl}
 
@@ -267,7 +270,7 @@ idea to design a dedicated ontology and potentially data store entirely.
 Finally, while we were able to formulate a SPARQL query that should
 take care of most of~$\mathcal{Q}_3$ we found that the existing data sets
 contain very little information about authorship. This underlines
-the observations made in Section~\label{sec:expl}, developers writing
+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''.