IVOA Roadmap for 2019A

This outlines the roadmap for development activities by the various IVOA working and interest groups in 2019 between the Paris and Groningan Interops.

• IVOA Roadmap for 2019A
  • Applications WG
  • Data Access Layer WG
  • Data Model WG
  • Grid and Web Services WG
  • Registry WG
  • Semantics WG
  • Data Curation & Preservation IG
  • Education IG
  • Knowledge Discovery IG
  • Operations IG
  • Solar System IG
  • Theory IG
  • Time Domain IG
  • Standard and Processes
  • Science Priorities

Applications WG

Standards

• VOTable 1.4: Complete RFC period and recommend (well) before Groningen Interop
• MOC 1.1: Complete RFC period and recommend (well) before Groningen Interop
• VOTable 1.5: Move VOTable standards development to ivoadoc in github, and consider other possible changes.
• MOC 2.0 (probably): Work towards standardizing Space-Time MOCs (twiki page TBD).

Python

• Continue to engage with Astropy community
• Support open development in PyVO
• Maintain votable parsing in Astropy core
  • Includes supporting VOTable 1.4

HiPS

• Continue to encourage HiPS providers to declare their services in the VO registry according to the HiPS Standard.
• Discuss metadata and integration with other standards.

Data Access Layer WG

• TAP-1.1 expected REC in summer
• ADQL-2.1 waiting 2nd implementation to enter RFC (fall?)
• DataLink 1.1 revision (internalWD)
• DALI1.2 revision,pending some discussion
• ObjVisSAP / ObsLocTAP 1.0 WD before Groningen, PR in 2020
  • Some “format” discussion,content to stay as is
• SLAP-2.0 & ProvTAP,dependencies on DM

Data Model WG

Provenance

• We hope to complete the process by the end of the Summer.
• The PR process should be started before the end of July

Meas/Cood/Transf

• Ongoing discussions with Mark on the schedule. The process must speed up once Provenance is OK.
• Models depending on STC are still pedning

PhotDMv1-1 VODML Adaptation

• Working with JS and ML to complete the job before Grôningen

Source DM

• We are working on an note (DM+DAL+Apps) giving some precise guidelines for using a component based model

TimeSeries

• see TDIG

Grid and Web Services WG

Authentication and Authorization

• New SSO version, Working draft by October 2019:
  • Describe approach for obtaining token credentials (SSO)
  • Describe approach for validating token credentials (SSO)
  • Define an IVOA "Realm" and how it determines the scope of services for which a token is applicable. (SSO)
• Implement OAuth in TAP
• Another Group Membership Service Working Draft with definition of User Identities (GMS 1.0)

• Encouraged groups to use Kubernetes. Data centres will be running services as containers. Natural step to run user code in containers. Standards after more experience.
• Encouraging remote executing prototypes with containers. What infrastructure and information did you need? What problems did you face?
• Describe POSIX access to a platform. New VOResource Interface Type?
• Encourage collaboration. Share knowledge, code and resources with similar institutes. Organic convergence.

Registry WG

Operations:

• Validation project: at least one telecon with RofR and registry maintainers (Notes at RegistryTelecon2019A)
• Validation project: bring remaining full registries to full validation compliance (aside from any remaining standards and RofR errors)

• Formally write and propose errata for # in identifiers, OR update RofR to newer VOResource standard to not need it.
• Contribute to TDIG work on registering event streams as needed
• Continue work on VODataService 1.2
• RegTAP11RFC

Semantics WG

Standards Track

• The UCD Maintenance standard is currently in late RFC and was pending the solution of some minor technicalities. Since these have been solved during the Paris interop, it should go to Exec for their next meeting.
• We will produce a first working draft for "Vocabularies in the VO 2.0" around August 2019; this will, much more than its predecessors, address consensus vocabularies, in particular as regards their maintenance and evolution.

See http://www.ivoa.net/rdf.

• Update vocabulary maintenance software in lockstep with Vocabularies 2.0 document; this, in particular, concerns support for vocabularies over classes, which we (probably) need for the VOTable-attached vocabularies; also, draft terms (as opposed to draft vocabularies) will need software support.
• Guide Timescale and Refpos vocabularies through the VOTable 1.4 RFC process.
• Work on metadata of the theory vocabularies.
• Perform the first “vocabulary enhancement proposals” (as per Vocabularies 2.0), presumably on Datalink terms.
• Observation facility vocabulary: test metadata and classes with the current TAP prototype, insert more lists, define or reuse a name resolver.
• UCD maintenance procedure: After completing the RFC process , put it in action for the current RFM pages.

Data Curation & Preservation IG

• DOI Survey to continue
• DOI Note draft to publish before Groningen and to discuss during the DCP session

Education IG

Knowledge Discovery IG

Operations IG

Continue normal activities:

• monitor VO services, expect to present weather reports at the next Interop
• monitor availability of validators for existing and new standards (and versions), recorded at IvoaValidatorsSummary
• provide a forum for discussion of operational issues at and between interops
  • encourage more use of Ops mailing list for topics of potential interest?
• try to provide better feedback between validation activities and WGs

Solar System IG

• Draft EPNcore / EPN-TAP version (with DAL?)
• List of reference frame / coordinate systems (with Semantics)

Theory IG

• Want to create SimDM 1.1: port to VO-DML (basically done) and fix vocabulary links.
• Discussion about maintenance of semantic vocabularies used in SimDM. Some can be shared (say astroobjects), but we should be able to create some just for theory. It will take too long to push through long acceptance process.
• How SimDAL services can be registered in the Registry?
• Any application able to use a SimDAL service?

Time Domain

• TimeSeriesDM:
  • Explore how the current status of the data model is able to describe ZTF-DR1 products (Objects Table, lightcurves, single-epoch images, quality flags) * Work with Apps on ST-MOC:
• ST-MOCs
  • Work with data providers to precompute STMOCs: VizieR catalogs and HiPS, and for solar system body ephemeris - work close to SSIG for that.
  • Ingest in CDS MocServer: clients can resource by Space-Time.
  • Create library in python and add to mocpy.
  • Do we need a standard IVOA 2.0 MOC for SMOC, TMOC and STMOC?
  • VO registry coverage by STMOC? Work with registry for that.
• Work with Semantics to improve discovery and client use of:
  • VOEvents services and streams (What and where)
  • Time Series as distributed by datalink (data product (sub)type)
  • Get the refposition case of topocenter started for TIMESYS in VOTable1.4

Standard and Processes

Science Priorities