1.1 --- a/doc/griesmayer/add-content.tex Wed Oct 01 09:17:24 2003 +0200
1.2 +++ b/doc/griesmayer/add-content.tex Wed Oct 01 21:22:34 2003 +0200
1.3 @@ -231,7 +231,7 @@
1.4 this tree are used to jump directly to an other information-page. (as
1.5 demanded in the UC desdribed in section \ref{creating_frameset})
1.6
1.7 - \subsection{information-processor}
1.8 + \subsection{Information-processor}
1.9 The \emph{information-processor} runs in the same virual machine as
1.10 the BrowserFrontend and communicates with the Frontend through a well
1.11 defined set of method calls. So, it exists one time per
1.12 @@ -271,7 +271,7 @@
1.13 the \emph{session-dialog}\kommentar{ref einfuegen}\footnote{explained
1.14 later in this section}.
1.15
1.16 - \subsection{browser-dialog}
1.17 + \subsection{Browser-dialog}
1.18 The \emph{browser-dialog} is the peer for the browser within the
1.19 dialog and gathers the informations for the request. Depending of the
1.20 type of request, it contacts the \emph{KE-Store} and/or the
1.21 @@ -615,7 +615,7 @@
1.22 the shown subexamples he can do this by setting up the dialog to
1.23 suppress the uninteded references (see subsection \ref{ADD:dialog}).
1.24
1.25 - \subsection{object structure}
1.26 + \subsection{Object structure}
1.27
1.28 We have seen in the last sections that -- although the informations
1.29 to present look very different at first glance -- we finally achieve
1.30 @@ -1065,7 +1065,7 @@
1.31
1.32 %\section{missing objects (temporary subsection)}
1.33
1.34 - \subsection{permissions-module}
1.35 + \subsection{Permissions-module}
1.36 The \emph{permissions-module} stores and maintaines informations
1.37 about which user might access to which \emph{KE-Objects}. The
1.38 administration of the permissions is based upon the users stored
1.39 @@ -1088,7 +1088,7 @@
1.40 the environment given in the \emph{temporary\_environ} field of the
1.41 user-object.
1.42
1.43 -\section{current status}
1.44 +\section{Current status}
1.45 The sections in this version of the document give informations which
1.46 are on a different state of development.
1.47
2.1 --- a/doc/griesmayer/da_griesmayer.tex Wed Oct 01 09:17:24 2003 +0200
2.2 +++ b/doc/griesmayer/da_griesmayer.tex Wed Oct 01 21:22:34 2003 +0200
2.3 @@ -688,7 +688,7 @@
2.4 \emph{namespaces} to distinguish them.\cite{metadata_principles}
2.5
2.6 The following sections give examples of popular metadata-sets.
2.7 -\subsection{dublin core}
2.8 +\subsection{Dublin core}
2.9 The first \emph{dublin core} metadata-set had 13 elements and was a
2.10 result of workshop held in Dublin, Ohio in 1995. A series of workshops
2.11 and conferences led to the initial ``classic'' Dublin Core which
2.12 @@ -843,20 +843,20 @@
2.13 MoWGLI uses RDF to define a metadata-set which is related to DC and
2.14 LOM \cite{mowgli_metadata}.
2.15
2.16 -\chapter{UseCases}
2.17 +\chapter{Usee interface}
2.18 %
2.19 % UC Creating the frameset for the problem browser
2.20
2.21 -This section presents a few use-cases to explain the user interface
2.22 -and scetch the collaboration of the internal modules.
2.23 +This section presents a few tasks of isac to explain the user interface
2.24 +and sketch the collaboration of the internal modules.
2.25
2.26 The first section handles the interaction with the users and can be
2.27 read to get informed about \sisac s capabilities. The second section
2.28 gives more details and referres to the ADD for more informations.
2.29
2.30 -\section{User Level UseCases}
2.31 +\section{User Level}
2.32
2.33 -\subsection{creating the frameset for the problem browser}
2.34 +\subsection{Creating the frameset for the problem browser}
2.35 \label{creating_frameset}
2.36 A page which occures in the browser-window is built up by a frameset
2.37 which consists of the \emph{navigation-frame} and a
2.38 @@ -883,9 +883,9 @@
2.39 are loaded by the \emph{browser-window} after loading the frameset.
2.40
2.41
2.42 -\section{System Level UseCases}
2.43 +\section{System Level}
2.44
2.45 -\subsection{user login}
2.46 +\subsection{User login}
2.47
2.48 In principle, \sisac is not dependent to special frontends like
2.49 WEB-Browser. Nevertheless, WEB-Browsers are installed on almost all
2.50 @@ -964,7 +964,7 @@
2.51
2.52 %
2.53 % UC Fetching a content-page from the KE-Store (SL-UC)
2.54 -\subsection{fetching a content-page from the KE-Store}
2.55 +\subsection{Fetching a content-page from the KE-Store}
2.56 When the browser-window requests a content-page, it encodes all
2.57 necessary informations to fetch the page within the URL and sends it
2.58 to the browser-frontend.
2.59 @@ -1023,11 +1023,11 @@
2.60 \chapter{SDD}
2.61 \input{sdd-content}
2.62
2.63 -\chapter{implementation}
2.64 +\chapter{Implementation}
2.65 \label{impl}
2.66 \input{implementation}
2.67
2.68 -\chapter{summary}
2.69 +\chapter{Summary}
2.70 \input{summary}
2.71
2.72 \appendix
3.1 --- a/doc/griesmayer/implementation.tex Wed Oct 01 09:17:24 2003 +0200
3.2 +++ b/doc/griesmayer/implementation.tex Wed Oct 01 21:22:34 2003 +0200
3.3 @@ -1,4 +1,4 @@
3.4 -\section{introduction}
3.5 +\section{Introduction}
3.6 \label{impl:introduction}
3.7 Part of my work on \sisac was to build an preliminary implementation
3.8 of the \emph{BrowserServlet} and the modules which are necessary to
3.9 @@ -89,9 +89,9 @@
3.10 the xsl stylesheets which are both not part of the java-code and easy
3.11 to change.
3.12
3.13 -\subsection{tomcat}
3.14 +\subsection{Tomcat}
3.15 \kommentar{informationen ueber die konfiguration vom tomcat}
3.16 -\subsection{servlet}
3.17 +\subsection{Servlet}
3.18 \kommentar{start des servlets/einbinden in eine tomcatinstallation}
3.19
3.20 \section{BrowserDialog}
4.1 --- a/doc/griesmayer/isac-intro-eng.tex Wed Oct 01 09:17:24 2003 +0200
4.2 +++ b/doc/griesmayer/isac-intro-eng.tex Wed Oct 01 21:22:34 2003 +0200
4.3 @@ -106,7 +106,8 @@
4.4 The thesis at hand is a subproject within the \sisac-project. At first the subproject is being located within the technical issues raised by the project as a whole, as described in subsection \ref{techn-aufg} p.\pageref{techn-aufg}. And secondly the expected contribution of the thesis to the general goals of \sisac{} will be specified.
4.5
4.6 %-------------------------------------------------------------------
4.7 -\subsection{Location within the technical issues} \label{intro:goals}
4.8 +%\subsection{Location within the technical issues}
4.9 +\subsection{Relation to other science disciplines}\label{intro:goals}
4.10 %-------------------------------------------------------------------
4.11 The main concern of this thesis are issues of software technology. Computer mathematics is just touched by the issue of presentation of math, and for the work on didactics and psychology elementary prerequisites are provided.
4.12
5.1 --- a/doc/griesmayer/sdd-content.tex Wed Oct 01 09:17:24 2003 +0200
5.2 +++ b/doc/griesmayer/sdd-content.tex Wed Oct 01 21:22:34 2003 +0200
5.3 @@ -528,7 +528,7 @@
5.4 instantiated on system-startup and registered an the
5.5 \emph{dinopolis}\/-NameService to be found by the frontend-applications.
5.6
5.7 -\subsection{create a new session}
5.8 +\subsection{Create a new session}
5.9 A new session is initiated when an user logs in the first time by the
5.10 GUI or a KnowledgeBrowser.
5.11 %by the session-controller. This is a
6.1 --- a/doc/griesmayer/summary.tex Wed Oct 01 09:17:24 2003 +0200
6.2 +++ b/doc/griesmayer/summary.tex Wed Oct 01 21:22:34 2003 +0200
6.3 @@ -32,7 +32,7 @@
6.4 A reason for this layering was the ability to control and bias the
6.5 information flow between all parts of \isac by the dialog.
6.6
6.7 -\section{achieved goals}
6.8 +\section{Achieved goals}
6.9 This section will outline the goals and results of this thesis. The
6.10 goals were given in section \ref{intro:goals}.
6.11