update

diff --git a/thesis2/.gitignore b/thesis2/.gitignore
index 1c65315..e1baa3b 100644 (file)
--- a/thesis2/.gitignore
+++ b/thesis2/.gitignore
@@ -12,3 +12,4 @@
 *.pyg
 scheme[12].xsd
 log.txt
+_minted*

diff --git a/thesis2/1.introduction.tex b/thesis2/1.introduction.tex
index a61eb8f..7ca6477 100644 (file)
--- a/thesis2/1.introduction.tex
+++ b/thesis2/1.introduction.tex
@@ -275,7 +275,11 @@ Identifier}(GUID)\footnote{A GUID is a unique identifier that in most cases is
 the permalink of the article. A permalink is a link that will point to the
 article}. An example of a RSS feed can be found in Listing~\ref{examplerss},
 this listing shows a partly truncated RSS feed of a well known venue in the
-Netherlands.
+Netherlands. As visible in the listing the similarities with XML are very
+clear. Every RSS feed contains a \texttt{channel} tag and within that tag there
+is some metadata and a list op \texttt{item} tags. Every \texttt{item} tag has
+a fixed number of different fields. The most important fields for RSS within
+the leisure industry are the \texttt{title} and the \texttt{description field}.
 
 \begin{listing}
        \caption{An example of a, partly truncated RSS feed of a well known dutch

diff --git a/thesis2/2.requirementsanddesign.tex b/thesis2/2.requirementsanddesign.tex
index 94a7c28..f3cfd73 100644 (file)
--- a/thesis2/2.requirementsanddesign.tex
+++ b/thesis2/2.requirementsanddesign.tex
@@ -50,7 +50,7 @@ and with a description underneath.
                source because of the scope of the project. Most sources require an
                entirely different strategy. The full reason why we chose RSS feeds can be
                found in Section~\ref{sec:whyrss}.
-               
+
        \item[F7:] Export the data to a strict XML feed.
 
                This requirement is an adapted version of requirement F3, this to done to
@@ -104,7 +104,22 @@ and with a description underneath.
                in the software managing the database.
 \end{itemize}
 
-\section{Design}
+\section{Application overview}
+\begin{figure}[H]
+       \label{appoverview}
+       \centering
+       \scalebox{0.7}{
+               \digraph[]{graph111}{
+                       rankdir=LR;
+                       node [shape="rectangle",fontsize=10,nodesep=0.7,ranksep=0.75,width=1];
+                       User -> System
+                       User -> Source
+                       System -> Crawler
+                       Crawler -> Source
+               }
+       }
+       \caption{Overview of the application}
+\end{figure}
 \subsection{Frontend}
 \subsubsection{General description}
 The frontend is a web interface to the backend applications that allow the user

diff --git a/thesis2/3.methods.tex b/thesis2/3.methods.tex
index 91834cb..09a9c31 100644 (file)
--- a/thesis2/3.methods.tex
+++ b/thesis2/3.methods.tex
@@ -1,3 +1,4 @@
+\section{Application overview}
 \section{Internals of the crawler generation module}
 Data marked by the user is in principle just raw html data that contains a
 table with for every RSS feed entry a table row. Within the html the code

diff --git a/thesis2/thesis.tex b/thesis2/thesis.tex
index 1b2eb5e..6a9264c 100644 (file)
--- a/thesis2/thesis.tex
+++ b/thesis2/thesis.tex
@@ -6,6 +6,7 @@
 \usepackage{graphicx}
 \usepackage{float}
 \usepackage{minted}
+\usepackage{xcolor}
 \usepackage[dvipdfmx,hidelinks]{hyperref}
 \usepackage{graphviz}
 \usepackage{amssymb}
@@ -36,8 +37,8 @@
        texcl=false,
 }
 
-\newcommand{\cvartitle}{Adaptable crawler generation system for leisure
-activity RSS feeds}
+\newcommand{\cvartitle}{Adaptable crawler specification generation system for
+leisure activity RSS feeds}
 % Setup hyperlink formatting
 \hypersetup{
        pdftitle={\cvartitle},