IVOA Roadmap for 2016B

This outlines the roadmap for development activities by the various IVOA working and interest groups in 2016/17 between the Trieste and Shanghai Interops.

---

---

Applications

• HiPS standards => from WD to PR
• VOTable 1.3 Errata (COOSYS)
• Awaiting VODML mapping in VOTable proposal (from DM WG)

Data Access Layer

• TAP-1.1
  • new WD according to Trieste decisions preapared for PR(will come after Shanghaï)

• ADQL-2.1
  • BNF and PEG grammar discussion
  • UDF and coordinate system changes
  • New 2.1 WD version in preparation for RFC

• SimDAL-1.0
  • REC since march 20th

• VTP-1.0
  • REC since march 20th

• SODA-1.0
  • Last modification from RFC. PR pushed to the Exec in Shaghaï

• DALI-1.1
  • Last modifications during RFC . PR pushed to the Exec in Shanghaï

Data Model

ObsCore-1.1

• in RFC, should be REC by Shanghai

VO-DML

• standard
  • is in RFC, expect some iteration.
  • goal is to be in TCG review by Shanghai
• mapping
  • evaluating new annotation syntax,
  • goal is to have a new WD, perhaps in PR by Shanghai

STC-2

• restructure and minimize content to NDCube use-case requirements
• goal is to have a generally accepted working draft, implemented in NDCube/Dataset models and ready for RFC by Shanghai

NDCube/DatasetMetadata

• keep updated to STC amd VO-DML developments
• implement examples in VOTable
• work as use-case for VO-DML mapping implementation
• goal is to have fully vetted/validated examples by Shanghai, with the documents ready for RFC pending completion/readiness of dependent models.

Provenance:

• goals
  • publish Working Draft on IVOA Documents webpage
  • VO-DML compliant representation of the model
  • work out relations between SimDM and ProvenanceDM
  • new section with expanded implementation notes for use cases (with used classes and attributes)

Source:

• regroup to get project working toward a working draft.

Grid and Web Sevices

During the interop in Trieste, the Grid and Web Services working group came to an agreement to support a standard means of authorization through group membership. Such a standard will enable interoperable authorization among IVOA services. It is to be determined whether a note documenting the endorsement and use of an external stardard, or an IVOA standard itself is the best way to incorporate group authorization into the IVOA. A draft of such a proposal will be presented in Shanghai.

A new VOSpace 2.1 Working Draft to be ready before Shanghai. As per the discussions in the first GWS Trieste session, it will include mention of the Public Share Protocol. This protocol may be use to obtain long-lived URLs for publishing papers and DOIs.

"Code to data" was a topic of much discussion in Trieste. The GWS working group would like to pair with the DAL working group to work on a simple IVOA approach on processing data using client submitted code.

Grid and Web Services Standards statuses:

• The SSO 2.0 final Proposed Recommendation will go to Exec by the end of 2016.
• The VOSI 1.1 final Proposed Recommendation will go to Exec by the end of 2016.

Registry

VOResource 1.1: There are still several open questions (e.g., representation of alternate identifier schemes) that we want to discuss on the mailing list before issuing a PR, together with a preliminary mapping into a RegTAP service (which would start as a proprietary extension before putting this extension on the standards trail). We will try to encourage more data providers to add DOIs or ORCIDs to their registry records. RFC could then start after Shanghai.

Registry Interfaces 1.1 is essentially pending a clarification for having standalone registry records for RegTAP-based searchable registries. We expect to work this point out very soon. It will, however, depend on the Discovering Data Collections Note. We will, therefore, probably synchronise PR of RI 1.1 with the endorsement process of this Note. That, in turn, we want to start in November 2016.

Standards records: We will continue to work with the chairs of the other IVOA working groups to ensure that they register their standards as envisioned by StandardsRegExt (cf. WriteAStandardsRecord).

TAPRegExt 1.1 will be kept in lockstep with TAP 1.1; since the latter is expected to go PR this year, so will TAPRegExt 1.1.

SimpleDALRegExt 1.1 has been fully reviewed in Trieste and should be approved by the Exec later this year.

Semantics

Data Curation & Preservation

The Data Curation & Preservation IG will continue to follow relevant topics, in particular the status and activities of the Research Data Alliance and the implementation of DOIs.

Education

Knowledge Discovery in Databases

Operations

The Operations Group continues to work to ensure effective operations of VO services. Two developments in the underlying network infrastructure may need to be addressed operationally. Some sites in the United States have been required to transfer to using secure HTTP (i.e., HTTPS) and this can invalidate existing entries. Since the use of HTTPS is expected to spread concerns and experiences will be addressed in Shanghai and future interops. The use of IP/V6 internet addresses is also becoming more widespread but there has been little investigation of the consquences of this new protocol.

The results from validations and monitoring of VO service will continue to be published at web sites and discussed at interoperability meetings and the group will continue to work to circulate operational best practices and lessons learned from large and small VO providers.

Theory

Time Domain

Standard and Processes

The aim is to finalize Document Standards V2.0 at the Shanghai Interoperability meeting at the latest. The RFC, including the request for comments from the TCG, was initially open 24 September 2016 - 5 November 2016.

Science Priorities

Current list of Science Priorities being followed up are:

• Time Series, time-domain astronomy
• Multi-dimensional data
• Multi-messenger astronomy

Within the context of the Science Priorities, the IVOA also seeks communication with large and small astronomical projects to identify and cross-fertilize their development plans with the IVOA development plans for protocols, services and applications.

<!--
* Set ALLOWTOPICRENAME = TWikiAdminGroup
-->