Skip to content
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.

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

Some minor style suggestions. #61

Merged
merged 1 commit into from
Oct 21, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
33 changes: 17 additions & 16 deletions VOTable.tex
Original file line number Diff line number Diff line change
Expand Up @@ -863,14 +863,16 @@ \subsection{\elem{RESOURCE} Element}
should exist in any of its sub-elements. A \elem{RESOURCE} without
this attribute {\em may} however have no \elem{DATA} sub-element.

\elem{RESOURCE} qualified by \attrval{type}{meta} can be used e.g. to host
\elem{RESOURCE} elements qualified by
\attrval{type}{meta} are also used to transmit
MIVOT (Model Instances in VOTables) annotations \citep{2023ivoa.spec.0620M}.
MIVOT defines a syntax to map VOTable
data to any model serizalized in VO-DML \citep{2018ivoa.spec.0910L}.
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 leaves.
It also brings up data or metadata that were possibly missing in the actual dataset.
MIVOT annotations have their own namespace; they have no impact on the VOTable schema.
metadata to data model entities, possibly adding advanced metadata not
representable in plain VOTable.
MIVOT annotations have their own XMLnamespace;
they have no impact on the VOTable schema.

Finally, the \elem{RESOURCE} element may have a \attr{utype} attribute
to link the element to some external data model
Expand Down Expand Up @@ -1138,20 +1140,19 @@ \subsection{Extended Datatype \attr{xtype}}
and their results in tabular form (Table Access Protocol or TAP,
\citet{2010ivoa.spec.0327D}).

The \attr{xtype} attribute is the way to
specify that a parameter represents a {\em timestamp}
As an example, setting \attrval{xtype}{timestamp} instructs VOTable
parsers to interpret a string as a {\em timestamp}
(an instant in an absolute time frame), materialized by a
UTC date/time string following the ISO-8601 standard
({\tt YYYY-MM-DDThh:mm:ss} eventually followed by a decimal point
and fractions of seconds);
parameters required to specify a spatial position may also have an associated
\attr{xtype}.

The actual values of the \attr{xtype} attribute are not defined
in this VOTable specification.
The IVOA recommendation Data Access Layer Interface
or DALI \citep{2017ivoa.spec.0517D},
defines the use of \attr{xtype} for various use cases.
and fractions of seconds). Supporting parsers might then expose the
corresponding values in whatever way appropriate for such timestamps in
the host language. VOTables software does not need to interpret xtypes,
but it should preserve them when doing round-trips.

The IVOA recommendation Data Access Layer Interface DALI
\citep{2017ivoa.spec.0517D} defines the common values of \attr{xtype}
and the literals of conforming column values.

\subsection{Units}
\label{sec:unit}
Expand Down
2 changes: 1 addition & 1 deletion ivoatex