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

higlight open questions

parent 3cf9b95b
No related branches found
No related tags found
No related merge requests found
......@@ -173,9 +173,12 @@
representation~$\mathcal{E}$} to \emph{database storage~$\mathcal{D}$}.
\item When $\mathcal{E}$ changes, so does~$\mathcal{E}$ when a new
export is run. This should result in~$\mathcal{D}$ changing as well.
\item Not trivial! A work around is (1)~re-creating databases from
scratch and (2)~splitting up knowledge into smaller repositories.
\end{itemize}
\begin{alertblock}{Huh!}
Not trivial! A work around is (1)~re-creating databases from
scratch and (2)~splitting up knowledge into smaller repositories.
\end{alertblock}
\end{frame}
% [Applications & Questions]
......@@ -208,9 +211,12 @@
with RDF4J that looks at what ULO~predicates are used.
\item Both Coq and Isabelle exports used less than a third of all
ULO~predicates. Many predicates are used by neither exports.
\item Queries formulated for a tetrapodal search system have to
account for these ``holes'' in existing data sets.
\end{itemize}
\begin{alertblock}{Huh!}
Queries formulated for a tetrapodal search system have to
account for these ``holes'' in existing data sets.
\end{alertblock}
\end{frame}
\begin{frame}{Exploration: Used Predicates}
......@@ -279,9 +285,12 @@
\item Algorithms aren't programs! Programs implement
algorithms that solve problems.
\end{itemize}
\item This illustrates the difficulty in designing an ontology
(schema) that is both expressive and concise.
\end{itemize}
\begin{alertblock}{Huh!}
This illustrates the difficulty in designing an ontology
(schema) that is both expressive and concise.
\end{alertblock}
\end{frame}
% [Summary]
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment