<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>As the implementor of one of the two RegTAP 1.1 reference implementations, I support this reversion to requiring ivo_nocasematch rather than lock in the ADQL version dependency. <br>
</p>
<p><br>
</p>
<p>It is worth noting that because of the configuration of the STScI full searchable Registry database, all text matching is done case insensitively, and our implementation on this point is dodgy: both ILIKE and the user function are aliases over the default
"LIKE" behavior. (So really, we implement ILIKE and ivo_nocasematch correctly, but never did for LIKE.) I should have perhaps taken this as a sign to pay more attention to this part of the spec rather than less. Thank you Marco for bringing it up.</p>
<p><br>
</p>
<p>As Reg chair, I know the voting dates for this remain undefined; we were hoping for a quick tally with the comments and bringing it up for TCG/Exec approval in November. Once the document reflects a general agreement on this issue, I'll formally set those
dates and ask again for input. It seems very likely we can still make that deadline.<br>
</p>
<p><br>
</p>
<p>--Theresa<br>
</p>
<p><br>
</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 Mark Taylor <M.B.Taylor@bristol.ac.uk><br>
<b>Sent:</b> Thursday, August 8, 2019 5:02:12 AM<br>
<b>To:</b> Molinaro, Marco<br>
<b>Cc:</b> IVOA Registry; IVOA DAL<br>
<b>Subject:</b> Re: RegTAP-1.1 & ADQL-2.1 - the ILIKE concerns</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Marco,<br>
<br>
I am all in favour of your suggestion. As far as I can see the move<br>
to ILIKE in RegTAP is really just a bit of tidying up that can harmlessly<br>
be omitted or deferred if the interaction with ADQL 2.1 is potentially<br>
problematic (which it seems it may be). I'm not aware that ILIKE does<br>
anything that ivo_nocasematch does not. From an implementation point<br>
of view in topcat I'm unlikely to be using ILIKE in this context<br>
(except maybe for example queries copied from the RegTAP 1.1 document),<br>
since ivo_nocasematch is required for all RegTAP service versions<br>
and ILIKE is not, so there's less logic required to just use the<br>
UDF in all cases.<br>
<br>
Mark<br>
<br>
<br>
On Thu, 8 Aug 2019, Molinaro, Marco wrote:<br>
<br>
> Dear ReR-ers,<br>
> (DAL-ers for reference)<br>
> <br>
> in the process of reviewing RegTAP-1.1 PR from the DAL perspective<br>
> a consideration come up with respect to the strong dependency of<br>
> RegTAP-1.1 case insensitive comparison on ADQL-2.1 (PR itself)<br>
> ILIKE operator.<br>
> <br>
> Two issues came up: RegTAP waiting ADQL for proper dependency<br>
> reference; too strong dependency/forcing of RegTAP requirement<br>
> over the ADQL specification.<br>
> <br>
> The first is actually minor/can-be-worked-around, the latter is more<br>
> critical.<br>
> <br>
> As things currently stand, there's the risk RegTAP controls ADQL behaviour<br>
> of ILIKE or that ADQL can break RegTAP when/if changing ILIKE definition.<br>
> <br>
> Proposed solution is to re-instate the ivo_nocasematch in RegTAP,<br>
> decoupling the specifications and releasing the two issues above in one<br>
> shot.<br>
> <br>
> Comments and discussion highly welcome (including detailed explanations<br>
> from the spec editors and thoughts from implementors).<br>
> <br>
> Cheers<br>
> Marco<br>
> <br>
<br>
--<br>
Mark Taylor Astronomical Programmer Physics, Bristol University, UK<br>
m.b.taylor@bris.ac.uk +44-117-9288776 <a href="http://www.star.bris.ac.uk/~mbt/">
http://www.star.bris.ac.uk/~mbt/</a><br>
</div>
</span></font>
</body>
</html>