From b452666f77562ac21edc095fdbe372c25b19a2b1 Mon Sep 17 00:00:00 2001 From: Laurent MICHEL Date: Tue, 14 Apr 2026 15:38:41 +0200 Subject: [PATCH 1/2] liter MIVOT mention in section 3.6 (RESOURCE) --- VOTable.tex | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/VOTable.tex b/VOTable.tex index 05f6261..2361a71 100644 --- a/VOTable.tex +++ b/VOTable.tex @@ -279,7 +279,16 @@ \subsection{VOTable in the VO Architecture} and hence for exchange of data and metadata between user layer applications and data-providing services. VOTable is also used as a serialization format for -some of the IVOA Data Models. +some of the IVOA Data Models. + +This can be achieved by using metadata required by DAL standards, +or in a more flexible way by using MIVOT (Model Instances in VOTables) annotations \citep{2023ivoa.spec.0620M}. +MIVOT defines a syntax that maps VOTable contents to any model serialized in VO-DML \citep{2018ivoa.spec.0910L}. +MIVOT annotations operate as a bridge between models and data, associating VOTable metadata +with data model entities and potentially adding advanced metadata that cannot be represented in plain VOTable. +MIVOT annotations have their own XML namespace and abide by a specific XML schema, +which has no connection with the VOTable schema ; they are not part of the VOTable standard, +and their use is optional. In order to represent semantically rich metadata, VOTable relies on the other IVOA standards UCD, Utype, VOUnits, and DALI. From 2be8f6da5cc457ddad505c4a8c2b744627b84090 Mon Sep 17 00:00:00 2001 From: Laurent MICHEL Date: Tue, 14 Apr 2026 16:08:53 +0200 Subject: [PATCH 2/2] mention of MANGO in section 3.6 (COOSYS) as generic way of describing sky position --- VOTable.tex | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/VOTable.tex b/VOTable.tex index 2361a71..c37ff52 100644 --- a/VOTable.tex +++ b/VOTable.tex @@ -783,6 +783,10 @@ \subsection{\elem{COOSYS} Element} Also note that \elem{COOSYS} may be deprecated in the future in favor of a more generic way of describing the conventions used to define the positions of the objects studied in the enclosed tables. +This generic approach could involve mapping VOTable data to the MANGO data model (REFERENCE TO MANGO), +which provides a consistent description of complete sky positions, including position, radial velocity, +proper motion, parallax and observation time. All of these are provided with errors, +correlations and coordinate systems (space and time). A \elem{COOSYS} element referenced via a \attr{ref} attribute SHOULD appear before the element that references it. @@ -911,14 +915,8 @@ \subsection{\elem{RESOURCE} Element} For example, a \elem{RESOURCE} qualified by \attrval{type}{meta} can be used to transmit -MIVOT (Model Instances in VOTables) annotations \citep{2023ivoa.spec.0620M}. -MIVOT defines a syntax to map VOTable -contents to any model serizalized in VO-DML \citep{2018ivoa.spec.0910L}. -It operates as a bridge between models and data that associates VOTable -metadata to data model entities, possibly adding advanced metadata not -representable in plain VOTable. -MIVOT annotations have their own XMLnamespace. The VOTable schema allows MIVOT, -and any elements from a foreign namespace, in a \elem{RESOURCE}. +MIVOT annotations (see \ref{sec:voarch}). The VOTable schema allows MIVOT annotations as +any elements from a foreign namespace, in a \elem{RESOURCE}. Finally, the \elem{RESOURCE} element may have a \attr{utype} attribute to link the element to some external data model