IVOA Roadmap for 2015A

This outlines the roadmap for development activities by the various IVOA working and interest groups in 2015 between the Sesto and Sydney Interops.


VOTable 1.4

→ awaiting VODML serialization decision before starting a new cycle
→ call to read and comment the VODML mapping document

→ Support for https → try and see if a few standard adjustements will be required

→ Study a new capability entry in the registry ?

Data Access Layer


  • Hopefully Recommendation before Sydney Interop rewritten
  • WD rework during summer
  • RFC by Sydney Interop
  • WD before Sydney Interop
  • RFC around end of 2015
  • minor impact on TAPRegExt
  • WD before Sydney Interop
  • RFC around end of 2015
  • links to UWS-1.1, ADQL-2.1
  • impacts VOSI, TAPRegExt, DALI
  • see Theory IG roadmap
  • WD soon. RFC before end 2015
VOEvent Transfer Protocol
  • see TD IG roadmap
  • WD soon

Data Model

SpectralDM 2.0

Document stable, waiting for one pending implementation already provided

Somes comments received fue to this implemenation. Discussions to be taken to either update the spec covering some of the

suggestions or close SpectralDM 2.0 (and wait for recommendation) and include proposals into a possible SpectralDM 2.1 (draft for Sydney)

ObsCore 1.1

Stable draft provided in Sesto


Document stable with enough implementations

PR to be released after Sesto if agreement is obtained during Sesto (presentation of the status to be done during this interop)

VO/DML mapping

Working in a public draft in coordination with Apps. Not clear schedule (maybe PR for Sydney)


Initial discussions. First WD to be presented in Sydney

CubeDM 1.0, DataSetDM 1.0

Parallel activities. Documents stable. Waiting to have implementations in coordination with SIAv2 DAL spec

If no major problems are found before Sydney, maybe we could have a PR version in Sydney for both specs

It makes use of a more or less stable version of STC 2.0 model

STC 2.0

Preliminary stable UML provided. Spec still in a preliminary editorial phase.

WD to be presented during interop in spring 2016

Grid and Web Sevices

  • VOSpace 2.1: RFC before Sydney
  • UWS 1.1: RFC in July 2015
  • SSO 2.0: RFC before Sydney
  • New VOSI version:
    • If there are no other additions besides the scalable tables rework, a VOSI 1.1 WD will be ready for Sydney
    • If there are other additions, a VOSI 2.0 WD will commence but will not be ready for Sydney most likely
  • IVOA Strong note on XML Schema versioning ready before Sydney
  • Draft document on authorization before Sydney
  • If time/resources allow: Note on "How to implement a VOSpace"


  • Registering TAP tables (and other dataset-within-service-like things): We will prepare a note on the general principle ("add an -aux to the capability standard id and use a plain vr:Capability record") and work with DAL to have that included for TAP 1.1. Prototyping with VizieR should commence soon, prototype at the GAVO DC already exists.
  • Registry searchable by spatial constraints: Development of a MOC-capable postgres extension will start.
  • Registry Interfaces: Version 1.1 (on harvesting and being a well-behaved registry, with the old client interfaces removed) of the REC should be RFC-ready by Sydney
  • Identifiers: Version 2 will go into RFC real soon now.
  • Mapper between ivoid and DOI -- we'll explore, presumably via Datacite.
  • Continued maintenance of Registry contents
  • RofR is going to move from Urbana to Cambridge, MA.


Data Curation & Preservation


Knowledge Discovery in Databases



Simulation Data Access Layer

SimDAL document as been approved by DAL as a DAL W.D.

Actions up to the end of the year are :

1 - Take into account suggestions in the SimDAL WD and publish it on the dedicated IVOA webpage under DAL

2 - Implementation of (at least) two reference implementations

3 - development of a client / validator

Time Domain

VOEvent Transport Protocol

There's agreement within the IG that this is broadly ready to move forward from Working Draft. Will need to be "sponsored" by a WG (likely DAL).

VOEvent Registry Extension

Revision required following comments. Pending manpower; hopefully addressed this year.


Currently on hold pending manpower and refined understanding of requirements.

Time series representation

Enrique Solano has demonstrated that neither of the two approaches currently suggested for representing time series in the VO -- SimpleTimeSeries and Spectral Data Model v2 -- address all potential use cases. Working towards a comprehensive solution is a priority. Pending manpower to make progress.

Community engagement

Time domain has been identified as a priority by the IVOA CSP. Community engagement is key to this, and will require support from the larger IVOA machinery.

Standard and Processes

Science Priorities

Edit | Attach | Watch | Print version | History: r10 < r9 < r8 < r7 < r6 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r10 - 2018-06-20 - GiuliaIafrate
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback