---+ Data Model Working Group Sessions: May 2024, Sydney, Australia [[InterOpMay2024][Back to main program]] *DM Session 1: High Energy focus* | *DM 1 - Tuesday, May 21, 14:00 -- 15:30, C122* |||| | *Speaker* | *Time* | *Title* | *Materials* | | Mathieu Servillat | | Overview based on the Note prepared by the HE group | | | TBD | | Experience building !ObsCore service for HE data <br /><br /> (abstract) | | | Ian Evans | | Chandra Data/Catalog <br /><br /> (abstract) | | | Mark Cresitello-Dittmar | | Data models: compatibility with High Energy data <br /><br />A brief review of the data models supporting high energy data (eg: event lists), and possible paths for enabling use cases with more complex data products and workflows | | | | | Open Discussion | | *DM Session 2: General Session* | *DM 2 - Thursday, May 23, 16:00 -- 17:30, C122* |||| | *Speaker* | *Time* | *Title* | *Materials* | | Paul Harrison | 15' + 3' | !VODML enhancement requests and Proposal Model state <br /><br /> (abstract) | | | Laurent Michel | 15' + 3' | MANGO, a Model for Annotating Generic Objects <br /><br />Mango is a !DataModel proposal designed to represent open-ended collections of complex properties such as we find in data tables.<br />We consider a property to be complex if it is built with multiple parameters, possibly associated with complex errors, flags or even other properties.<br />The purpose of Mango is to facilitate the processing of data tables property by property rather than column by column, which requires clients to infer the property components.<br />The properties supported by Mango can be modeled by classes imported from other data models (Meas/Coords, photDM ) or by built-in classes. | | | François Bonnarel | 15' + 3' | !FoV data model : integrating a rendering class<br /><br /> (abstract) | | | Mathieu Servillat | 15' + 3' | One-step Provenance updates <br /><br /> (abstract) | | *Joint Session:* | *DM/DAL/APPS - Wednesday, May 22, 11:00--12:30, C122* |||| | *Speaker* | *Time* | *Title* | *Materials* | | Mark Cresitello-Dittmar | 15' | Introduction <br /><br /> This will primarily be a discussion session to consider options for how Data Models are to be delivered and consumed by clients (DAL, APPS) with vastly different requirements. <br /> The IVOA Data Models to date have been focused primarily on Data Discovery and Access via interactions with database tables. The results of these are served by simple VOTables and/or !DataLink to native format files. More recent Data Model work ( Provenance, Cube family, Mango ) have been directed to more complex use cases and are consequently, more detailed than is desired to serve simple use cases directly. In addition, we have the prospect of integrating the Common Archive Observation Model (CAOM) into our Data Model suite, which has significant concept overlap with existing models, but serves its target clients very well. <br /><br /> How do we develop/present models rich enough to serve the most complex cases AND serve clients who don't require that level of flexibility WITHOUT creating a maze of data models with overlapping content? Bring your ideas! | | | Laurent Michel | 10' | Epic Propagation project: case in point<br /><br /> (abstract) | | | | | Open Discussion | | <!-- * Set ALLOWTOPICRENAME = IVOA.TWikiAdminGroup -->
This topic: IVOA
>
WebHome
>
IvoaEvents
>
InterOpMay2024
>
InterOpMay2024DM
Topic revision: r4 - 2024-05-03 - MarkCresitelloDittmar
Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback