InterOpNov2024DM < IVOA

---+ Data Model Working Group : November 2024

[[InterOpNov2024][back to main programme page]]

---++ Schedule
| *Data Model Session 1: Saturday November 16, 2024 @ 11:00-12:30; Room Aula Magna* ||||
| *Speaker* | *Title* | *Materials* | *Time* |
| Bruno Khelifi | <b>Data Model for VHE gamma-ray data and relations with IVOA standards</b><br /> <p>The very-high-energy gamma-ray astrophysics (above few tens of GeV up to few hundreds of TeV) is showing the emergence of observatories that will provide proposal-driven observations, open data and open science analysis tools. The largest observatory of such type is the Cherenkov Telescope Array Observatory (CTAO) that is currently under construction. In this context of opening of the VHE astrophysics, the FAIRisation of the data and an efficient data dissemination using VO technologies are necessary to allow multi-wavelength and multi-messenger analyses. The presentation will present the status of the data models of the VHE data products, in regard with the current IVOA data models and model drafts</p> | [[%ATTACHURL%/BKhelifi_VHEDM_v1_compressed.pdf][pdf]] |  15'+3' |
| Ian Evans | <b>An X-ray Astrophysicist Looks at !ObsCore </b><br /> <p>Data discovery in the Virtual Observatory is supported by the !ObsCore data model, which identifies key observation metadata that can be queried to search for data products of interest to the end user. I review the current !ObsCore documents and definitions from the perspective of an X-ray astrophysicist who wants to use !ObsCore to support data discovery of the scientifically rich Chandra X-ray Observatory data archive and specifically the numerous Chandra Source Catalog data products. I discuss which !ObsCore components appear to work well for high-energy astrophysics data, what could be improved, and what appears to be missing.</p> | [[%ATTACHURL%/IEvans_Malta_Interop_2024.pdf][pdf]] |  15'+3' |
| Paul Harrison | <p> *VO-DML 1.1 candidates* </p> <p>The VO-DML tooling has been extended to include robust Java and Python code generation that enables XML and JSON serialization as well as ORM to databases for arbitrary data models (first reported on in the <a href="InterOpNov2021DM" target="_blank">Nov 2021 Interop</a>, with ongoing progress reported subsequently). This work has highlighed some areas where the VO-DML standard should be clarified, as well as some ideas for extensions to the standard. These ideas have mainly been managed as <a href="https://github.com/ivoa/vo-dml/milestones" target="_blank">GitHub issues</a> so far, and this talk is an invitation for people to contribute to the VO-DML 1.1 standardization process. The suggestions so far will be summarized as well as the progress on actually updating the standard document.</p> <p> </p> | [[%ATTACHURL%/VO-DML_Extensions2_PAH.pdf][pdf]] | 15'+3' |
| Laurent Michel | *MANGO model updates* <p>After being delayed due to the MIVOT recommendation process, the MANGO data model is now a VO working draft.<br />The purpose of MANGO, which stands for MO-del for AN-notating G-enericO-objects, is to add an upper level of description to the tabular data of query responses. It allows metadata to be extended, complex quantities to be reconstructed from multipl column values and properties to be linked together. It also allows to specify the origin of the data.<br />I'll give an overview of the model and the tools available to exercise it. <br />This talk is an invitation for people to contribute to the REC process.</p>  | |  15'+3' |
| Mark Cresitello-Dittmar | *Follow-up from Sydney Joint session* <p>As the IVOA Data Model landscape becomes fuller, we are introducing models which serve overlap in domain space with other models, but are represented at a level appropriate for their target usage. For example, CAOM for archives overlaps with content in Dataset, Characterisation, Cube, etc which are more data product oriented. MANGO introduces an !EpochPosition which consolidates elements from the Coordinates model into a compact object suitable for application workflow. This talk is an update on an effort to define a mechanism to formally map the relation between models with overlapping content. The goal is to minimize the effort needed to ensure the consistency of this content.</p> | [[%ATTACHURL%/modelOverlap_Nov2024.pdf][pdf]] |  15'+3' |

| *Applications/Data Model Session 2: Saturday November 16, 2024 @ 16:00-17:30; Room 103* ||||
| *Speaker* | *Title* | *Materials* | *Time* |
| *Applications Segment* ||| 60' |
| | see [[InterOpNov2024Apps][Apps schedule]] | | |
| *DataModel Segment* ||||
| Pat Dowler | <b>CAOM - integration status and discussion</b><br /> <p> </p> | | 30' |

<!--
      * Set ALLOWTOPICRENAME = IVOA.TWikiAdminGroup
-->

Attachments

Topic attachments
I	Attachment	History	Action	Size	Date	Who	Comment
pdf	BKhelifi_VHEDM_v1_compressed.pdf	r1	manage	1083.3 K	2024-11-15 - 14:19	BrunoKhelifi
pdf	IEvans_Malta_Interop_2024.pdf	r1	manage	520.7 K	2024-11-15 - 20:36	MarkCresitelloDittmar	Look at ObsCore
pdf	VO-DML_Extensions2_PAH.pdf	r1	manage	6374.3 K	2024-11-15 - 15:45	PaulHarrison	VODML 1.1 WD Presentation
pdf	modelOverlap_Nov2024.pdf	r1	manage	2496.2 K	2024-11-15 - 20:36	MarkCresitelloDittmar	Domain overlap in models

This topic: IVOA > WebHome > IvoaEvents > InterOpNov2024 > InterOpNov2024DM
Topic revision: r13 - 2024-11-15 - MarkCresitelloDittmar