DM Sessions Schedule - IVOA Apr 2022 Interoperability Meeting

[back to main programme page]

** DRAFT in good progress *

Notes and session video recording are linked below each session schedule table.

DM 1: Data Models

Time: Apr 27 15:00 [session #10]

Moderator: Laurent, Notetaker: Jesus

notes: etherpad notes (link to live notes, should expire around end of April 2023)

DM 2 : VOTable Annotation

Time: Apr 28 05:00 [session #14]

Moderator: Laurent, Notetaker: Jesus

notes: etherpad notes (link to live notes, should expire around end of April 2023)

Abstracts

DM Tooling (Paul Harrison)

Recent updates to the tools for data model authors will be discussed. The tools are now driven by gradle and can be found in https://github.com/ivoa/vo-dml

Last Step Provenance (Mathieu Servillat)

abstract

Observation Proposal DM (Paul Harrison)

A data model for creating and managing observing proposals is being created in https://github.com/ivoa/ProposalDM. The current status and future plans will be presented. It should be noted that there will be a hack-a-thon session for those wishing to learn more and be able to contribute to the model.

Field of View DM (François Bonnarel)

The field of views descriptors used by Alain are currently coded in VOTable in a way that is not standardized by the OV but are understood only by Aladin.
The Model Instance in VOtable (MIVOT) standard is being recommended to encode in VOTable annotations to associate data models with tabular data.
The presented work proposes to replace the current field of view encoding in Aladin with an encoding based on MIVOT and on a field of view data model reusing some VO model components.

Annotation Syntax (Laurent Michel)

VO mode annotation syntax proposes a syntax to map VOTable data on any model serialized in VO-DML. MIVOT annotations are grouped in a single XML block located in the resource head. The annotations operate as a bridge between the data and the model. It can denote the way data are connected to each other as well as different tables can be joined together. It is also able to carry data or meta-data that are missing in the VOTable. The annotation block is made of bricks that facilitate both annotation process and model instance reconstruction. it has been designed so as not to alter the original VOTable content, thus limiting its impact on legacy clients.

Annotating TAP Response on the Fly (Mireille Louys)

Currently the TAP protocol presents table data and metadata via a {TAP\_SCHEMA} describing the served tables with their columns and possible joins between them.

We explore here how to add an information layer, so that values within table columns can be used to instanciate objects defined in a selected IVOA data model like Photometry, Coords, Measure or the proposed MANGO container model. This information layer is provided through annotation tags which tell how the columns' values can be interpreted as attributes of instances of that model.

Then when a TAP query is processed, our server add-on interprets the ADQL query string and produces on-the-fly, when possible, the TAP response as an annotated VOTable document. The FIELD elements in the table response are mapped to corresponding model elements templated for this service. This has been prototyped in Java, using the VOLLT package library and a template annotation document representing elements from the MANGO data model. Examples on Vizier and Chandra catalogs will be shown.

Annotation: Implementation Status, Issues and Prospects (Laurent Michel)

The Model Instance in VOtable standard needs reference implementations to be validated. These reference implementations are based on annotated VOtables; they must also demonstrate that code reading VOtable data through a model view is both feasible and useful. We will present a Python based demonstrator exploring different ways to design model-based APIs. This talk is connected with the first hack-a-thon topic

[back to main programme page]

-- LaurentMichel - 2022-04-21