<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><font face="Courier" class=""><span style="font-style: normal;" class="">Dear VO<br class=""></span></font><br class=""><div><div class=""><div class=""><font face="Courier" class=""><span style="font-style: normal;" class="">There has been much discussion about the MIVOT validation during the RFC period.<br class="">These discussions started on the DM list</span></font><span style="font-family: Courier;" class="">, as usual,</span><span style="font-family: Courier;" class=""> </span><span style="font-family: Courier;" class="">before migrating toward the TCG list before becoming mostly private.</span></div><div class=""><font face="Courier" class=""><span style="font-style: normal;" class="">I apologize to the interested people who could not follow the threads because of this.<br class="">To try to make up for this I have written this summary of the situation 5 weeks before Interop so that interested folks can follow the MIVOT session in Bologna (DM I).<br class=""><br class="">There are currently 2 groups apart of DM (Apps and Semantic) and 5 IGs that have not voted although the RFC period has been open in last September<br class=""><br class="">I’m going to list here the points which were open as well as the answers which were brought there. </span></font></div><div class=""><font face="Courier" class=""><span style="font-style: normal;" class="">- I encourage the chairs to correct me if I'm wrong.</span></font></div><div class=""><font face="Courier" class=""><span style="font-style: normal;" class="">- This message is sent to ivoa@net because several groups are mentioned.<br class=""><br class="">For newcomers:</span></font></div><div class=""><font face="Courier" class=""><span style="font-style: normal;" class="">==============</span></font></div><div class=""><font face="Courier" class=""><span style="font-style: normal;" class="">MIVOT is a standard that defines an XML syntax to link VOTable data to one or more models. </span></font></div><div class=""><font face="Courier" class=""><span style="font-style: normal;" class="">MIVOT is designed so that the XML elements mapping data onto models are grouped in a block isolated from the rest of the VOTable. </span></font></div><div class=""><font face="Courier" class=""><span style="font-style: normal;" class="">The purpose of MIVOT is to tell how form such blocks. </span></font></div><div class=""><font face="Courier" class=""><span style="font-style: normal;" class="">MIVOT as such does not carry any semantic.</span></font></div><div class=""><font face="Courier" class=""><span style="font-style: normal;" class=""><br class=""></span></font></div><div class=""><font face="Courier" class=""><span style="font-style: normal;" class="">Ops IG (voted)</span></font></div><div class=""><font face="Courier" class=""><span style="font-style: normal;" class="">==============</span></font></div><div class=""><font face="Courier" class=""><span style="font-style: normal;" class="">Group suggestion:</span></font></div><div class=""><font face="Courier" class=""><span style="font-style: normal;" class="">- [DONE] put in the document a complete annotated VOTABLE </span>to which links in the text will point.</font></div><div class=""><br class=""></div><div class=""><font face="Courier" class=""><span style="font-style: normal;" class="">Registry WG (voted)<br class="">================</span></font></div><div class=""><font face="Courier" class=""><span style="font-style: normal;" class="">Group requests:<br class="">- [DONE] add a section about how to declare services producing MIVOT annotations in the registry<br class="">- [PR] clarify the role of some snippets given in the document<br class="">- [WIP] produce a reader's guide to the different reference implementations proposed<br class=""><br class="">Apps (Not voted)<br class="">=============</span></font></div><div class=""><font face="Courier" class=""><span style="font-style: normal;" class="">Apps is certainly, apart from DM, the group most concerned by this standard.<br class=""></span></font></div><span style="font-family: Courier;" class="">Group requests:</span><br class="" style="font-family: Courier;"><div class=""><font face="Courier" class=""><span style="font-style: normal;" class="">- [DONE] clarify how NULL values are handled<br class="">- [WIP] produce a reader's guide to the different reference implementations proposed<br class="">- [WIP](*) give the possibility to members of the group to propose use cases other than those implemented in our examples.<br class=""><br class="">(*) We keep a slot at Interop for this purpose in case nobody answers before (this is a call for contribution).<br class=""><br class="">Semantic</span></font> <span style="font-family: Courier;" class=""> (Not voted)</span><br class="" style="font-family: Courier;"><font face="Courier" class="">====================<br class="">Although this standard is not connected with the semantic activities, this is where we had the most of requests.<br class=""></font><span style="font-family: Courier;" class="">Group requests:</span><br class="" style="font-family: Courier;"><font face="Courier" class="">- [DONE] Numerous corrections and clarifications of the text<br class="">- [WIP] produce a reader's guide to the different reference implementations proposed<br class="">- [WIP](*) Improve the visibility of resources related to model standards on ivoadoc</font></div><div class=""><font face="Courier" class="">- [PR] </font><span style="font-family: Courier;" class=""> add an appendix telling where to find VODML resources and ho to interpret them in regard with the MIVOT syntax</span></div><div class=""><font face="Courier" class="">- [DONE] Provide an advanced validator able to check that the structure of mapped models is well respected<br class="">- [DONE](**)Provide a VOTable containing real GAIA data and a mapping block grouping position, pm, parallax and radial velocity.<br class="">- [DONE](**)Provide a VOTable containing real GAIA data and a mapping block giving a complete definition of the photometric data<br class=""><br class="">(*) in progress in relation with the document coordinator<br class="">(**) Since MIVOT has no semantic out of that of the mapped models, the request answers assume the use of MANGO DM that is barely a draft.<br class=""><br class=""></font></div></div><div class=""><font face="Courier" class="">LINKS</font></div><div class=""><font face="Courier" class="">=====</font></div><div class=""><font face="Courier" class="">MIVOT on Github. <a href="https://github.com/ivoa-std/ModelInstanceInVot" class="">https://github.com/ivoa-std/ModelInstanceInVot</a></font></div><div class=""><font face="Courier" class="">RFC page. <a href="https://wiki.ivoa.net/twiki/bin/view/IVOA/DataAnnotation" class="">https://wiki.ivoa.net/twiki/bin/view/IVOA/DataAnnotation</a></font></div><div class=""><font face="Courier" class=""><br class=""></font></div><div class=""><font face="Courier" class="">Best,</font></div><div class=""><font face="Courier" class=""><br class=""></font></div><div class=""><font face="Courier" class=""><br class=""></font></div><div class=""><font face="Courier" class="">Laurent</font></div></div><br class=""></body></html>