2018ARoadmap < IVOA

---+ IVOA Roadmap for 2018A

This outlines the roadmap for development activities by the various IVOA working and interest groups in 2018 between the Victoria and College Park Interops.

---

<br />%TOC%
---

---++ [[IvoaApplications][Applications WG]]

Python

   * Engage with Astropy community
   * Possible Astroquery VO module
VOTable Standards

   * Work towards [[IVOA.VODML-Mapping][VODML-Mapping]] consesnsus.
   * Determine if there are other driving factors for a new VOTable version.
HiPS

   * Continue to encourage HiPS providers to declare their services in the VO registry according to the <a target="_blank" href="http://ivoa.net/documents/HiPS/index.html" title="HiPS Standard">HiPS Standard</a> (section 5.3).

---++ [[IvoaDAL][Data Access Layer WG]]

+ TAP 1.1 : + Little extension of RFC (new PR). Will finish soon.

+ ADQL 2.1 : + Some revision and 1 implementation before going to RFC.

+ SLAP 2.0 : + Implementation to be published. More comments needed.

+ SCS 1.1 : + New draft and back-compatibility check for fall Interop.

+ DALI-next : + Discussion page settled. Please contribute!!!

+ OLAP (observatory locator access protocol) : + note promoted to WD

+ OVAP (object visibility access protocol) : + Note promoted to WD

+ ProvTAP and ProvSAP (ex ProvDAL°) : + internal draft promoted to WD. Implementation of ProvTAP durring summer

+ DataLink : + Discussion page. Implementation note. DataLink1.1 spec to be started

+ SIAV2.1 + Mak a start

+ SODA + more implementation needed

+ TimeSeries discovery and access protocol + make a start

---++ [[IvoaDataModel][Data Model WG]]

Fairly packed roadmap as we try to close up current projects and start up the next phase.

Current model efforts:
   * VO-DML 
      * REC approved in Victoria 
         * upload final REC version of documents _( July 2018 )_
         * upload new registry records for document and IVOA data model _( July 2018 )_
   * "STC" component models (coords, meas, trans) 
      * document current versions of models; most content to be extracted from last model drop by Arnold _( July 2018 )_
      * fold in 'missing' elements identified in Victoria 
         * coords - SpaceReferenceFrame to enumeration to vocabulary to better support SSIG domain _( Aug 2018 )_
         * trans - restore transform operations needed by LSST, implemented by AST library _( Aug 2018 )_
         * coords/meas - restore basic Velocity _( Aug 2018 )_; discuss/add 'ProperMotion', 'RadialVelocity', 'UpperLimit' _( Aug+ 2018 )_
      * with concensus on model content, move to PR/RFC process _( Sep 2018 )_
   * Dataset Metadata 
      * no contention, ready to move forward when measurement model dependency is satisfied. _( Sep 2018 )_
   * NDCube 
      * no open issues, ready to move forward when dependencies are satisfied... most likely AFTER "STC" and Dataset are completed _( Oct+ 2018 )_
   * Provenance 
      * resolve open questions; get concensus on content; migrate to RFC process _( Oct 2018 )_
Upcoming model efforts:

Most of these projects are being driven by the time domain work and feedback from the 'Hack-a-thon" in Victoria with data providers exercising existing models. There are no hard goals for these projects at this point, but will be worked as a 'best effort' level
   * TimeSeries 
      * continue working with TDIG to flesh out requirements for time domain data models and prototype/develop models as time and resources permit
   * PhotDM 
      * Generate VO-DML compliant model; it is not yet clear if this is a major version update or minor.. the original model had gone far in this direction. 
         * preliminary work has been done in Volute in preparation for Victoria demos
         * pick up from there with 'official' model project; modeler=Jesus, domain=??, tech=??
   * Characterisation 
      * Migrate Characterisation to a VO-DML compliant model; this is a major project, at least in part motivated by time domain project needs
      * modeler=Francois/Mireille?, domain=??, tech=??
   * SourceDM 
      * It is still unclear if a full SourceDM is required or useful at this point given the resources available.
      * A better approach might be to concentrate on the Entities which might be most useful TO a SourceDM, and work to get those entities included in the proper model (eg: meas ).

---++ [[IvoaGridAndWebServices][Grid and Web Services WG]]

   * Authentication and Authorization 
      * Work with Applications WG on client authentication support
      * Completion of the Group Membership Service (GMS) working draft
      * Prototypes and implementations of GMS
   * TAP 1.1 VOSI capabilities support 
      * Publication of the UWSRegExt 1.0 Note and XSD?
   * Schema versioning: work out issues with versioning attribute context
   * Encourage working group to collaborate on Science Platform development
   * Continue with GWS telecons

---++ [[IvoaResReg][Registry WG]]

RegTAP 1.1, includig new VOResource 1.1 features, can now go through RFC; prototype implementations exist at GAVO and partially at ESAVO, and are planned at MAST (USVAO). The main change is in describing services requiring authentication, which will eventually require changes in some client queries to RegTAP services if these become more common. <br /> <br /> STC in the Registry: Work in prototypes will continue based on a recent STC in the Registry note introducing the concept of MOCs in the registry.<br /> <br /> Discovering Dependent Resources: A note in progress addresses the problem of discovering data collections that are published through other services, the prime use case so far being TAP tables. A path forward involving creating a new registry extension allowing both tables and capabilities was discussed in Victoria, this work will be continued and prototypes developed.<br /> <br /> 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). <br /> <br /> Maintenance: We will keep making sure the registry system runs; in particular, we will address anomalies diagnosed by ESAVO especially including inconsistencies in the Registry of Registries.
---++ [[IvoaSemantics][Semantics WG]]

