Skip to content

Commit 0635b3d

Browse files
committed
typo fixing and history cleaned
1 parent c293414 commit 0635b3d

File tree

1 file changed

+5
-10
lines changed

1 file changed

+5
-10
lines changed

ConeSearch.tex

Lines changed: 5 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -234,7 +234,7 @@ \subsection{Succesful response}
234234
VOTable\citep{2025ivoa.spec.0116O} format. However, if RESPONSEFORMAT is
235235
set (see Sec.~\ref{subsec:baseurl}) the response table \textbf{should}
236236
match the requested format; if this format is unsupported the request
237-
textbf{should} fail.
237+
\textbf{should} fail.
238238

239239
When the response is in the default VOTable format (see Appendix \ref{appendix:a}
240240
for an example), the MIME-type of the HTTP response \textbf{should} be
@@ -617,16 +617,11 @@ \section{Changes from Previous Versions}
617617

618618
\subsection*{Changes from WD-1.1-20200828}
619619
\begin{itemize}
620-
\item prescribed DALI VOTable response usage, including error
621-
responses and usage of the OVERFLOW indicator
622-
\item added DALI MAXREC and RESPONSEFORMAT parameters, for response
623-
flexibility and DALI alignment
620+
\item included OVERFLOW indicator (updating MAXREC usage)
624621
\item updated all UCD(s) to conform to the UCD1+ specification
625-
\item introduced flexibility on the decimal (float or double) behaviour
626-
for RA and Dec in responses (and explicitly stated that they must be
627-
in units of decimal degrees)
628-
\item clarified that the single RESOURCE with single table is meant
629-
for results only, without preventing other RESOURCE types to be present
622+
\item explicitly stated that RA and Dec responses must be
623+
in units of decimal degrees
624+
\item re-instated changes done in the previous WD-1.1-20200828
630625
\item embedded errata 1, 2 and 3 for ConeSearch-1.03
631626
\item Complete revert of changes to restore clean 1.03 contents,
632627
in view of specific minor updates (listed here above)

0 commit comments

Comments
 (0)