|
1 | 1 | \documentclass[11pt,a4paper]{ivoa}
|
2 | 2 | \input tthdefs
|
| 3 | +\tolerance=2000 |
3 | 4 |
|
4 | 5 | \customcss{tablefix.css}
|
5 | 6 | \usepackage{verbatim}
|
@@ -568,7 +569,7 @@ \section{The VOTable Document Structure}
|
568 | 569 | element MUST define \attrval{version}{\ivoaDocversion{}}. All VOTable \ivoaDocversion{} elements come from the
|
569 | 570 | namespace \nolinkurl{http://www.ivoa.net/xml/VOTable/v1.3}. It is recommended to bind
|
570 | 571 | the empty namespace prefix to this URI, as in
|
571 |
| -\attrval{xmlns}{http://www.ivoa.net/xml/VOTable/v1.3}, but instance |
| 572 | +$$\hbox{\attrval{xmlns}{http://www.ivoa.net/xml/VOTable/v1.3}~,}$$ but instance |
572 | 573 | documents are free to use whatever namespace prefix is convenient for them.
|
573 | 574 |
|
574 | 575 | Note that starting with VOTable 1.3, the namespace URI for VOTable will
|
@@ -928,7 +929,7 @@ \subsection{\elem{LINK} Element}
|
928 | 929 | standards that make use of VOTable.
|
929 | 930 |
|
930 | 931 | In addition the \elem{LINK} element
|
931 |
| -may announce the MIME type of the data it references |
| 932 | +may announce the RFC 2046 media type of the data it references |
932 | 933 | with a \attr{content-type} attribute (e.g.\ \attrval{content-type}{image/fits}).
|
933 | 934 | Although this might be overridden by metadata received during the
|
934 | 935 | retrieval operation (e.g.\ the HTTP Content-Type header)
|
@@ -1140,7 +1141,7 @@ \subsection{Extended Datatype \attr{xtype}}
|
1140 | 1141 | and corresponds therefore exactly to the {\em FITS} definitions.
|
1141 | 1142 | It fills the gap between the datatypes
|
1142 | 1143 | known by FITS and those required to express queries
|
1143 |
| -(Astronomical Data Query Language or ADQL, \citet{2008ivoa.spec.1030O}) |
| 1144 | +(Astronomical Data Query Language or ADQL, \citet{2023ivoa.spec.1215M}) |
1144 | 1145 | and their results in tabular form (Table Access Protocol or TAP,
|
1145 | 1146 | \citet{2010ivoa.spec.0327D}).
|
1146 | 1147 |
|
@@ -1184,7 +1185,7 @@ \subsection{Unified Content Descriptors}
|
1184 | 1185 | Two versions of UCDs have been developed:
|
1185 | 1186 | the initial version (UCD1) created at CDS, which uses
|
1186 | 1187 | atomic words separated by underscores (e.g. {\tt POS\_EQ\_RA\_MAIN});
|
1187 |
| -and a more flexible one, UCD1+ \citep{2021ivoa.spec.0616C}, |
| 1188 | +and a more flexible one, UCD1+ \citep{2023ivoa.spec.0125C}, |
1188 | 1189 | developed in the frame of the IVOA Semantics Working Group, which uses
|
1189 | 1190 | a reduced vocabulary of dot-separated atoms which can be
|
1190 | 1191 | combined with semi-colons (e.g. {\tt pos.eq.ra;meta.main}).
|
|
0 commit comments