report: write about apps

I like playing w/ languages, but I am not sure at all if this is a
good idea.

doc/report/Makefile

-TEX_SOURCES = report.tex abstract.tex endpoint.tex
+TEX_SOURCES = report.tex abstract.tex endpoints.tex applications.tex
 
 report.pdf: $(TEX_SOURCES) references.bib
 	chronic pdflatex $<

doc/report/applications.tex

+\section{Applications}
+
+With endpoints in place, we can now query the ULO/RDF
+data set. Depending on the kind of application, different interfaces
+and approaches to querying the database might make sense.
+
+For integrating the ULO/RDF data set into an existing application, it
+probably is reasonable to directly query the data set using RDF4J.
+That is, of course, assuming the existing co debase is based on the
+{JVM}.  If that is not the case, generating SPARQL queries is the
+obvious choice.
+
+The advantage of this approach is that connecting and interacting
+with the database is straightforward. The disadvantage is that this
+approach requires a deep understanding of structure of the underlying
+ULO triplets.
+
+\subsection{A Language for Organizational Data}
+
+ULO/RDF is a subset of RDF. While it can be queried as just standard
+RDF data, maybe it is helpful to design a query language only for
+ULO/RDF triplets. Expressions in this particular query language could
+then be converted to SPARQL or RDF4J expressions. Ideally this means
+that (1)~the query language is intuitive and easy to use for this
+specific use case and (2)~execution is still fast as the underlying
+SPARQL database is already very optimized.
+

doc/report/report.tex

@@ -35,7 +35,13 @@
     \input{abstract.tex}
 \end{abstract}
 
-\input{endpoint.tex}
+\textbf{
+  --- This is more of a scratchpad for now. Do not go into this document
+  expecting a real report just yet. ---
+}
+
+\input{endpoints.tex}
+\input{applications.tex}
 
 \newpage
 \printbibliography{}