\caption{The shape map used for validating the full subgraph starting with RiverBodyOfWater-nodes.}
\label{fig:shape_map}
\end{figure}
...
...
@@ -256,7 +259,7 @@ Additionally, the JVM was set up to use up to 16 GB of main memory for its heap
\subsection{Runtime}
\label{section:runtime}
Figures~\ref{fig:exec_times_per_limit} and \ref{fig:exec_times_per_triples} show the measurements we obtained by changing the \emph{LIMIT} input parameter. This parameter limits the size of the start-node subset, from which connected nodes are queried. All the measurements are shown in Tables~\ref{table:runtimes_wo_limit} and \ref{table:runtimes_w_limit}.
Figures~\ref{fig:exec_times_per_limit} and \ref{fig:exec_times_per_triples} show the measurements we obtained by changing the \emph{LIMIT} input parameter. This parameter limits the size of the start-node subset, from which connected nodes are queried. All the measurements are shown in Tables~\ref{table:runtimes_w_limit} and \ref{table:runtimes_wo_limit}.
\begin{figure}[htp]
\begin{subfigure}{\textwidth}
...
...
@@ -341,7 +344,7 @@ Secondly, optional properties are not always inferred and therefore missing from
\subsubsection{ShEx Validation}
The generated \emph{ShEx}-constraints for small subgraphs (Canal with \emph{LIMIT} 50, Service with \emph{LIMIT} 50) were cross validated using the online-tool \emph{RDFShape}\cite{RDFShape}. The validation result was the same as in our tool.
The generated \emph{ShEx}-constraints for small subgraphs (Canal with \emph{LIMIT} 50, Service with \emph{LIMIT} 50) were cross validated using the online-tool \emph{RDFShape}\cite{RDFShape}. The validation result was the same as in our tool, being that all nodes are conformant.