<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p><br>
</p>
<meta content="text/html; charset=UTF-8">
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size: 12pt; color: rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif, "EmojiFont", "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols;">
<p>Paul,</p>
<p><br>
</p>
<p>Thanks for looking into the issue and writing up the errata! I agree with you and Markus that removing the unused
<span>ProtoSpectralAccess element is the thing to do here.</span></p>
<p><span><br>
</span></p>
<p><span>--Theresa<br>
</span></p>
<p><span></span><br>
</p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> registry-bounces@ivoa.net <registry-bounces@ivoa.net> on behalf of Paul Harrison <paul.harrison@manchester.ac.uk><br>
<b>Sent:</b> Friday, August 24, 2018 12:32:24 PM<br>
<b>To:</b> Markus Demleitner<br>
<b>Cc:</b> registry@ivoa.net<br>
<b>Subject:</b> Re: error in SSAP v1.2 extension schema</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText"><br>
<br>
> On 2018-08 -24, at 09:15, Markus Demleitner <msdemlei@ari.uni-heidelberg.de> wrote:<br>
> <br>
> Hi Paul,<br>
> <br>
> On Thu, Aug 23, 2018 at 11:05:27AM +0000, Paul Harrison wrote:<br>
>> there is an error in the SSAP extension schema that is delivered<br>
>> for the <a href="http://www.ivoa.net/xml/SSA/v1.1" id="LPlnk629071" previewremoved="true">
http://www.ivoa.net/xml/SSA/v1.1</a> namespace (which is in<br>
>> fact v1.2 of the schema). This schema file has an element<br>
>> ProtoSpectralAccess defined which is erroneously an extension at<br>
>> line 958 of ssap:SSACapRestriction which does not exist in the<br>
>> schema.<br>
> <br>
> Ouch. My bad. For SimpleDALRegExt 1.1, we dropped the restriction<br>
> (that fixed the standardID, which kept people from using the SIA<br>
> extension to register SIAv2 services). I ran an XML validator on the<br>
> schema file, which doesn't catch this.<br>
> <br>
> Regrettably, even loading the schema into an (lxml-based) schema<br>
> processor doesn't flag the issue, so I again haven't noticed it. Hm.<br>
> I can't say I understand why that is, and I don't have time just now<br>
> to try and figure it out.<br>
<br>
It is my recent adventures in using code generation tools that have highlighted these issues - they generate the code without complaint, but then the compiler spots it easily….Though when subsequently verifying that the compiler was right, the eclipse schema
validator did find the problem, after I too had made the initial error of just XML validating...<br>
<br>
> But having ProtoSpectralAccess part of the standard has been painful<br>
> all along. I'd argue that removing something that shouldn't have<br>
> been there, that is no longer used, that should not be used in the<br>
> future, and the removal of which will make this work a better place<br>
> shouldn't be blocked by the TCG.<br>
> <br>
> Does anyone want to protest? If not: Paul, do you feel like writing<br>
> an Erratum for the removal?[1]<br>
<br>
<br>
<br>
I am happy to write the erratum is no-one objects….<br>
<br>
<br>
Paul.<br>
<br>
</div>
</span></font></div>
</body>
</html>