conclusion.tex

\section{Conclusions and Next Steps}\label{sec:conclusion}

\subsection{An Additional Harvester Component} % copied from introduction.tex

These are the three components realized for
\emph{ulo-storage}. However, additionally to these components, one
could think of a \emph{Harvester} component.  Above we assumed that
the ULO triplets are already available in RDF~format.  This is not
necessarily true.  It might be desirable to automate the export from
third party formats to ULO and we think this should be the job of a
Harvester component.  It fetches mathematical knowledge from some
remote source and then provides a volatile stream of ULO data to the
Collecter, which then passes it to the Importer and so on. The big
advantage of such an approach would be that exports from third party
libraries can always be up to date and do not have to be initiated
manually. Another advantage of this hypothetical component is that
running exports through the Harvester involves the whole import chain
of Collecter and Importer which involves syntax~checking for the
exported RDF data. Bugs in exporters that produce faulty XML would be
found earlier in development.