Model Annotation in VOTables (MIVOT)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.HistoryThe 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
Annotations and AstropyThe 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.
Reference Interoperable Implementations | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Implementations Validators
Comments from the IVOA Community during RFC/TCG review period: RFC_start_date - RFC_end_dateThe comments from the TCG members during the RFC/TCG review should be included in the next section. In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your Wiki Name so that authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from TCG member during the RFC/TCG Review Period: TCG_start_date - TCG_end_dateWG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupGrid & Web Services Working GroupRegistry Working GroupSemantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupRadio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes CommitteeTCG Vote : Vote_start_date - Vote_end_dateIf you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
<--
|