| |
| META TOPICPARENT |
name="IvoaTCG" |
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.
- TAP-1.1 expected REC in summer
- ADQL-2.1 waiting 2ndimplementation to enterRFC (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
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)
Science Platforms
- 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.
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)
Standards:
- 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
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.
Vocabularies Work
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.
|
