Skip to content

Wd1.6/mivot mango #88

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
lmichel wants to merge 2 commits into
base: master
Choose a base branch
from
Draft

Wd1.6/mivot mango #88

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b452666
liter MIVOT mention in section 3.6 (RESOURCE)
lmichel Apr 14, 2026
2be8f6d
mention of MANGO in section 3.6 (COOSYS) as generic way of describing
lmichel Apr 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 16 additions & 9 deletions VOTable.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -774,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.
Expand Down Expand Up @@ -902,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
Expand Down
Loading