@@ -148,7 +148,7 @@ Another constraint generator has been introduced by Spahiu et al. with \emph{ABS
\section{Approach}\label{section:approach}
%You may add any subsections you deem appropriate for your specific project. Some examples for your reference: Technology stack, Training strategy, Data, Experiments, etc.
To construct a framework that offers a way to evaluate a \emph{knowledge graph} in an automated way, we divided our project into three main subtasks.
At first, we fetch a subgraph of a \emph{knowledge graph} from the \emph{CommonCrawl} datasets, as explained in greater detail in Section~\ref{fetchingKG}.
At first, we fetch a subgraph of a \emph{knowledge graph} from the \emph{CommonCrawl} datasets, as explained in greater detail in Section~\ref{section:fetchingKG}.
After this, our framework infers constraints over this data set (see Section~\ref{generatingconstraints}).
In the last step, the subgraph is validated against the constraints (see Section~\ref{validatingconstraints}).
The structure of the framework can be seen in Fig.~\ref{fig:uml}.
...
...
@@ -174,6 +174,7 @@ In this section, we summarise the main technologies that we used in this project
The framework was implemented in \emph{Java}. We used \emph{Maven} as a project management tool. We also used java framework \emph{Jena}, which offers an \emph{RDF} API as well as support for \emph{SPARQL} queries and the \emph{ShEx} language. The front-end was implemented using \emph{Vue3}\cite{Vue} as a front-end framework and \emph{PrimeVue} as a library for the different UI components. For the deployment of our application we used a single virtual machine. Access to the front-end is done via a single \emph{Apache} server. The front-end accesses the back-end via an internal \emph{REST-API}.
\subsection{Fetching Knowledge Graphs}
\label{section:fetchingKG}
Because \emph{knowledge graphs} can be very large and contain many nodes, we concentrated on fetching smaller subgraphs and only working on those. With this method, the relevant subgraph gets extracted from a \emph{knowledge graph} and can be worked upon in isolation.
We take our initial \emph{knowledge graphs} from the \emph{CommonCrawl} datasets and import them as a static file.
\todo{Explain query magic that fetches the graph here}
