<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; 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 tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> registry-bounces@ivoa.net <registry-bounces@ivoa.net> on behalf of Markus Demleitner <msdemlei@ari.uni-heidelberg.de><br>
<b>Sent:</b> Wednesday, February 3, 2021 3:47:36 AM<br>
<b>To:</b> registry@ivoa.net<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 class="PlainText">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">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">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://ia2.inaf.it/tap/projects (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>
</body>
</html>