<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:monospace">Hi,</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">fixed the IA2 TAP resource.</div><div class="gmail_default" style="font-family:monospace">I'm not sure where that 1.1 came from, possibly simply my fault.</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">I'll check if other resources I managed are affected.</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">Cheers</div><div class="gmail_default" style="font-family:monospace"> Marco</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il giorno mer 3 feb 2021 alle ore 17:09 Theresa Dower <<a href="mailto:dower@stsci.edu">dower@stsci.edu</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div dir="ltr">
<div id="gmail-m_-6605246293532002902x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt;color:rgb(0,0,0);font-family:Calibri,Helvetica,sans-serif">
<p><br>
</p>
<p>Aha, thank you Juan for catching this, and to Markus for the quick follow-up.</p>
<p><br>
</p>
<p>I've fixed the stray MAST resource at our publishing registry end, hopefully as noted the VizieR update resolves the bulk of the issues.</p>
<p><br>
</p>
<p>Cheers,</p>
<p>--Theresa</p>
</div>
<hr style="display:inline-block;width:98%">
<div id="gmail-m_-6605246293532002902x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> <a href="mailto:registry-bounces@ivoa.net" target="_blank">registry-bounces@ivoa.net</a> <<a href="mailto:registry-bounces@ivoa.net" target="_blank">registry-bounces@ivoa.net</a>> on behalf of Markus Demleitner <<a href="mailto:msdemlei@ari.uni-heidelberg.de" target="_blank">msdemlei@ari.uni-heidelberg.de</a>><br>
<b>Sent:</b> Wednesday, February 3, 2021 3:47:36 AM<br>
<b>To:</b> <a href="mailto:registry@ivoa.net" target="_blank">registry@ivoa.net</a><br>
<b>Subject:</b> Re: VOResource 1.1 namespace implementations breaking XSD validity</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt">
<div>External Email - Use Caution<br>
<br>
Juan,<br>
<br>
On Tue, Feb 02, 2021 at 04:24:56PM +0100, Juan Gonzalez wrote:<br>
> Performing a compliance check we have found out that that ~85% of<br>
> the VOResources currently published in the IVOA ecosystem are using<br>
> the following namespace:<br>
><br>
> xmlns:vr="<a href="http://www.ivoa.net/xml/VOResource/v1.1" target="_blank">http://www.ivoa.net/xml/VOResource/v1.1</a>"<br>
<br>
Ouch. Yeah, that's bugs (which fortunately didn't hit at least my<br>
RegTAP services because of fortunate conincidences).<br>
<br>
> So in our understanding,<br>
> xmlns:vg="<a href="http://www.ivoa.net/xml/VORegistry/v1.0" target="_blank">http://www.ivoa.net/xml/VORegistry/v1.0</a>" would have to be<br>
> used to not break XSD validity.<br>
<br>
That is right.<br>
<br>
> This seems to be more on our responsibility as Registry providers<br>
> to check resources validity. Would there be general consensus to<br>
> request our publishing registries to perform this change?<br>
<br>
Sure: Dear registry operators, please make it a routine to run your<br>
registries through the validator at the beginning of each month.<br>
<br>
However, this particular problem doesn't concern too many operators.<br>
VizieR, where most of this comes from, will have a shiny new<br>
publishing registry real soon now (cf. the talk at the last interop),<br>
so that problem is going to go away by itself.<br>
<br>
Then I'm spotting ivo://xcatdb/3xmmdr7/tap, which is produced by you<br>
and should be easily fixed (use the opportunity to fix the<br>
broken xsi:schemaLocation on this one), and likewise<br>
ivo://<a href="http://ia2.inaf.it/tap/projects" target="_blank">ia2.inaf.it/tap/projects</a> (though the schemaLocation is fine in<br>
this case). It might be interesting to understand where the bad<br>
namespace URIs came from.<br>
<br>
Finally, there's ivo://mast.stsci/ssap/befs served by STScI. I'm<br>
sure Theresa can quickly fix this one.<br>
<br>
So... phewy... it's essentially three records plus something that's<br>
already fixed with the rollout of the fix pending.<br>
<br>
Thanks for bringing this up,<br>
<br>
Markus<br>
</div>
</span></font>
</div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div><font face="monospace">Marco Molinaro</font></div><div><font face="monospace">INAF - Istituto Nazionale di AstroFisica</font></div><div><font face="monospace">Osservatorio Astronomico di Trieste</font></div><div><font face="monospace">email <a href="mailto:marco.molinaro@inaf.it" target="_blank">marco.molinaro@inaf.it</a></font></div><div><span style="font-family:monospace">tel. +39 040 3199 152</span><br></div></div></div></div></div></div></div>