From 439f6e965c35cd93774864ce3a800b3990defd03 Mon Sep 17 00:00:00 2001 From: lmichel Date: Fri, 27 Sep 2024 11:31:04 +0200 Subject: [PATCH 1/2] (little) work on the MIVOT section --- .gitignore | 2 +- VOHE-Note.tex | 15 +++++++++------ 2 files changed, 10 insertions(+), 7 deletions(-) diff --git a/.gitignore b/.gitignore index 6682403..607fc84 100644 --- a/.gitignore +++ b/.gitignore @@ -13,4 +13,4 @@ *.pdf *.toc ivoatexmeta.tex - +.project diff --git a/VOHE-Note.tex b/VOHE-Note.tex index e9cd4ac..ce82581 100644 --- a/VOHE-Note.tex +++ b/VOHE-Note.tex @@ -561,12 +561,15 @@ \subsubsection{MOCs} \subsubsection{MIVOT} -Model Instances in VOTables (MIVOT) defines a syntax to map VOTable data to any model serialized in VO-DML. The annotation operates as a bridge between the data and the model. It associates the column/param metadata from the VOTable to the data model elements (class, attributes, types, etc.) [...]. The data model elements are grouped in an independent annotation block complying with the MIVOT XML syntax. This annotation block is added as an extra resource element at the top of the VOTable result resource. The MIVOT syntax allows to describe a data structure as a hierarchy of classes. It is also able to represent relations and composition between them. It can also build up data model objects by aggregating instances from different tables of the VOTable. -In the case of HE data, this annotation pattern, used together with the MANGO model, will help to make machine-readable quantities that are currently not considered in the VO, such as the hardness ratio, the energy bands, the flags associated with measurements or extended sources. -% (LM) - -\todo[inline]{To be completed} - +Model Instances in VOTables (MIVOT _cite{2023ivoa.spec.0620M}) defines a syntax to map VOTable data to any model serialized in VO-DML. +The annotation operates as a bridge between the data and the model. +It associates the column/param metadata from the VOTable to the data model elements (class, attributes, types, etc.) [...]. +The data model elements are grouped in an independent annotation block complying with the MIVOT XML syntax. +his annotation block is added as an extra resource element at the top of the VOTable result resource. +The MIVOT syntax allows to describe a data structure as a hierarchy of classes. +It is also able to represent relations and composition between them. It can also build up data model objects by aggregating instances from different tables of the VOTable. +In the case of HE data, this annotation pattern, used together with the MANGO model, will help to make machine-readable quantities that are currently not considered in the VO, +such as the hardness ratio, the energy bands, the flags associated with measurements or extended sources. \subsubsection{Provenance} From c6d4466d70543cdb429fe2045495e2fdc1668abb Mon Sep 17 00:00:00 2001 From: lmichel Date: Fri, 27 Sep 2024 11:38:00 +0200 Subject: [PATCH 2/2] typo --- VOHE-Note.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/VOHE-Note.tex b/VOHE-Note.tex index ce82581..41c5e7d 100644 --- a/VOHE-Note.tex +++ b/VOHE-Note.tex @@ -561,7 +561,7 @@ \subsubsection{MOCs} \subsubsection{MIVOT} -Model Instances in VOTables (MIVOT _cite{2023ivoa.spec.0620M}) defines a syntax to map VOTable data to any model serialized in VO-DML. +Model Instances in VOTables (MIVOT \cite{2023ivoa.spec.0620M}) defines a syntax to map VOTable data to any model serialized in VO-DML. The annotation operates as a bridge between the data and the model. It associates the column/param metadata from the VOTable to the data model elements (class, attributes, types, etc.) [...]. The data model elements are grouped in an independent annotation block complying with the MIVOT XML syntax.