Skip to content
Merged
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
6 changes: 3 additions & 3 deletions VOTable.tex
Original file line number Diff line number Diff line change
Expand Up @@ -1515,7 +1515,7 @@ \subsection{\elem{TABLEDATA} Serialization}
then the item is assumed to contain no data.
Valid representations of values in a cell, depending on their
\attr{datatype}, are detailed in \Aref{sec:datatypes}.
If the {\elem{TD}} element is empty ({\verb|<TD/>| or \verb|<TD></TD>|)
If the {\elem{TD}} element is empty ({\verb|<TD/>| or \verb|<TD></TD>|})
the cell is considered to contain no data, i.e.\ to be null.

If a cell contains an array of numbers or a complex number,
Expand Down Expand Up @@ -2164,13 +2164,13 @@ \section{MIME Type}

In the HTTP protocol (RFC 2616), the MIME type is the value specified by the
{\textsf{Content-Type:}} header. The recommended MIME type describing
a VOTable document is {\literalvalue{\textsf{application/x-votable+xml}}:
a VOTable document is {\literalvalue{\textsf{application/x-votable+xml}}}:
the {\bf x-} prefix indicates an experimental type, and
is required for non-registered media types; and the
{\bf+xml} suffix (defined by RFC 3023 section 7)
indicates that the type describes a specialization of XML.
This type may be accompanied by an optional parameter
{\literalvalue{\textsf{serialization}}
{\literalvalue{\textsf{serialization}}}
with a value specifying the serialization type used for table data within the
document, one of TABLEDATA, FITS, BINARY or BINARY2,
interpreted case-insensitively.
Expand Down