Data Model Session 1: Saturday November 16, 2024 @ 11:00-12:30; Room Aula Magna | |||
---|---|---|---|
Speaker | Title | Materials | Time |
Bruno Khelifi | Data Model for VHE gamma-ray data and relations with IVOA standards
|
15'+3' | |
Ian Evans | An X-ray Astrophysicist Looks at ObsCore 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. |
15'+3' | |
Paul Harrison | VO-DML 1.1 candidates 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 Nov 2021 Interop, 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 GitHub issues 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.
|
15'+3' | |
Laurent Michel | MANGO model updates After being delayed due to the MIVOT recommendation process, the MANGO data model is now a VO working draft. |
15'+3' | |
Mark Cresitello-Dittmar | Follow-up from Sydney Joint session 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. |
15'+3' |
Applications/Data Model Session 2: Saturday November 16, 2024 @ 16:00-17:30; Room 103 | |||
---|---|---|---|
Speaker | Title | Materials | Time |
Applications Segment | 45' | ||
see Apps schedule | |||
DataModel Segment | |||
Pat Dowler | CAOM - integration status and discussion
|
30' - 45'? |