diff --git a/Makefile b/Makefile index 959ab51..4367a78 100644 --- a/Makefile +++ b/Makefile @@ -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 diff --git a/VODataService-v1.3.xsd b/VODataService-v1.3.xsd index c82ec8f..57a0062 100644 --- a/VODataService-v1.3.xsd +++ b/VODataService-v1.3.xsd @@ -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"> @@ -1004,7 +1004,7 @@ The unit associated with the values in the parameter - or column. + or column. This should use VOUnits syntax. @@ -1472,49 +1472,6 @@ - - - - A description of standard space-time coordinate systems, - positions, and regions. - - - 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. - - - - - - - - - - - An STC description of coordinate systems, - positions, and/or regions - - - Each system, position, and region description - should have a an XML ID assigned to it. - - - Because the STC schema sets - elementFormDefault="qualified", it is - recommended that this element specify the STC - default namespace via an xmlns namespace. - - - - - - - - - diff --git a/VODataService.tex b/VODataService.tex index 682e644..9028da3 100644 --- a/VODataService.tex +++ b/VODataService.tex @@ -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} @@ -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} @@ -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 @@ -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} @@ -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 @@ -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} @@ -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} @@ -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} @@ -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} @@ -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 @@ -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} diff --git a/ipac-resource.xml b/ipac-resource.xml index 7a5d81a..64c23d1 100644 --- a/ipac-resource.xml +++ b/ipac-resource.xml @@ -98,7 +98,7 @@ http://nedwww.ipac.caltech.edu/cgi-bin/nph-datasearch?search_type=Redshifts& The radial velocity , derived from derived from the shift of some spectral feature, in km/sec - km/sec + km/s spect.dopplerVeloc int diff --git a/role_diagram.pdf b/role_diagram.pdf index 41152fb..20c7449 100644 Binary files a/role_diagram.pdf and b/role_diagram.pdf differ diff --git a/role_diagram.svg b/role_diagram.svg index 2507b93..6f4ae33 100644 --- a/role_diagram.svg +++ b/role_diagram.svg @@ -46,4 +46,5 @@ STC VOSI MOC + VOUnits diff --git a/role_diagram.xml b/role_diagram.xml index ecbbf16..1f94739 100644 --- a/role_diagram.xml +++ b/role_diagram.xml @@ -20,4 +20,5 @@ with missing dependencies. + diff --git a/samples/catalogservice.xml b/samples/catalogservice.xml index 098b359..d84cf41 100644 --- a/samples/catalogservice.xml +++ b/samples/catalogservice.xml @@ -99,7 +99,7 @@ The radial velocity , derived from derived from the shift of some spectral feature, in km/sec - km/sec + km/s src.spect.dopplerVeloc int diff --git a/samples/extendedtable.xml.no-test b/samples/extendedtable.xml.no-test deleted file mode 100644 index 6b7c31f..0000000 --- a/samples/extendedtable.xml.no-test +++ /dev/null @@ -1,132 +0,0 @@ - - - The NASA/IPAC Extragalactic Database - NED_redshift - ivo://ned.ipac/Redshift_By_Object_Name - - The NASA/IPAC Extragalactic Database - - Olga Pevunova - contact@datacenter.edu - - - - redshift - galaxies - - NED is built around a master list of extragalactic objects for - which cross-identifications of names have been established, - accurate positions and redshifts entered to the extent possible, - and some basic data collected. This service will return recorded - redshifts for a given object. - - http://nedwww.ipac.caltech.edu/help/data_help.html#zdat - BasicData - Research - - - - http://nedwww.ipac.caltech.edu/cgi-bin/nph-datasearch?search_type=Redshifts& - GET - application/xml+votable - - objname - Name of object - string - - - of - Output format parameter, must be "xml_main" for VOTable output. - string - - - - - - - - - - - - - - Radio - Millimeter - Infrared - Optical - UV - EUV - X-ray - Gamma-ray - - - - - default - - default - - No. - - A sequential data-point number applicable to this list only. - - meta.number - INTEGER - - - Name in Publication - - The object's name in NED's standard format, of the object - to which the data apply. - - meta.id;name - VARCHAR - - - Published Velocity - - The radial velocity , derived from derived from the shift - of some spectral feature, in km/sec - - km/sec - src.spect.dopplerVeloc - INTEGER - -
- - - coord1 - REAL - degrees - - pos - VARCHAR - - - - - area - REAL - degrees - - region - - REGION - - - - - diff --git a/samples/specsample.xml b/samples/specsample.xml index 9bba7cc..0bbda1f 100644 --- a/samples/specsample.xml +++ b/samples/specsample.xml @@ -100,7 +100,7 @@ The radial velocity , derived from derived from the shift of some spectral feature, in km/sec - km/sec + km/s src.spect.dopplerVeloc int diff --git a/samples/stc.xml b/samples/stc.xml deleted file mode 100644 index d1856ae..0000000 --- a/samples/stc.xml +++ /dev/null @@ -1,63 +0,0 @@ - - - - 4 - Standard Space-time Coordinate Systems - STC - ivo://STClib/CoordSys - - - - Harvard-Smithsonian Center for Astrophysics - - - Arnold Rots - - Dr. Raymond Plante - 2006-06-01 - - Arnold Rots - arots@hea.cfa.harvard.edu - - - - - world coordinate systems - - This represents a set of standard Coordinate Systems that may - be used to referenced in coverage descriptions. This includes - UTC-FK5-TOPO, a common FK5-based system. - - http://hea-www.harvard.edu/~arots/nvometa/v1.30/ - BasicData - University - Research - - - - - - - UTC - - - - - J2000.0 - - - - - - - - -