<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<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>
<p>Markus:<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><span style="color:rgb(33,33,33); font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif,serif,EmojiFont; font-size:13.3333px">> I'm fairly convinced we should phase out SimpleDALRegExt as the </span><span style="color:rgb(33,33,33); font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif,serif,EmojiFont; font-size:13.3333px">standards
covered there get reviewed</span></p>
<p><span style="color:rgb(33,33,33); font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif,serif,EmojiFont; font-size:13.3333px">....<br>
</span></p>
<p><span style="color:rgb(33,33,33); font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif,serif,EmojiFont; font-size:13.3333px">><font size="2"><span style="font-size:10pt">So... I'm rather fervently for retiring the SCS section in SimpleDALRegExt
and having everything in SCS.</span></font></span></p>
<p><span style="color:rgb(33,33,33); font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif,serif,EmojiFont; font-size:13.3333px"><br>
</span></p>
<p><span style="color:rgb(33,33,33); font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif,serif,EmojiFont; font-size:13.3333px">A good point, and one I'd actually forgotten about since this particular capability hasn't been touched in
a while. Either way it looks like SimpleDALRegExt needs updated to match this, even if by removing the SCS resource section entirely and and pointing back to the SCS spec that now overrides it. I'll work on that in parallel once this gets out of WD. Thanks!<br>
</span></p>
<p><span style="color:rgb(33,33,33); font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif,serif,EmojiFont; font-size:13.3333px"><br>
</span></p>
<p><span style="color:rgb(33,33,33); font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif,serif,EmojiFont; font-size:13.3333px"><br>
</span></p>
<p><span style="color:rgb(33,33,33); font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif,serif,EmojiFont; font-size:13.3333px"></span></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> dal-bounces@ivoa.net <dal-bounces@ivoa.net> on behalf of Markus Demleitner <msdemlei@ari.uni-heidelberg.de><br>
<b>Sent:</b> Tuesday, September 1, 2020 11:58:34 AM<br>
<b>To:</b> dal@ivoa.net<br>
<b>Subject:</b> Re: Working Draft - Simple Cone Search, v.1.1 2020-08-28 - released</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt">
<div class="PlainText">External Email - Use Caution<br>
<br>
Hi Theresa,<br>
<br>
On Tue, Sep 01, 2020 at 02:18:50PM +0000, Theresa Dower wrote:<br>
> From the Registry end: it seems it may be helpful to add<br>
> capability/interface information noting time information support,<br>
> especially in the test query. Note this change would be in<br>
> SimpleDALRegExt, and included back to the main CS document. Do we<br>
> think this section is solid enough to work on it now, or do we keep<br>
> it in mind for later in the WD process?<br>
<br>
I'm fairly convinced we should phase out SimpleDALRegExt as the<br>
standards covered there get reviewed -- discovery is an integral part<br>
of a standard and thus shouldn't be regulated somehwere else.<br>
That we did it differently for the old S-protocols was just because<br>
the Registry wasn't (really) ready when the SCS and SIAP came along<br>
(well... for SSAP and SLAP Registry would have been there, but the<br>
bad pattern had already been established).<br>
<br>
So... I'm rather fervently for retiring the SCS section in<br>
SimpleDALRegExt and having everything in SCS.<br>
<br>
[Apologies to DAL: Registry in-talk start]<br>
Now that I skim SimpleDALRegExt again I notice it doesn't say "only<br>
valid until overridden" clearly and early enough. While it's still<br>
in WD (pending a few more adoptions of SSAP productType), I think I'd<br>
just explicitly say:<br>
<br>
Regulations here are only valid until the specifications themselves<br>
define their modes of discovery.<br>
<br>
in the abstract and repeat it a few times at strategic places in the<br>
document.<br>
[Registry in-talk end]<br>
<br>
<br>
As to noting TIME support: Well, we already have param in<br>
vs:ParamHTTP (DaCHS, for instance, has declared its SCS parameters in<br>
this way forever). Sure, you need to query the Registry to figure<br>
out parameters in this way, but while doing discovery that's not a<br>
problem.<br>
<br>
When talking to a service a client has run into in another way, I'd<br>
say MAXREC=0 metadata discovery, SSAP-style, ought to do the trick.<br>
<br>
-- Markus<br>
</div>
</span></font></div>
</body>
</html>