International Virtual Observatory Alliance

Difference: VOTable15RFC (3 vs. 4)

Revision 42024-03-04 - TomDonaldson

META TOPICPARENT	name="IvoaResReg"

VOTable 1.5 Proposed Recommendation: Request for Comments

VOTable is a standard for the interchange of data represented as a set of tables, and includes both table metadata and the data itself.

Summary

Latest Draft: VOTable 1.5 (Proposed Recommendation)

The main purpose of VOTable 1.5 is to support refposition attribute analogous to TIMESYS.

VOTable 1.5 is a backward-compatible revision.

The other main differences between version 1.5 of VOTable and the preceding version 1.4 are:

COOSYS now has a refposition attribute analogous to TIMESYS.
The frame identifiers (system attribute) in COOSYS are now taken from the refframe IVOA vocabulary.
Clarifications and rewording on:
- the meaning of MIN and MAX value attributes for array types.
- removing the recommendation to use xmlns to do utype prefix binding.
- timescales for calendar epochs.
- positioning advice for ID and corresponding references.
- noting that RESOURCE elements can contain MIVOT blocks.
- unit attribute SHOULD conform to VOUnits, and correct examples accordingly.

Changed:

<
< See GitHub for a full list of changes.

>
> See GitHub for a full list of changes.

To Do Upon Approval, Prior to Upload

Change version attribute in schema to "1.5"
In the document, set the \ivoatype to "IVOA Recommendation" and set the status text according to the official wording is in DocStd.

Future

The VOTableInfo page contains a list of proposed changes that, during the WD phase, were agreed to defer to a future version. When the document maintenance is transitioned to GitHub, those item will be converted to GitHub issues.

Reference Interoperable Implementations

Changed:

<
<

AladinProto: TIMESYS and COOSYS full support

>
> DaCHS produces COOSYS refposition in TAP results from the gaia.dr3lite table in the GAVO Data Center TAP service which can be read by the prerelease versions of STILTS ( stilts.jar) and TOPCAT ( topcat-full.jar). For example:

Deleted:

<
<

DaCHS 1.2.6 (beta) produces TIMESYS. Deployed services serving time series with TIMESYS include ivo://org.gavo.dc/gaia/q2/dr2epochflux, ivo://org.gavo.dc/bgds/l/ssa, and ivo://org.gavo.dc/k2c9vst/q/ssa, as well as the datalink-linked datasets from the gaia.dr2epochflux, bgds.ssa_time_series, and k2c9vst.timeseries tables in http://dc.g-vo.org/tap
STIL v3.3-3/ STILTS v3.1-6/ TOPCAT v4.6-3 support VOTable 1.4 (PR-VOTable-1.4-20190604): COOSYS and TIMESYS elements are ingested and the relevant properties are attached to columns in the internal table data model, and can be seen in the library/application column metadata. The same attributes are written out, though currently for TIMESYS only if output VOTable version is set to "1.4" ( -Dvotable.version=1.4). These applications don't do much with the information beyond making it visible, though (experimental) time plots use the timeorigin and (in most cases) time units to offset temporal coordinates.

Added:

>
>

STILTS shows the metadata from the GAVO TAP results:
- stilts tapquery tapurl=http://dc.g-vo.org/tap sync=true adql='select top 1 * from gaia.dr3lite' ocmd=meta

STILTS rewrites the VOTable from the GAVO TAP results, including the COOSYS refposition:
- stilts tapquery tapurl=http://dc.g-vo.org/tap sync=true adql='select top 1 * from gaia.dr3lite' ofmt='votable(version=V15)' | grep COOSYS

TOPCAT's Columns Window shows that same metadata for those same GAVO TAP results.

Implementations Validators

Changed:

<
<

votlint from STILTS v3.1-6 validates VOTable 1.4, corresponding to PR-VOTable-1.4-20190604.

>
>

The prerelease version of STILTS ( stilts.jar) validates VOTable 1.5 with the following command:

Added:

>
>

stilts votlint my_votable_file.xml

Changed:

<
< Comments from the IVOA Community during RFC/TCG review period: 2024-02-01 - 2024-03-20

>
>

The [[http://voparis-validator.obspm.fr ][VO Paris validator] validates VOTable 1.5 by following these instructions:

Added:

>
>

- Click on Load for VOTable.
- In the empty text box below "URL of the service to validate:", enter the URL of a VOTable to validate.

Comments from the IVOA Community during RFC/TCG review period: 2024-03-01 - 2024-04-20

The comments from the TCG members during the RFC/TCG review should be included in the next section.

In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your Wiki Name so that authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment.

Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document

Sample comment by WikiName
- Response (by WikiName)

Comments from TCG members during the RFC/TCG Review Period: 2024-03-01 - 2024-04-20

WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment.

IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.

TCG Chair & Vice Chair

Applications Working Group

Data Access Layer Working Group

Data Model Working Group

Grid & Web Services Working Group

Registry Working Group

Semantics Working Group

Data Curation & Preservation Interest Group

Education Interest Group

Knowledge Discovery Interest Group

Operations Interest Group

Radio Astronomy Interest Group

Solar System Interest Group

Theory Interest Group

Time Domain Interest Group

Standards and Processes Committee

TCG Vote

If you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.

Group	Yes	No	Abstain	Comments
TCG
Apps
DAL
DM
GWS
Registry
Semantics
DCP
Edu
KDIG
Ops
Radio
SSIG
Theory
TD
StdProc

View topic | History: r33 < r32 < r31 < r30 | More topic actions...