Skip to content
Open
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
2 changes: 1 addition & 1 deletion Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ DOCNAME = VODataService
DOCVERSION = 1.3

# Publication date, ISO format; update manually for "releases"
DOCDATE = 2026-06-01
DOCDATE = 2026-07-15

# What is it you're writing: NOTE, WD, PR, REC, PEN, or EN
DOCTYPE = PR
Expand Down
47 changes: 2 additions & 45 deletions VODataService-v1.3.xsd
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
xmlns:stc="http://www.ivoa.net/xml/STC/stc-v1.30.xsd"
xmlns:vm="http://www.ivoa.net/xml/VOMetadata/v0.1"
elementFormDefault="unqualified" attributeFormDefault="unqualified"
version="1.3-pr1">
version="1.3-pr2">

<xs:annotation>
<xs:appinfo>
Expand Down Expand Up @@ -1004,7 +1004,7 @@
<xs:annotation>
<xs:documentation>
The unit associated with the values in the parameter
or column.
or column. This should use VOUnits syntax.
</xs:documentation>
</xs:annotation>
</xs:element>
Expand Down Expand Up @@ -1472,49 +1472,6 @@
</xs:simpleContent>
</xs:complexType>

<xs:complexType name="StandardSTC">
<xs:annotation>
<xs:documentation>
A description of standard space-time coordinate systems,
positions, and regions.
</xs:documentation>
<xs:documentation>
This resource type is deprecated, and no resource records
of this type exist in the Registry. It will be removed
in version 1.3 of VODataService.
</xs:documentation>
</xs:annotation>

<xs:complexContent>
<xs:extension base="vr:Resource">
<xs:sequence>

<xs:element name="stcDefinitions"
type="stc:stcDescriptionType"
minOccurs="1" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>
An STC description of coordinate systems,
positions, and/or regions
</xs:documentation>
<xs:documentation>
Each system, position, and region description
should have a an XML ID assigned to it.
</xs:documentation>
<xs:documentation>
Because the STC schema sets
elementFormDefault="qualified", it is
recommended that this element specify the STC
default namespace via an xmlns namespace.
</xs:documentation>
</xs:annotation>
</xs:element>

</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>

<xs:complexType name="ForeignKey">
<xs:annotation>
<xs:documentation>
Expand Down
53 changes: 31 additions & 22 deletions VODataService.tex
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,7 @@
\editor{Markus Demleitner}
\editor{Ray Plante}

