Skip to content
Snippets Groups Projects
Commit 12028569 authored by Andreas Schärtl's avatar Andreas Schärtl
Browse files

report: put emphasis on contributions

parent 0fe505d4
No related branches found
No related tags found
No related merge requests found
\section{Applications}\label{sec:applications} \section{Applications}\label{sec:applications}
With programming endpoints in place, we can now query the data set With programming endpoints in place, we can now query the data set
containing both Isabelle and Coq exports stored in {GraphDB}. We containing both Isabelle and Col exports stored in {GraphDB}. We
experimented with the following applications that talk to a GraphDB experimented with the following applications that talk to a GraphDB
Endpoint, our second contribution. Endpoint, our second contribution.
...@@ -126,9 +126,10 @@ actually reachable URI on the open web, if that is applicable for a ...@@ -126,9 +126,10 @@ actually reachable URI on the open web, if that is applicable for a
given library. given library.
While translating from \texttt{ulo:sourceref} to original URI While translating from \texttt{ulo:sourceref} to original URI
introduced some extra work, implementing this application was easy and introduced some extra work, implementing this application was
straight-forward. Implementing similar features for other environments straight-forward. With this we showed that searching through metadata
should not be very difficult. in existing ULO data sets is already quite feasible. Implementing
similar features for other environments should not be very difficult.
\subsection{Querying for Tetrapodal Search}\label{sec:tetraq} \subsection{Querying for Tetrapodal Search}\label{sec:tetraq}
...@@ -333,11 +334,11 @@ query. Because everything is handled by the database, access should be ...@@ -333,11 +334,11 @@ query. Because everything is handled by the database, access should be
about as quick as we can hope it to be. about as quick as we can hope it to be.
While the sparse data set available to use only returned a handful of While the sparse data set available to use only returned a handful of
results, we see that queries like~$\mathcal{Q}_3$ are easily serviced results, we showed that queries such as~$\mathcal{Q}_3$ are easily
with organizational knowledge formulated in ULO~triplets. More serviced with organizational knowledge formulated in
advanced queries could look at the interlinks between authors and even ULO~triplets. More advanced queries could look at the interlinks
uncover ``citation cartels'' as was done previously with similar between authors and even uncover ``citation cartels'' as was done
approaches~\cite{citcart}. previously with similar approaches~\cite{citcart}.
\subsubsection{Summarizing $\mathcal{Q}_1$ to $\mathcal{Q}_3$} \subsubsection{Summarizing $\mathcal{Q}_1$ to $\mathcal{Q}_3$}
......
...@@ -50,7 +50,9 @@ necessary to further extend the upper level ontology. It will be ...@@ -50,7 +50,9 @@ necessary to further extend the upper level ontology. It will be
necessary to look at the properties of future exports to make a more necessary to look at the properties of future exports to make a more
well-funded decision. well-funded decision.
Despite many open questions, \emph{ulo-storage} provides the necessary Despite many remaining open questions, \emph{ulo-storage} provides the
infrastructure for importing ULO triplets into an efficient storage necessary infrastructure for importing ULO triplets into an efficient
engine. A necessary building block for a larger tetrapodal search storage engine. A necessary building block for a larger tetrapodal
system. search system. In addition to the concrete implementation, the
experiences we have made along the way should benefit future research
towards a greater tetrapodal search system.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment