VOTable 1.4 Proposed Recommendation: Request for Comments
Summary
Latest Draft: VOTable 1.4 (Working Draft)
The substantive differences between version 1.4 of VOTable and the preceding version 1.3 are:
• Applying erratum VOTable 1.3-1, un-deprecating COOSYS.
• Applying erratum VOTable 1.3-2, permitting F0 in precision.
• Applying erratum VOTable 1.3-3, clarifying the meaning of arraysize="1".
• Add a new TIMESYS element as a simple means for supplying metadata for time values in the VOTable.
Reference Interoperable Implementations
- AladinProto: TIMESYS and COOSYS full support
- 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 (WD-VOTable-1.4-20190403): 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". These applications don't do much with the information beyond making it visible, though (experimental) time plots use the
timeorigin
to offset temporal coordinates.
Implementations Validators
- votlint from STILTS v3.1-6 validates VOTable 1.4, corresponding to WD-VOTable-1.4-20190403, with the correction that the TIMESYS
timeframe
and refposition
attributes have RDF vocabularies at URIs http://www.ivoa.net/rdf/...
and not http://ivoa.net/rdf/...
Comments Prior to Official RFC Period
Comment here prior to the official RFC period. Include your Wiki Name. Discussion can be continued on the mailing list (
apps@ivoa.net).
Ignore Below Until RFC Period Starts
Comments from the IVOA Community during RFC/TCG review period: RFC_start_date_TBD - RFC_end_date_TBD
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
Comments from TCG member during the RFC/TCG Review Period: TCG_start_date_TBD - TCG_end_date_TBD
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
TCG Vote : Vote_start_date - Vote_end_date
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 |
|
|
|
|
KDIG |
|
|
|
|
SSIG |
|
|
|
|
Theory |
|
|
|
|
TD |
|
|
|
|
Ops |
|
|
|
|
StdProc |
|
|
|
|