# [Volute] r4895 - trunk/projects/time-domain/time-series/note

Volute commit messages volutecommits at g-vo.org
Fri Apr 6 18:31:35 CEST 2018

Author: lmichel
Date: Fri Apr  6 18:31:34 2018
New Revision: 4895

Log:
pdf uptdate

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	Fri Apr  6 14:29:54 2018	(r4894)
+++ trunk/projects/time-domain/time-series/note/laurent.tex	Fri Apr  6 18:31:34 2018	(r4895)
@@ -24,13 +24,13 @@
\end{itemize}

The present section explores a possible simplification of the mapping syntax relying on the strengths of the VO-DML workflow while targeting an easier job for both data providers and data consumers.
-The syntax baseline is designed to provide general-purpose clients (e.g. Aladin, JS widget  \dots) with nothing more than what they need, considering that more advanced clients could retrive in any case any model features within the model itself.
+The syntax baseline is designed to provide general-purpose clients (e.g. Aladin, JS widget  \dots) with nothing more than what they need, considering that more advanced clients could retrieve in any case any model features within the model itself.
This simplification could also improve the reliability of the data annotation process.
This is not a complete proposal, but a proof of concept validated on TD data.

\subsubsection{Mapping Syntax}
\paragraph{Basics}
-The design of this  mapping syntax being not complete, we just describe here the outlines of this simplification and the features required to map the present sample of time domain data.
+The design of this  mapping syntax being not complete, we just describe here the outlines of this simplification and the features we need to map the sample of time domain data.

The <VODML> block keeps split in 3 sections as shown below.