<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=""><div class="">Dear DM,</div><div class=""><br class=""></div><div class="">The MIVOT proposal (20/12/2023) has been updated (PR #174) in order to allow the RESOURCE containing the MIVOT block to be anywhere in the HOST resource.</div><div class=""><br class=""></div><div class="">The Markus proposal goes further since he suggest to drop the requirement of having the MIVOT block into a specific RESOURCE.</div><div class="">I’ve no strong opinion on that topic although it makes sense to me to see the model annotation block as a resource.</div><div class=""><br class=""></div><div class="">We need your comments on that that topic before to decide to go in one way or another.</div><div class="">An issue has been open for this </div><div class=""> <a href="https://github.com/ivoa-std/ModelInstanceInVot/issues/176" class="">https://github.com/ivoa-std/ModelInstanceInVot/issues/176</a></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">MIVOT authors</div><div class=""><br class=""></div><div class="">
<meta charset="UTF-8" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div>—</div><div>Translate with https: //<a href="http://www.deepl.com/translator" class="">www.deepl.com/translator</a></div><div class="">-- <br class="">jesuischarlie/Tunis/Paris/Bruxelles/Berlin<br class=""><br class="">Laurent Michel<br class="">SSC XMM-Newton<br class="">Tél : +33 (0)3 68 85 24 37<br class="">Fax : +33 (0)3 )3 68 85 24 32<br class="">Université de Strasbourg <<a href="http://www.unistra.fr" class="">http://www.unistra.fr</a>><br class="">Observatoire Astronomique<br class="">11 Rue de l'Université<br class="">F - 67200 Strasbourg</div></div></div>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On 15 Dec 2022, at 12:02, Markus Demleitner <<a href="mailto:msdemlei@ari.uni-heidelberg.de" class="">msdemlei@ari.uni-heidelberg.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Dear DM,<br class=""><br class="">On Wed, Dec 14, 2022 at 12:31:58PM -0500, CresitelloDittmar, Mark wrote:<br class=""><blockquote type="cite" class="">If I recall, it was originally that the annotation syntax would be in the<br class="">first RESOURCE of the VOTABLE, making it a simple insert with minimal<br class="">impact on the native VOTABLE. When it moved into the 'results' RESOURCE, I<br class="">think we wanted it to retain that 'minimal impact' on the native VOTABLE,<br class="">so required it to be the first child.<br class=""><br class="">I think that operationally it shouldn't matter where it resides within the<br class="">parent RESOURCE since there can be only 1 annotation block per 'results'<br class="">block.<br class=""></blockquote><br class="">Whatever the history: Looking again, when you put the annotation into<br class="">the RESOURCE it annotates anyway (which I think will make Mark<br class="">Taylor's life simpler when he merges multiple VOTables into one, so I<br class="">won't argue against it), you could drop the extra RESOURCE around the<br class="">VODML element entirely.<br class=""><br class="">Just write the VODML element directly into the RESOURCE with the<br class="">table (or whatever) and be done with it. This actually has the<br class="">advantage that parsing clients already have seen all the ID-s you are<br class="">talking about, because syntactically, this means VODML is at the end<br class="">of the RESOURCE.<br class=""><br class="">Thanks,<br class=""><br class=""> Markus<br class=""></div></div></blockquote></div><br class=""></body></html>