correction for PR 56

doc/MANGO.tex

@@ -141,7 +141,7 @@ \section{Introduction}
 
 MANGO is not designed to describe what a source is but to help clients to discover and to understand
 the features (i.e quantities) available for a particular source instance.
-VOTable data mapped on MANGO with MIVOT (2023ivoa.spec.0620M) annotations can be consumed on a feature basis 
+VOTable data mapped on MANGO with MIVOT \citep{2023ivoa.spec.0620M} annotations can be consumed on a feature basis 
 instead of column per column.
 The way complex quantities are built is described by MANGO but no longer by the client applications.
 
@@ -162,6 +162,7 @@ \subsection{Role within the VO Architecture}
 \section{Representing observed astronomical objects : Use Cases and  Requirements}
 
 \subsection{Use Cases}
+
 \input{usecases.tex}
 
 \subsection{Requirements}
@@ -215,7 +216,9 @@ \subsection{Requirements}
                 the position of an object may depend on its proper motion. This kind of correlation can be revealed 
                 with a model that can link data columns.
           \item MANGO must provide an accurate description of the epoch propagation. 
-                This is probably the most important use case for MANGO. It consists in constructing 6 parameter     		position vectors (position, proper motion, parallax and radial velocity), whose components are 			correlated and valid for a given epoch. 
+                This is probably the most important use case for MANGO. It consists in constructing 6 parameter 
+                position vectors (position, proper motion, parallax and radial velocity), whose components are 			
+                correlated and valid for a given epoch. 
                 This feature is required to compare positions given by surveys with high astrometry accuracy such as GAIA.
        \end{itemize} 
 
@@ -236,13 +239,12 @@ \section{Model Overview}
 \begin{figure}
      \includegraphics[width=1.0\textwidth]{../model/overview.png}
      \caption{Model overview}
-     \label{fig:overview}
+     \label{overview}
 \end{figure}
 
-Figure \ref{fig:overview} shows the general structure of the model.
 
-The root class is \texttt{MANGOObject}]. 
-It has only one mandatory attribute, an \texttt{identifier}.
+The root class of the model \texttt{MANGOObject} which has only
+one mandatory attribute, an \texttt{identifier}.
 Identifiers should be unique within a collection, e.g. a data table, although 
 this feature is not required by the model.
 
@@ -252,7 +254,7 @@ \section{Model Overview}
 
   \item \texttt{dataOrigin} (origin of the \texttt{MANGOObject}) : The structure of this class is based on
         the recommendations of the DCP interest group \footnote{https://ivoa.net/documents/DataOrigin/index.html}.
-  \item \texttt{popertyDock} (place holder for all the \texttt{MANGOObject} properties) :
+  \item \texttt{propertyDock} (place holder for all the \texttt{MANGOObject} properties) :
         This is an open-ended collection.
         Mango properties inherit from the base class \texttt{Property},
         which contains everything necessary to identify both their nature and their role.
@@ -267,8 +269,7 @@ \subsection{Properties}
         \caption{MANGO Properties}
         \label{fig:property}
       \end{figure}
-
-\subsubsection{Supported Properties}
+      \subsubsection{Supported Properties}
 
 \begin{table}[h!]
 \small
@@ -300,10 +301,9 @@ \subsubsection{Supported Properties}
  \end{table}
 This initial release supports a limited list of properties, listed in table \ref{table:properties}, that address the most common use cases.
 
+All of these components are described in alphabetical order in the next section. 
 
 
-All of these components are described in alphabetical order in the next section.
-
 \subsubsection{Property Identification}
 Since the set of properties associated with a particular instance is not defined by the model,
 MANGO cannot define a specific role for each property. However, the model provides different ways
@@ -333,7 +333,6 @@ \subsubsection{MANGO and MIVOT: Structuring Tabular Data}
           with its properties grouped within a container or dock.
     \item Scattered Independent Quantities: Each table row is considered as a collection of independent quantities.
 \end{itemize}
-
 \hfill \break
 
 MIVOT annotations support both approaches:
@@ -357,6 +356,15 @@ \subsubsection{MANGO and MIVOT: Structuring Tabular Data}
 The decision ultimately rests with the data providers.
 However, both options are based on the full-featured MANGO model.
 
+%\section{Model: mango in details} 
+%\label{section:mangomodel_desc}
+%  The purpose of MANGO, which stands for MO-del for AN-notating G-eneric O-objects, is to add an upper level of description to the tabular data of query responses. It allows metadata to be extended, complex quantities to be reconstructed from column values, and properties to be linked. It also allows to specify the origin of the data.
+%Here is an overview of the data model organization. 
+
+%\subsection{Building blocks}
+%  \input{model_principles_head.tex}
+%
+%\subsection{Model Dictionnary}
 \input{model.tex}