<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="">Dear DM<div class=""><br class=""><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>All REC models (IVOA, Meas, Coords, Provenance) should be accessible through <a href="https://ivoa.net/xml/VODML/%3CModel%3E-v1.vo-dml.xml" class="">https://ivoa.net/xml/VODML/<Model>-v1.vo-dml.xml</a></div><div>This is true for all but Coords which returns a 404. The link was working when the model has been published, I’ll ask for restoring the reWrite rule.</div><div><br class=""></div><div>However I’m not satisfied with the way those VODML files are published because the physical URLs e.g <a href="https://ivoa.net/xml/VODML/%3CModel%3E-v1.8.vo-dml.xml" class="">https://ivoa.net/xml/VODML/<Model>-v1.8.vo-dml.xml</a> are hidden.</div><div>Both links should be visible on the XML page.</div><div><br class=""></div><div>Laurent</div><div><br class=""></div></div></div>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On 22 Feb 2023, at 13:17, 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="">I didn't look for them -- but while giving in to the fact that I'll<br class="">have to shallow-parse the VO-DML in order to come up with the<br class=""><mild expletive deleted> VO-DML ids in MIVOT I stepped into a few<br class="">problems related to obtaining VO-DML files that, I think, nicely<br class="">illustrate my point that whatever isn't validated (or at least used)<br class="">by a machine is broken.<br class=""><br class="">(1) The IVOA types DM (sigh!) ivoa.vo-dml.xml<br class="">(<a href="https://ivoa.net/xml/VODML/IVOA-v1.vo-dml.xml" class="">https://ivoa.net/xml/VODML/IVOA-v1.vo-dml.xml</a>) is schema-invalid:<br class=""><br class=""> <string>:7:0:ERROR:SCHEMASV:SCHEMAV_ELEMENT_CONTENT: Element 'title': This element is not expected. Expected is one of ( identifier, uri ).<br class=""><br class="">This is because the model element in VO-DML has a mandatory uri<br class="">element, which is described as:<br class=""><br class=""> Each model has an associated model URI that MUST be used to<br class=""> reference it, for example in ModelImports or in VOTable<br class=""> annotations. Dereferencing the model URI and following redirects<br class=""> yields the latest VO-DML for the data model<br class=""><br class="">Inserting <uri><a href="http://www.ivoa.net/xml/VODML/v1</uri>" class="">http://www.ivoa.net/xml/VODML/v1</uri></a> in front of the<br class="">title element fixes this.<br class=""><br class="">(2) While I was figuring this out, I noticed that in coords, meas,<br class="">and phot (didn't check the others), the uri element is present but<br class="">empty. I'm pretty sure we should fix that, and I guess as an<br class="">editorial oversight I'd even do it without an erratum process.<br class="">Who'll push it along?<br class=""><br class="">[but at least these other vo-dmls are schema-valid]<br class=""><br class="">(3) Requesting the coords model at<br class=""><br class=""><a href="https://ivoa.net/xml/VODML/Coords-v1.vo-dml.xml" class="">https://ivoa.net/xml/VODML/Coords-v1.vo-dml.xml</a><br class=""><br class="">results in a 300 Multiple Choices response from our web server.<br class="">That's because the underlying file is called Coords-v1.0.vo-dml.xml<br class="">(note the extra ".0"). I think I've always argued that -v1 should<br class="">redirect to -v1.0. But I'm open to any alternative, as long as<br class="">people get a plain 200 or redirect when they access the DM URI.<br class="">Who'll tackle this?<br class=""><br class=""><br class="">I give you all of these are minor annoyances, but, really, I again<br class="">take them as indications we've not done a good job providing<br class="">reference implementations of MIVOT yet.</div></div></blockquote><blockquote type="cite" class=""><div class=""><div class=""><br class=""> -- Markus<br class=""></div></div></blockquote></div><br class=""></div></body></html>