TAP-1.0 Next

This topic collects proposals for modifications of the TAP-1.0 specification in order to improve the next revision of the specification.

Errata to the TAP-1.0 recommendation can be found on the devoted TAP-1_0-Errata page.

Proposed Features

Suggestion for revision of TAP-1.0, in terms of errata content, clarifications and proposed new features, where initially collected in the TAP Implementation Notes wiki topic, later serial as an IVOA Note (its source available on volute), and then discussed at various Interoperability Meetings.

With reference to the TAP-1.1 internal WD (see [[TableAccess][TAP] topic), a session and splinter discussion took place at Sesto Interop. The outcome of that discussion can be summarized as (thanks to PatrickDowler):

• remove REQUEST
• remove VERSION
  • versioned LANG parameter needs to be examined/prototyped wrt. ADQL-2.1
• explore a mechanism (tap_schema?) to denote tables that can/cannot be queried by ADQL
  • and what LANG to use of not ADQL?
  • allows for a TAP service with ADQL to query tap_schema and other LANG for non-relational content
• datatypes: point, interval, circle, polygon, box?, coordrange?
  • move defintion of xtype and serialisation upstream -> DALI? VOTable?
• contains and intersects for interval -> ADQL-2.1
• clarify how field metadata to be generated
  • for union?
  • non-unique result table column names?
• TAPRegExt-1.1 remains separate doc
  • need to remove/relax standardID constraint

• idea from Mark Taylor:
  • ordering of tap_schema rows (int)
  • columns for sure, maybe tables? all?
• idea from Pat:
  • add arraysize to tap_schema.columns and keep "size" for compat