International Virtual Observatory Alliance

Difference: VOTable15RFC (2 vs. 3)

Revision 32024-02-23 - AdrianDamian

META TOPICPARENT	name="IvoaResReg"

Changed:

<
<

RegTAP 1.2 Proposed Recommendation: Request for Comments

>
>

VOTable 1.5 Proposed Recommendation: Request for Comments

Changed:

<
< RegTAP, formally known as the IVOA Registry Relational Schema, is the standard way for clients to query the VO Registry. Version 1.2 adds

>
>

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

Deleted:

<
< tables to give the coverage in space, time, and spectrum and a tap_table view intended to replace GloTS. To make use of these features, we require a few optional ADQL features and the extra UDF ivo_interval_overlaps.

Changed:

<
< Latest version of RegTAP can be found at:

>
> Latest Draft: VOTable 1.5 (Proposed Recommendation)

Deleted:

<
<

https://ivoa.net/documents/RegTAP/20240124/
Bleeding edge versions during RFC can be built from the sources, which are kept on github. Feel free to open bugs or pull requests there at any time.

Changed:

<
< RegTAP is a fairly long standard. For review, it is probably advisable

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

Deleted:

<
< to only skim the unchanged text. For the purposes of this RFC, it is probably sufficient to closely inspect sects. 4.5, 7, 8.15 through 8.18, 9, and 10 (in particular 10.13). See also appendix E.

Changed:

<
<

Reference Interoperable Implementations

>
> VOTable 1.5 is a backward-compatible revision.

Changed:

<
< Server-side implementations exist in the TAP services at http://reg.g-vo.org/tap and https://registry.euro-vo.org/regtap/tap.

>
>

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

Added:

>
>

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.

See GitHub for a full list of changes.

To Do Upon Approval, Prior to Upload

Changed:

<
< Client-side code exploiting the new spatial tables is present in pyVO; WIRR also has constraints on coverage in space, time, and spectrum.

>
>

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

Changed:

<
< Support for tap_tables is less common; however, once the data providers fix their metadata records, the content of tap_tables essentially is equivalent to what we already have in GloTS, and hence the editor would

>
>

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

Deleted:

<
< argue that all clients using GloTS (e.g., TOPCAT) count as reference implementations of tap_tables.

Changed:

<
<

Implementations Validators

>
>

AladinProto: TIMESYS and COOSYS full support

Added:

>
>

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.

Changed:

<
< A validator is part of the source distribution at https://github.com/ivoa-std/RegTAP. See the validator subdirectory.

>
>

Implementations Validators

Deleted:

<
< Note that it requires a registry seeded with the data provided, and hence the suite can only be used by the service operators.

Changed:

<
<

>
>

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

Changed:

<
<

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

Deleted:

<
<

Deleted:

<
<

Comments from the IVOA Community during RFC/TCG review period: 2024-02-01 - 2024-03-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)

Changed:

<
<

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

>
>

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

Changed:

<
<

TCG Vote : Bambi eyes - more Bambi eyes

>
>

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

Added:

>
>

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