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

Volute commit messages volutecommits at g-vo.org
Mon Apr 30 19:07:14 CEST 2018


Author: francois
Date: Mon Apr 30 19:07:14 2018
New Revision: 4944

Log:
modification of the note / full utype part

Modified:
   trunk/projects/time-domain/time-series/note/TSSerializationNote.bbl
   trunk/projects/time-domain/time-series/note/TSSerializationNote.pdf
   trunk/projects/time-domain/time-series/note/appendixFrancois.tex
   trunk/projects/time-domain/time-series/note/francois.tex

Modified: trunk/projects/time-domain/time-series/note/TSSerializationNote.bbl
==============================================================================
--- trunk/projects/time-domain/time-series/note/TSSerializationNote.bbl	Mon Apr 30 18:43:18 2018	(r4943)
+++ trunk/projects/time-domain/time-series/note/TSSerializationNote.bbl	Mon Apr 30 19:07:14 2018	(r4944)
@@ -1,3 +1,3 @@
 \begin{thebibliography}{xx}
-\bibitem{gl:mapping} Lemson, Laurino, et al. \emph{Mapping Data Models to VOTable}, 2017
+
 \end{thebibliography}

Modified: trunk/projects/time-domain/time-series/note/TSSerializationNote.pdf
==============================================================================
Binary file (source and/or target). No diff available.

Modified: trunk/projects/time-domain/time-series/note/appendixFrancois.tex
==============================================================================
--- trunk/projects/time-domain/time-series/note/appendixFrancois.tex	Mon Apr 30 18:43:18 2018	(r4943)
+++ trunk/projects/time-domain/time-series/note/appendixFrancois.tex	Mon Apr 30 19:07:14 2018	(r4944)
@@ -1,6 +1,6 @@
 \section{VODataservice tableset mapping of TimeSeries}
 
-This appendix points to three vodatservice "tableset" descriptions.
+This appendix points to five vodatservice "tableset" descriptions.
 
 The first xml document corresponds to example 1 of full-utype serialisation. It contains the table definitions for the TimeSeries metadata and 
 the absolutely minimal content for the data table with two column definitions.
@@ -12,6 +12,12 @@
 The third xml-document corresponds to example 3 of full-type serialisation. The data table is very complex and most of the dependant measurements definitions have to be refined using ucds.
 (http://volute.g-vo.org/svn/trunk/projects/time-domain/time-series/standardized\_votables/francois/TimeSeries-GAPS-vos-tableset.xml)
 
+The fourth and fifth xml documents correspond to the two Gaia examples : in 3 tables or ib one single table. Note that in the 3 table case, each of the three "data" tables actually represent an instance of SparseCube.
+
+( http://volute.g-vo.org/svn/trunk/projects/time-domain/time-series/standardized\_votables/francois/TimeSeries-Gaia3tables-vos-tableset.xml \\
+and \\
+http://volute.g-vo.org/svn/trunk/projects/time-domain/time-series/standardized\_votables/francois/GaiaDR2Example-time-series.xml)
+ 
 TimeSeries projects in the VO will present very different flavors of the model, expressed as one specific tableset  
 
 

Modified: trunk/projects/time-domain/time-series/note/francois.tex
==============================================================================
--- trunk/projects/time-domain/time-series/note/francois.tex	Mon Apr 30 18:43:18 2018	(r4943)
+++ trunk/projects/time-domain/time-series/note/francois.tex	Mon Apr 30 19:07:14 2018	(r4944)
@@ -1,8 +1,10 @@
 \subsection{Full utype serialisation} 
 
-In this approach, a relational view of the TimeSeries described above is provided. Hierarchies of classes showing 1 to 1 relationships are grouped in one single table. Table x shows the list of tables used to map the model with the full set of their columns metadata ( utype, datatype, ucd, unit and xtype).
+In this approach,  relational views of the TimeSeries described above are provided. Hierarchies of classes showing 1 to 1 relationships are grouped in one single table. Table x shows the list of tables used to map the model with the full set of their columns metadata ( utype, datatype, ucd, unit and xtype), in the case of example 1.
 The VODataservice "tableset" representation of this set of tables is described in Appendix. 
 
+Each TimeSeries project as its own subset of attributes of the generic model. This leads to a specific partial relational view of the model. For each of these a dedicated table like table x could be provided. See the tableset representations in Appendix. 
+
 The structure is made of 4 "tables" number which seems to be a compromise to separate very differents groups of classes without having too much of them.
 
 The main "table" is the data table where the actual values of the independant variable (Time stamps) and of the "one to many" varying variables are stored.
@@ -21,7 +23,7 @@
 
 "Tables" mentionned here and described in the Appendix are not required to be serialized as TABLE elements in VOTable. In the case there is only one single TimeSeries in the VOTable document, "generic metadata tables" have only one single instance. They can be serialized as groups and their columns as PARAMS instead of using TABLES with one single row.
 
-The Appendix illustrates the background of the simplest example the serialization of which is provided at following URL : \\ 
+The Appendix illustrates the background of the  examples the serialization of which is provided at the  URL included here, starting with the simplest example : \\ 
 \begin{small}
 http://volute.g-vo.org/svn/trunk/projects/time-domain/time-series/standardized\_votables/\\
 /francois/SDSS\_J080434.20+510349.2\_VizieR\_complete\_utypes.xml \\
@@ -58,3 +60,12 @@
 \end{small}
 
 
+In example 5, the Gaia DR2 TimeSeries with its three bands is organized in a single table.
+
+
+\begin{small}
+(http://volute.g-vo.org/svn/trunk/projects/time-domain/time-series/standardized\_votables/\\
+francois/GaiaDR2Example-time-series.xml) \\
+\end{small}
+
+


More information about the Volutecommits mailing list