Metadata, resolve some TODOs

en/abstract.xmpdata

@@ -1,5 +1,5 @@
 % Metadata to be stored in PDF, see documentation of the pdfx package for more details.
 
-\Author{Name Surname}
+\Author{Pavel Turinský}
-\Title{Thesis title}
+\Title{Visualizing OSPF topology}
 \Publisher{Charles University}

en/chap05.tex

@@ -51,7 +51,8 @@ Birdvisu does not unfortunately support that at the moment.
 \section{Czela.net}
 
 Czela.net~\cite{czelanet} is a network system run by a community of network
-enthusiasts in Čelákovice and the surrounding area. This is the typical OSPF
+enthusiasts in Čelákovice and the surrounding area. There are about 1600 people
+connected to Czela.net. This is the typical OSPF
 deployment, whose main task is to dynamically provide fallbacks in case of
 outages. It is also an example of a larger network, with 45 routers, 32 transit
 networks and 178 external routes\footnote{Most of these would be stub routes in
@@ -68,7 +69,9 @@ as with loading the topology from file.
 This turned out to be helpful for both us and Czela.net. We discovered that our
 method of highlighting of costs does not work well with too big range of the
 costs, and on the other hand, we found several misconfigurations in their
-network, even without any other knowledge of their system.
+network (some routers had external routes to transit networks, a few networks
+with routing-unaware clients were used as transit), even without any other
+knowledge of their system.
 
 We did not notice any performance issues when dealing with the topology.
 

en/epilog.tex

@@ -50,5 +50,6 @@ source for other visualisation tools. While this is currently not possible,
 because the GUI controls all the parts of the program, it might be possible to
 separate the GUI and the coordination part.
 
-And of course, many more Annotators may be written to provide other functions,
+More Annotators could also be written to provide other functions, like
-like detecting single points of failure.
+detecting single points of failure. And last, but not least, the user interface
+can definitely be prettier.

en/header.tex

@@ -96,12 +96,19 @@ Last, but not least, I want to thank You, my dear reader, because right now You
 }
 
 \def\Abstract{%
-Abstract. \X{Recommended length around 80--200 words. This is not a~copy of your thesis assignment!}
+Network administrators need to be aware of the state of their network. While
+link-state routing protocols like OSPF have the required information, there was
+no easy way to present it to the administrator. To solve this problem, we
+developed Birdvisu, a program to visualise the topology as seen by the BIRD
+Internet Routing Daemon. Our approach allows the topology to be easily
+annotated with other data, providing an extensible way of analysing the
+topology. While not fully featured yet, Birdvisu helped discover several
+misconfigurations in a community-run network connecting about 1600 people.
 }
 
 % 3 to 5 keywords (recommended), each enclosed in curly braces
 \def\Keywords{%
-{OSPF} {network visualisation} {BIRD} {routing}
+	{OSPF}, {network visualisation}, {routing}, {BIRD}
 }
 
 %% The hyperref package for clickable links in PDF and also for storing

en/thesis.xmpdata

@@ -2,6 +2,6 @@
 
 \Author{Pavel Turinský}
 \Title{Visualizing OSPF topology}
-\Keywords{keywords\sep more such\sep yet another}
+\Keywords{OSPF\sep network visualisation\sep routing\sep BIRD}
-\Subject{Abstract of thesis}
+\Subject{Network administrators need to be aware of the state of their network. While link-state routing protocols like OSPF have the required information, there was no easy way to present it to the administrator. To solve this problem, we developed Birdvisu, a program to visualise the topology as seen by the BIRD Internet Routing Daemon. Our approach allows the topology to be easily annotated with other data, providing an extensible way of analysing the topology. While not fully featured yet, Birdvisu helped discover several misconfigurations in a community-run network connecting about 1600 people.}
 \Publisher{Charles University}

en/title.tex

@@ -41,12 +41,6 @@ Prague \YearSubmitted
 
 \end{center}
 
-\newpage
-
-\XXX{Bound into the introductory part must be the form with signed approval of the thesis topic (a photocopy suffices). This is not a~part of the electronic version of the thesis, do not scan!}
-
-%%% A page with a solemn declaration to the bachelor thesis
-
 \openright
 \hypersetup{pageanchor=true}
 \pagestyle{plain}
@@ -110,7 +104,6 @@ Abstract:
 Keywords:
 \Keywords
 
-\XXX{This information must be stored as PDF meta-data, too. Please refer to the {\tt README} file.}
 \vss}
 
 \newpage