\previousversion[https://www.ivoa.net/documents/VODataService/20260601]{PR-1.3-20260601}
\previousversion[https://www.ivoa.net/documents/VODataService/20260324]{WD-1.3-20260324}
\previousversion[https://www.ivoa.net/documents/VODataService/20241113]{WD-1.3-20241113}
\previousversion[https://www.ivoa.net/documents/VODataService/20211102]{REC-1.2}
Expand Down Expand Up @@ -192,6 +193,8 @@ \subsection{The Role in the IVOA Architecture}
to support the space-time constraints added here.
\item[MOC, v2.0 \citep{2022ivoa.spec.0727F}] Multi-Order coverage maps
are used by VODataService to communicate spatial coverage.
\item[VOUnits, v1.1 \citep{2023ivoa.spec.1215G}] Tablesets should use
VOUnits syntax.
\end{description}

\subsection{Purpose}
Expand All @@ -211,8 +214,8 @@ \subsection{Purpose}
Resource records using VODataService types are commonly used to register
services that support standard IVOA data access layer protocols such
as Simple Image Access \citep{2015ivoa.spec.1223D} and Simple Cone Search
\citep{2008ivoa.specQ0222P}. As of October 2018, there are more than
20000~resources of type \xmlel{vs:CatalogService} in the VO Registry.
\citep{2008ivoa.specQ0222P}. As of July 2026, there are more than
31'000~resources of type \xmlel{vs:CatalogService} in the VO Registry.

While other VOResource extensions
define the protocol-specific metadata (encapsulated as a standard
Expand Down Expand Up @@ -543,11 +546,13 @@ \subsubsection{VODataService Resource Classes}

Two further resource classes defined by VODataService 1.1,
\xmlel{vs:DataCollection} and \xmlel{vs:StandardSTC},
are deprecated since version 1.2.
have been deprecated since version 1.2.
Resource record authors are requested to migrate or discard resource
records using these deprecated types. If all such records have
disappeared from the VO by version 1.4 of this specification, their
type declarations may be removed from the schema.
records using these deprecated types. \xmlel{vs:StandardSTC} has been
dropped in VODataService 1.3 since there were no resource records using
that type in the VO Registry. We will similarly drop
\xmlel{vs:DataCollection} when the last records using the type have
vanished from the Registry.

\subsubsection{Discovering Data Within Other Services}
\label{sect:discoverdata}
Expand Down Expand Up @@ -757,9 +762,9 @@ \subsubsection{DataResource}
\url{http://www.ivoa.net/rdf/data-source} contains these terms:

% GENERATED: !vocterms data-source
\textsl{artificial},
\textsl{observation},
\textsl{theory}
\textsl{abstract-model},
\textsl{concrete-model},
\textsl{observation}
% /GENERATED

Following previous VO practice, resources giving no data source can be
Expand Down Expand Up @@ -1014,16 +1019,6 @@ \subsubsection{DataCollection}
This type may be removed from the schema when all resource records using
it have vanished from the VO Registry.

\subsubsection{StandardSTC}

The \xmlel{vs:StandardSTC} type is deprecated and should no longer be
used in new resource records. Since the XML serialisation of the STC 1
data model was never promoted to an IVOA recommendation, there also is
no properly standardised way of creating such records. Since no such
records ever existed in the Registry, this type will probably be removed
from the schema in version 1.4 of this specification.



\subsection{Coverage in Space, Time, and Spectrum}
\label{sect:cover}
Expand Down Expand Up @@ -2100,7 +2095,7 @@ \subsection{Data Parameters}
\begin{description}
\item[Type] string: \xmlel{xs:token}
\item[Meaning] The unit associated with the values in the parameter
or column.
or column. This should use VOUnits syntax.
\item[Occurrence] optional

\end{description}
Expand Down Expand Up @@ -2225,7 +2220,7 @@ \subsection{Data Parameters}
\item[Element \xmlel{percentile97}]
\begin{description}
\item[Type] floating-point number: \xmlel{xs:double}
\item[Meaning] The 97nd percentile (“2σ”) in a distribution of numbers.
\item[Meaning] The 97th percentile (“2σ”) in a distribution of numbers.
\item[Occurrence] optional

\end{description}
Expand Down Expand Up @@ -2729,7 +2724,7 @@ \subsubsection{Table Columns}
\item[Type] boolean (true/false): xs:boolean
\item[Meaning] If true, the meaning and use of this parameter is
reserved and defined by a standard model. If false,
it represents a parameter specific to the data described
it represents a parameter specific to the data described.
If not provided, then the value is unknown.
\item[Occurrence] optional
\end{description}
Expand Down Expand Up @@ -2786,6 +2781,12 @@ \subsubsection{Table Columns}
sect.~\ref{sect:tbldatatypes}, this SHOULD be
\xmlel{vs:VOTableType} for VODataService 1.3 table columns.

Units specified for columns and params SHOULD follow the VOUnits grammar
\citep{2023ivoa.spec.1215G}, which is particularly important for clients
obtaining them from VOSI tables endpoint with the intent of using them
for automatic unit conversions. New implementors should consider
VOUnits compliance a MUST rather than a SHOULD.

When the tableset describes a set of TAP-accessible tables, the value of
a \xmlel{tableColumn}'s \xmlel{name} child must be in a form immediately
usable for use in ADQL or SQL queries. This corresponds to the analogous
Expand Down Expand Up @@ -2930,6 +2931,14 @@ \subsubsection{Table Column Data Types}

\section{Changes from previous versions}

\subsection{Changes since PR-1.3-20260601}

\begin{itemize}
\item Dropping an outdated example for how one would do ADQL functions
in the tableset (which we don't do).
\item Dropping StandardSTC after all.
\end{itemize}

\subsection{Changes since WD-1.3-20260324}

\begin{itemize}
Expand Down
2 changes: 1 addition & 1 deletion ipac-resource.xml
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,7 @@ http://nedwww.ipac.caltech.edu/cgi-bin/nph-datasearch?search_type=Redshifts&amp;
The radial velocity , derived from derived from the shift
of some spectral feature, in km/sec
</description>
<unit>km/sec</unit>
<unit>km/s</unit>
<ucd>spect.dopplerVeloc</ucd>
<dataType xsi:type="vs:VOTableType">int</dataType>
</column>
Expand Down
Binary file modified role_diagram.pdf
Binary file not shown.
1 change: 1 addition & 0 deletions role_diagram.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
1 change: 1 addition & 0 deletions role_diagram.xml
Original file line number Diff line number Diff line change
Expand Up @@ -20,4 +20,5 @@ with missing dependencies.
<rec name="STC" x="550" y="230"/>
<rec name="VOSI" x="540" y="435"/>
<rec name="MOC" x="430" y="400"/>
<rec name="VOUnits" x="220" y="250" w="50"/>
</archdiag>
2 changes: 1 addition & 1 deletion samples/catalogservice.xml
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,7 @@
The radial velocity , derived from derived from the shift
of some spectral feature, in km/sec
</description>
<unit>km/sec</unit>
<unit>km/s</unit>
<ucd>src.spect.dopplerVeloc</ucd>
<dataType xsi:type="vs:VOTableType">int</dataType>
</column>
Expand Down
132 changes: 0 additions & 132 deletions samples/extendedtable.xml.no-test

This file was deleted.

2 changes: 1 addition & 1 deletion samples/specsample.xml
Original file line number Diff line number Diff line change
Expand Up @@ -100,7 +100,7 @@
<description>
The radial velocity , derived from derived from the shift of some spectral feature, in km/sec
</description>
<unit>km/sec</unit>
<unit>km/s</unit>
<ucd>src.spect.dopplerVeloc</ucd>
<dataType xsi:type="vs:VOTableType">int</dataType>
</column>
Expand Down
Loading