[Volute] r4901 - trunk/projects/time-domain/time-series/note

Volute commit messages volutecommits at g-vo.org
Tue Apr 10 13:01:57 CEST 2018


Author: lmichel
Date: Tue Apr 10 13:01:57 2018
New Revision: 4901

Log:
table update

Modified:
   trunk/projects/time-domain/time-series/note/laurent.tex

Modified: trunk/projects/time-domain/time-series/note/laurent.tex
==============================================================================
--- trunk/projects/time-domain/time-series/note/laurent.tex	Tue Apr 10 11:37:15 2018	(r4900)
+++ trunk/projects/time-domain/time-series/note/laurent.tex	Tue Apr 10 13:01:57 2018	(r4901)
@@ -34,47 +34,62 @@
 
 The <VODML> block keeps split in 3 sections as shown below.
 
-\smallskip 
-\scriptsize
-\begin{tabular}{|r|l|}
+\begin{table}[th]
+  \begin{center}
+  \scriptsize
+  \caption{Main mapping elements.}\label{tab:mapping_elements}
+    \begin{tabular}{rl}
+      \sptablerule
 
-\hline
    <MODELS> & References to all referenced models (models + imports) \\
    <GLOBALS> & Not implemented here \\   
-   <TEMPLATES> & \makecell[l]{One template per table} \\
-\hline
-\end{tabular}
-\normalsize
-\smallskip 
-
-Each template refers to a particular table and contains de mapping of the classes hosted by that table. The mapping is bases on the 3 concepts necassary to describe a hierarchy of classes:
-
-
-\smallskip 
-\scriptsize
-\begin{tabular}{|r|l|}
-\hline
-   <VALUE> & \makecell[l]{Model leaf. It either points to a PARAM or a FIELD \\or it has its own value like a literal}  \\ \hline
-   <INSTANCE> & \makecell[l]{Denotes a class.\\ An <INSTANCE> is a tuple of elements which can be either \\ <VALUE>, <INSTANCE> or <COLLECTION>}  \\ \hline
-   <COLLECTION> & \makecell[l]{Denotes a list or an array. \\ A collection can contain  be either \\ <VALUE>, <INSTANCE> or <COLLECTION>} \\\hline
-\end{tabular}
-\normalsize
-\smallskip 
+   <TEMPLATES> & One template per table \\
+      \sptablerule
+    \end{tabular}
+  \normalsize
+  \end{center}
+%  \textbf{Note:} $^1$For SSO or moving objects coordinates might not be enough or relevant. 
+\end{table}
+Each template refers to a particular table and contains de mapping of the classes hosted by that table. 
+The mapping is based on the 3 concepts necassary to describe a hierarchy of classes:
+
+\smallskip
+\begin{table}[th]
+  \begin{center}
+  \scriptsize
+  \caption{Mapping element roles.}\label{tab:mapping_elements}
+    \begin{tabular}{rp{0.75\textwidth}l}
+      \sptablerule
+   <VALUE> & Model leaf. Either points to a <PARAM> or a <FIELD> or it has its own value like a literal  \\ \sptablerule
+   <INSTANCE> & Denotes a class. An <INSTANCE> is a tuple of elements which can be either  <VALUE>, <INSTANCE> or <COLLECTION>  \\ \sptablerule
+   <COLLECTION> & Denotes a list or an array.  A collection can contain  be either  <VALUE>, <INSTANCE> or <COLLECTION> \\\sptablerule
+
+    \end{tabular}
+  \normalsize
+  \end{center}
+%  \textbf{Note:} $^1$For SSO or moving objects coordinates might not be enough or relevant. 
+\end{table} 
 
  Each one of these elements supports some attributes wich can be mandatory (mand.) or optional (opt). It should be noted that some attributes such as units or formats are not described here as well as the foreign key mechanism. 
 
-\smallskip 
-\scriptsize
-\begin{tabular}{|r|c|c|c|c|c|c|}
-\hline
-    Attribute:     & \textbf{@dmrole} & \textbf{@dmtype} & \textbf{@ref} & \textbf{@tableref} & \textbf{@size} & \textbf{@value} \\ \hline
-   <VALUE>  & mand. & none & mand. if no @value & none & none & mand. if no @ref \\ \hline   
-   <INSTANCE>  & mand. & opt. & none & opt. & none & none \\ \hline  
-  <COLLECTION>  & mand. & none & none & none & opt & none \\ \hline
-
-\end{tabular}
-\normalsize
-\smallskip 
+\begin{table}[th]
+  \begin{center}
+  \scriptsize
+  \caption{Mapping element attributes.}\label{tab:mapping_elements}
+    \begin{tabular}{cp{1cm}cp{1cm}cp{1cm}cp{1cm}cp{1cm}cp{1cm}cp{1cm}cp{1cm}}
+      \sptablerule
+    Attribute:     & \textbf{@dmrole} & \textbf{@dmtype} & \textbf{@ref} & \textbf{@tableref} & \textbf{@size} & \textbf{@value} \\ \sptablerule
+   <VALUE>  & mand. & none & mand. if no @value & none & none & mand. if no @ref \\ \sptablerule   
+   <INSTANCE>  & mand. & opt. & none & opt. & none & none \\ \sptablerule  
+  <COLLECTION>  & none & none & none & none & opt & none \\ \sptablerule
+
+    \end{tabular}
+  \normalsize
+  \end{center}
+%  \textbf{Note:} $^1$For SSO or moving objects coordinates might not be enough or relevant. 
+\end{table} 
+
+
 
 \paragraph{<VALUE>}
 The @dmrole attribute is the one set in the VO-DML model. Other VO-DML attributes (e.g. @dmtype) can be retrieved in the VO-DML file from the location of the <VALUE> element and from its @dmrole.


More information about the Volutecommits mailing list