Table Access Protocol 1.1 Proposed Recommendation: Request for Comments

The table access protocol (TAP) defines a service protocol for accessing general table data, including astronomical catalogs as well as general database tables. Access is provided for both database and table metadata as well as for actual table data.

This is the proposed revision (version 1.1) of the standard, including changes from community feedback, clarifications and a few optional features.

Latest version of IVOASTANDARD can be found at:

• PR-TAP-1.1-20180416

Reference Interoperable Implementations

(Indicate here the links to at least two Reference Interoperable Implementations)

The primary CADC TAP service (http://www.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/tap/) is a complete TAP-1.1 implementation. We have implemented TAP-1.1 changes over the whole time that the new version was developed, but I would like to draw attention to these in particular:

• the VOSI-capabilities endpoint makes use of the prototype UWSRegext interface types to denite sync and async endpoints with a variety of security methods
• the tap_schema uses the new datatype,arraysize,xtype column description and this is directly seen in the VOSI-tables output use of VOTableType everywhere
• we do use ObsCore compatible TAP-1.0 style description of the s_region column (char,*,adql:REGION in tap_schema.columns) so the ObsCore output in VOTable complies with the type and STC-S serialisation in ObsCore-1.1
• we use the DALI-1.1 datatypes otherwise (point, interval, and polygon in use)

In Release 1.1, I believe DaCHS (http://soft.g-vo.org/DaCHS) implements all aspects of TAP 1.1 (though of course I also expect that a validator will uncover a couple of issues, which we'll fix as fast as possible). An endpoint to try things out is http://dc.g-vo.org/tap, which also has interoperated nicely with TAP 1.0 clients so far.

Pat's notes on tap_schema datatypes, adql:Region, and DALI 1.1 geometries apply here, as well. -- MarkusDemleitner - 2018-04-23

Implementations Validators

(If any, indicate here the links to Implementations Validators)

Comments from the IVOA Community during RFC/TCG review period: 2018-04-23 - 2018-06-04

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 member during the RFC/TCG Review Period: 2018-04-23 - 2018-06-04

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

Some minimal comments from my read through.. Laurent may have some more technical comments as well.

Section 1.2.6: 'simple key-vale' -> 'simple key-value'

Section 2.4: 'the mandatory chilsd' -> 'the mandatory child'

Section 2.7: 'Thus, for the asynchronous TAP queries, the parameter requirements must be satisfied (and errors returned if not) only when the query is run in (in the sense of UWS job execution).' Something seems missing.. the query mode maybe?

Section 2.7: ' may be created with with no parameters' == Extra 'with'

Section 5.1.3: 'URL should lead to a an error' == Extra 'a'

Grid & Web Services Working Group

Registry Working Group

Semantics Working Group

Data Curation & Preservation Interest Group

Education Interest Group

Knowledge Discovery in Databases Interest Group

Solar System Interest Group

Theory Interest Group

Time Domain Interest Group

Operations

I have some comments on PR-TAP-1.1-20180416, but following discussions in Victoria, I understand some parts of the document (sec 2.4 on capabilities) will be rearranged into an external Note, with an extension to the RFC deadline. I will await this rearrangement before I post comments. -- MarkTaylor - 2018-06-04

Standards and Processes Committee

TCG Vote : 2018-05-21 - 2018-06-04

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.