Abstracts
| Speaker |
Abstract |
| Laurent Michel |
MIVOT: development status and progress In this presentation we will remind the MIVOT syntax, from the simplest pattern to quite complex cases.
After that we will give an overview on the models that can be used with MIVOT yet. We will conclude with
an overview on the implementation on both server and client side. This talk will be based on the ADASS
poster P112. |
| Laurent Michel |
MANGO: Redesign after the workshop and the MIVOT recommandation MANGO is a model for describing catalog data. The draft has been presented in 2019 (Groningen) and after it has been put on hold during the DM workshop and until MIVOT be a recommandation. The work on it has been resumed since with major changes that will be presented at the session. MANGO is still open for supporting new data patterns. |
| François Bonnarel (on behalf of the RadioIG) |
Last news from the ObsCore Extension for radio data Working draft The WD has recently integrated better description of Single dish data, dataproduct_types, instrument types, and sky scan modes. An appendix with a set of use cases ADQL queries has been added. First test implementations are developed. Towards PR ? |
| François Bonnarel / Mathieu Servillat |
Discussion around an ObsCore Extension for high energy event-list data Data in the High Energy domain has some specificities, in particular the base dataset is often an Event List,
that contains information on each detection (e.g. a probable photon with its time of arrival, coordinates and energy).
ObsCore description can be adapted to such data, but may require some adjustments or an extension. This topic
has been discussed in the context of the ESCAPE European project, then during 2 ASOV workshops and now at the
IVOA level during High Energy splinter meetings. |
| Mark CD |
Cube/Dataset models in the high energy context |
| Trey Roby |
IPAC - grouping Spectra in VOTable At IPAC and using Firefly we are looking for ways to handle a group of spectra in one VO file. We use the spectrum data model which defines one spectrum but we need to also handle many spectra. We are working on a VO table format the will define one or two spectrum per line. Then we can extract spectra into the spectrum data model for display. This is a work in progress so we are seeking feedback as well. |
* Set ALLOWTOPICRENAME = TWikiAdminGroup | 
