# HG changeset patch
# User Hans Plum <hans.plum@intevation.de>
# Date 1273213241 0
# Node ID 4615bc4dc8222d2a5bfc1f492a0c85b78b0de2fd
# Parent  a0c54d4edbdf2cf1cd5fc9ac48879ef1789f0aae
Added some FIXMEs where questions arose.

doc/trunk@1071 c6561f87-3c4e-4783-a992-168aeb5c3f6f

diff -r a0c54d4edbdf -r 4615bc4dc822 doc/config-manual/model_of_transitions.tex
--- a/doc/config-manual/model_of_transitions.tex	Thu May 06 08:53:33 2010 +0000
+++ b/doc/config-manual/model_of_transitions.tex	Fri May 07 06:20:41 2010 +0000
@@ -74,11 +74,11 @@
 Within each of these files, the steps for gathering the values for the
 parameterisation are configured by defining states, transitions and outputs
 (c.f. \ref{ref:config-a-product}).  The definition of states, transitions and
-outputs reference the actual SQL-statements via identifier. The SQL-statements
-are gathered in the file \verb+conf/queries.txt+.
+outputs reference the actual SQL-statements via an identifier. The SQL-statements
+are gathered in the file \verb+conf/queries.properties+.
 
 
-\subsection{General principle of model of transitions}
+\subsection{Explaining the background of the XML configuration}
 
 It is possible to configure the GNV in many ways.
 It is possible to add or remove FIS, add or remove Products from a FIS or
@@ -103,7 +103,7 @@
 /artifact-database/artifact-factories of the Configurationfile.
 
 \begin{lstlisting}
-<artifact-factory name='fis\_marnet' 
+<artifact-factory name='fis_NEWFISNAME' 
                   description='Factory to create an artifact to be used with the FIS NEWFISNAME'  
                   ttl='3600000' 
                   artifact='de.intevation.artifactdatabase.ProxyArtifact'>
@@ -155,7 +155,7 @@
 the Configurationfile.
 
 \begin{lstlisting}
-<artifact name='fis\_marnet'>
+<artifact name='fis_NEWFISNAME'>
     <products>
      ...
     </products>
@@ -248,6 +248,7 @@
                    conf/queries.properties
     \item dataname: The ID of the Data which will be displayed in this State.
                     The ID will be use to localize the description of the Data.
+                    %% FIXME HP: Where are this localization files; a hint is enough
     \item data-multiselect: true it is possible to select 1 or more Items.
                             false it is possible to select only one Item.
     \item inputvalues: The Values which can be "feed" to this State and which 
@@ -287,6 +288,7 @@
                 of the Value.
                 This might be String, Integer, Double, Date, Point, LineString, 
                 Polygon, Coordinate, Geometry and AttributeName.
+                %% FIXME HP: Explain Coordinate, AttributeName
     \item multiselect: true if more than on Value can be feed or put into the SQL-statement.
                        false if one on Value will be accepted.
     \item usedinquery: Number how often the value should be put into the SQL-Statement:
@@ -301,6 +303,7 @@
 
 This SQL-statement is configured to use in the State above.
 
+%% FIXME HP: What do we expect with this statement? Whats the result?
 \begin{lstlisting}
 SELECT DISTINCT 
        p.PARAMETERID KEY, 
@@ -324,6 +327,7 @@
 \begin{itemize}
     \item featureid: 4 (Marnet)
     \item fisname: fis\_marnet
+    %% FIXME HP: Where does these values come from? Do not get the context, sense here.
     \item parameterid: not set because it's the value that should be 
                        chosen in this state. 
 \end{itemize}
@@ -364,7 +368,6 @@
 </inputvalues>
 \end{lstlisting}
 
-
 \begin{lstlisting}
 SELECT DISTINCT 
     ...
@@ -396,6 +399,7 @@
 \end{lstlisting}
 
 
+%% FIXME HP: For the fisname, we get NOCOLUMNINDB? Why? Better to take an existing/real example ...
 \begin{lstlisting}
  SELECT DISTINCT 
     ...
@@ -444,6 +448,7 @@
   \item to:   The ID of the State which can be reached.
   \item condition: The Condition which have to be fulfilled.
 \end{itemize}
+%% FIXME: What type of conditions do exist?
 
 \paragraph{Outputstate}
 
@@ -460,6 +465,7 @@
   \item TimeSeries: TimeSeriesOutputState
   \item Horizontalprofile: HorizontalProfileOutputState
   \item Horizontalprofile on Meshes: HorizontalProfileMeshOutputState
+  %% FIXME HP: Whats the reason for this split up? Horizontale Schnittprofile? Explain orally.
   \item Verticalcrosssection:VerticalCrossSectionOutputState
   \item Verticalprofiles: VerticalProfileOutputState
   \item Horizontalcrosssections: HorizontalCrossSectionMeshOutputState