Model Annotation in VOTables (MIVOT) | ||||||||
Changed: | ||||||||
< < | 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. | |||||||
> > | VO model 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. | |||||||
History | ||||||||
Changed: | ||||||||
< < | The first propasal for a solution for mapping data on models was based on GROUPS and UTypes. This approach suffered some flaws that could have been fixed, but to be consistant with VO-DML (REC in 2016), the IVOA decided to promote a mapping syntax closer to the VO-DML model serialization. The baseline of this approach consists in inserting into the VOTable to be anotated, an XML block that is is faith to the model structure and that acts as a bridge between the model leaves and the actual data. | |||||||
> > | The first proposal for a solution for mapping data on models was based on GROUPS and UTypes. This approach suffered some flaws that could have been fixed, but to be consistent with VO-DML (REC in 2016), the IVOA decided to promote a mapping syntax closer to the VO-DML model serialization. The baseline of this approach consists in inserting into the VOTable to be annotated, an XML block that is faithful to the model structure and that acts as a bridge between the model leaves and the actual data. | |||||||
Standard and ToolsThe draft is managed following the GitHub workflow. The proposal is hosted in https://github.com/ivoa-std/ModelInstanceInVot
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Annotations and Astropy | ||||||||
Changed: | ||||||||
< < | The TCG mandate related to the mapping syntax also included the commitment of providing tools that could help both data provider and client developpers to assess the impact of working with annotated data.
| |||||||
> > | The TCG mandate related to the mapping syntax also included the commitment of providing tools that could help both data provider and client developers to assess the impact of working with annotated data.
| |||||||
<--
|