From c0fb8eada1b0ce77ec5f2416447bb5435c21eaa1 Mon Sep 17 00:00:00 2001 From: Markus Demleitner Date: Tue, 30 Apr 2024 13:23:59 +0200 Subject: [PATCH] Some minor style suggestions. I hope none of this changes anything normative, but all of it helps improving the presentation. --- VOTable.tex | 33 +++++++++++++++++---------------- ivoatex | 2 +- 2 files changed, 18 insertions(+), 17 deletions(-) diff --git a/VOTable.tex b/VOTable.tex index 87a8376..126c5ec 100644 --- a/VOTable.tex +++ b/VOTable.tex @@ -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 @@ -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} diff --git a/ivoatex b/ivoatex index 4cb591c..dd11806 160000 --- a/ivoatex +++ b/ivoatex @@ -1 +1 @@ -Subproject commit 4cb591cb784bd06378b537cff05a02e658aad143 +Subproject commit dd1180689db58b7660fbfea9f38a9db953650629