*Maintenance of UCDs :*

Improve the revision loop proposed. Adjust the Maintenance for UCD WD with the lessons learned. _By end June 2018_

<span style="background-color: transparent;">Work out the process for sharing the progress on UCD terms revision with the community. </span> _By end July 2018_ <span style="background-color: transparent;"> </span>

<span style="background-color: transparent;"> </span><span style="background-color: transparent;">Complete the revision of terms asked by the planetary science on the </span>RFMforUCD<span style="background-color: transparent;"> web page. </span><span style="background-color: transparent;">Propose face to face meetings to speed up the process. _By nov 2018_ </span>

*Visibility of IVOA vocabularies*

Setup of a vocabulary page at the top the http://ivoa.net/documents front page as collaboration effort with the media group and <span style="color: #0000ff;"><span style="text-decoration: underline;">IVOA </span></span>document coordinator. <span style="background-color: transparent;">A prototype page gives an idea of this prototyped page </span><span style="background-color: transparent;">[[VocabularyTestPage][http://wiki.ivoa.net/twiki/bin/view/IVOA/VocabularyTestPage]]</span>

<span style="background-color: transparent;"> </span><span style="background-color: transparent;">Organisation of the Vocabulary repository </span><span style="background-color: transparent;"> _By nov 2018_ </span>

*Nomenclature for names for Observatories, instruments, missions.*

Collaboration Baptiste Cecconi (Lesia, Paris) - University of Graz - <span style="background-color: transparent;">Fuzzy logic tools applied to instruments telescopes list cross match . Description of Space missions from Vespa</span>

<span style="background-color: transparent;">General thesaurus building to be continued with ADS, AAS, astronomical journals, librarians and documentalists involved.</span>

<span style="background-color: transparent;">Design of a metadata description based on the reuse of the PDS 4 Information model to categorize the various items. </span> _By nov 2018_
---++ [[IvoaDCP][Data Curation & Preservation IG]]

The Data Curation & Preservation IG will continue to be the place where liaison between the IVOA and the Research Data Alliance RDA is established, with regular discussion of RDA activities, their relevance to the IVOA, and the IVOA activities relevant to the RDA (e.g. Provenance). This is a standing item for the IG session at each IVOA Interoperability meeting. The IG also hosts discussions on other topics of interest for Data Curation & Preservation. DOIs have been one of the important topics addressed in the past. It is proposed to have it as a topic again for the next <nop>DataCP meeting in November 2018, to discuss requirements, implementation, lessons learnt, granularity, etc.

---++ [[IvoaEducation][Education IG]]
   * EduIG and Media Session at the Victoria Interop
   * Tutorial at the 2018 ADASS on "A comprehensive use case scenario of VO standards and protocols"
---++ [[IvoaKD][Knowledge Discovery IG]]

---++ [[IvoaOps][Operations IG]]

---++ [[IvoaSS][Solar System IG]]

---++ [[IvoaTheory][Theory IG]]

Work in the "Implemementation Note" for SimDAL.

We intend to describe several implementations, done by different groups, about different types of simulations.
---++ [[IvoaTD][Time Domain IG]]

<strong><span style="background-color: transparent;">Alerts</span><br /></strong>

<span style="background-color: transparent;">Time domain IG members working with ZTF and LSST to develop brokers and filters: Lessons learned from ZTF and LSST will inform future developments of VOEvent</span>

Feedback from SSIG, investigate and report on how to proceed on VOEvent to meet their requirements

<span style="background-color: transparent;"> *Time Series:* </span>

<strong><span style="background-color: transparent;"> </span><span style="background-color: transparent;">DAL:</span></strong>

TimeSeries extension for DAL protocols as a single spec: &ldquo;TimeSeries discovery and access protocol a set of extensions to DAL protocol for TimeSeries&rdquo;

Obscore extension (Time sampling&hellip;)

Corresponding PARAMETERS in SIAV2-like interface

SODA extension parameters for data selection

Access or DataLinks tags in source-driven context

<span style="background-color: transparent;"><strong>DM: </strong>Representation (requires modelling and serialisation)</span>

Work close to Gaia, ZTF, LSST to meet their deadlines

Deliver different versions on our path towards ultimate goal

Present serialisations &mdash;&gt; encourage applications to test &mdash;&gt; collect feedback

Steps towards a TimeSeries DM:

   * PhotDM --&gt; DMLize
   * STC --&gt; check which parts are a must
   * Characterisation --&gt; DMLize
   * Following Time Series <span style="background-color: transparent;">[[%PUBURL%/IVOA/IvoaVOEvent/Strasbourg-TimeSeriesData-Meeting-MinimalRequirements.pdf][minimal requirements]]</span>
<span style="background-color: transparent;"> *T-Moc:* </span>

Connect to space MOC (towards a ST-MOC?)

Progenitors (HiPS for Time?)

No documentation, we need it

Test and give feedback

---++ [[IvoaStdsDocsProc][Standard and Processes]]

---++ [[IvoaSciencePriorities][Science Priorities]]

<!--
      * Set ALLOWTOPICRENAME = IVOA.TWikiAdminGroup
<del>-->--&gt;
This topic: IVOA > WebHome > WebPreferences > 2018ARoadmap
Topic revision: r18 - 2018-07-05 - AdaNebot