summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--Report/Chapter1.tex19
-rw-r--r--Report/Chapter3.tex53
2 files changed, 37 insertions, 35 deletions
diff --git a/Report/Chapter1.tex b/Report/Chapter1.tex
index 712bfdd..d1d5628 100644
--- a/Report/Chapter1.tex
+++ b/Report/Chapter1.tex
@@ -1,8 +1,8 @@
\section{Introduction}
-For the master course Advanced Databases (2ID45), group 1 chose to
-create a liquor database. The project is called ”Pottepei” which is
-Flemish (Brussels) for a drunk. To access the database we've made a
-web interface, which can be found at "pottepei.schinagl.nl".
+For the master course Advanced Databases (2ID45), we chose to create
+a liquor database. The project is called ”Pottepei” which is Flemish
+(Brussels) for a drunk. To access the database we made a web
+interface, which can be found at "pottepei.schinagl.nl".
\\\\
This document will discussed the inside view of the project. The
general description of the project can be read in chapter 2. What
@@ -10,9 +10,10 @@ does the website do? And an overview of the techniques that were used
to complete the project.
\\\\
In the next chapters we will go further into details about the
-project we used. In chapter 3 we will discuss all the XML aspects of
-the project. Which XML files were used? And how they look like. Also
-the purpose of the files will be discussed.
+techniques we used. In chapter 3 we will discuss all the XML aspects
+of the project. Which XML files were used? And how they look like.
+Also the purpose of the files will be discussed.
\\\\
-In chapter 4 we will explain which query's we've used to retrieve
-some goals. Some query's will be given and explained.
+In chapter 4 we will explain which query's we used to retrieve some
+goals. Some query's will be given and explained. And finally we come
+up with a conclusion.
diff --git a/Report/Chapter3.tex b/Report/Chapter3.tex
index 345a338..b59969b 100644
--- a/Report/Chapter3.tex
+++ b/Report/Chapter3.tex
@@ -12,20 +12,19 @@ In this section you can read how the XML files are build.
All the information for the website is stored in four Database XML
files. One file contains the main information about all the liquor.
Two files contains grouping information of the liquor. And there is
-one file which contains technical information for the RSS feeds. In
-this section we will discussed the four files. This will be done by a
-description, (a part of) the file and a XML tree. We started with the
-two grouping information files. Note: The information in the XML
-files are the information, or a part of the information, which the
-files contains at the moment this report is written. Some files can
-be extended with information, because of the dynamically of the
-website.
-
-
-\begin{itemize}
-\item \textbf{LiquorTypes.xml} \\
-In this file we'll store the different kind of liquor, for which we
-have data in the data base.
+one file which contains technical information for the incoming RSS
+feeds. In this section we will discussed the four files. This will be
+done by a description, (a part of) the file and a XML tree. We
+started with the two grouping information files. Note: The
+information in the XML files is the information, or a part of the
+information, which the files contains at the moment this report is
+written. Some files can be extended with information, because of the
+dynamically of the website.
+
+
+\subsubsection{LiquorTypes.xml} In this file we'll store the different
+kind of liquor, for which we have data in the database. Below you see
+the XML-file.
\begin{verbatim}
<LiquorTypes>
<LiquorType ID="1"><Name>General</Name></LiquorType>
@@ -52,9 +51,10 @@ they are showed dotted (without their descendants).
-\item \textbf{NewsCategories.xml} \\
+\subsubsection{NewsCategories.xml}
In this file we'll store the different categories the items are from.
-It is very similar to the LiquorTypes XML.
+It is very similar to the LiquorTypes XML. Below you see the
+XML-file.
\begin{verbatim}
<NewsCategories>
<NewsCategory ID="1"><Name>News</Name></NewsCategory>
@@ -82,8 +82,9 @@ dotted (without their descendants).
-\item \textbf{DB.xml} \\
-In this file we'll store the main information of the website.
+\subsubsection{DB.xml}
+In this file we'll store the main information of the website. Below
+you see a part of the XML-file.
\begin{verbatim}
<db>
<items>
@@ -148,10 +149,11 @@ showed dotted (without their descendants).
-\item \textbf{rssfeeds.xml} \\
+\subsubsection{rssfeeds.xml}
In this file we'll store the RSS binding information for the incoming
RSS feed, so the website knows from which rss he must take
-information, and how that is must store.
+information, and how that is must store. Below you see a part of the
+XML-file.
\begin{verbatim}
<IncomingRSSFeedBindings>
<RSSFeed ID="1">
@@ -190,7 +192,6 @@ showed dotted (without their descendants).
-\end{itemize}
@@ -201,8 +202,8 @@ RSS feeds the website uses, then how a RSS-Feed looks like.
\\\\
The website uses two types of RSS feeds:
-\begin{itemize}
-\item \textbf{Incomming RSS-feed}\\
+
+\subsubsection{Incomming RSS-feed}
This is the RSS-Feeds from which the website takes his information.
There are several incoming RSS feeds and for each the website does
the same procedures to add the information into the database. This is
@@ -221,7 +222,7 @@ the same. If it is the same go on with the next item of RSS Feed.
\item The news item is already there, but it has different LiquorTypeID's or NewsCategoryID's, so add the new LiquorTypeID or NewsCategoryID to the item and go on with the next item of RSS Feed.
\end{enumerate}
-\item \textbf{Outgoing RSS-feed} \\
+\subsubsection{Outgoing RSS-feed}
The website has also an outgoing RSS-Feed. In this feed the latest
twenty news messages from the database will be put into an RSS feed.
The latest twenty news messages are gained from the DB xml via a X
@@ -265,10 +266,10 @@ part of the code generates.
<title>Pottepei RSS feed</title>
\end{verbatim}
This code will be automatically execute every day.
-\end{itemize}
-\textbf{The construction of a RSS feed}\\
+
+\subsubsection{The construction of a RSS feed}
A RSS feed has a standard constructions. We use the RSS version 2.0.
There are many information which you can store in a RSS feed. We use
a some of those. Below you can see a part of our RSS feed file: