<div dir="ltr">Hi Markus, all,<div><br></div><div>I like the WD, here follow some (I imagine minor) points.</div><div><br></div><div>In the introduction, resource records' numbers may be </div><div>updated (now it's nearly 20000 records out of about 40</div><div>registries), but maybe you'd like to wait for this WD to </div><div>change state before.</div><div><br></div><div>Also it refers to RI-1.0 and the XML search interface.</div><div>Does it make sense, given RI-1.1 RFC?</div><div><br></div><div>Given the RegTAP tables now report datatypes in the</div><div>more general form, I think we can nicely remove the</div><div>Appendix C.</div><div><div class="gmail_extra"><br></div><div class="gmail_extra">There are still a couple of "RegTAP#1.0" strings around</div><div class="gmail_extra">in §7 (pg.12) and §9.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Apart from that (and maybe a fix to the nearly empty</div><div class="gmail_extra">pg.17) I'm ok with the specification update.<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Cheers,</div><div class="gmail_extra"> Marco</div><div class="gmail_extra"><br><div class="gmail_quote">2017-12-07 14:46 GMT+01:00 Markus Demleitner <span dir="ltr"><<a href="mailto:msdemlei@ari.uni-heidelberg.de" target="_blank">msdemlei@ari.uni-heidelberg.de</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear Registry community,<br>
<br>
Since I guess VOResource 1.1 won't change terribly much any more, I<br>
went ahead and put up RegTAP 1.1 on the document repository, also in<br>
celebration of the REC's fourth birthday:<br>
<br>
<a href="http://ivoa.net/documents/RegTAP/20171206/index.html" rel="noreferrer" target="_blank">http://ivoa.net/documents/<wbr>RegTAP/20171206/index.html</a><br>
<br>
This is essentially just adapting for the changes of VOResource 1.1.<br>
As behooves a point release, it shouldn't break existing clients (or<br>
so I claim). As a matter of fact, the RegTAP service at<br>
<a href="http://dc.g-vo.org/tap" rel="noreferrer" target="_blank">http://dc.g-vo.org/tap</a> already implements RegTAP 1.1 (or so I claim).<br>
<br>
As confessed during the Shanghai interop, I'm cheating a bit, though:<br>
the rr.resource.rights column is going away, which would count as an<br>
incompatible change. If anyone had done anything with this column,<br>
which I claim hasn't been the case. Still, protest if you think<br>
that's fishy.<br>
<br>
Also, the handling of the securityMethod element has changed. As in<br>
VOResource, I claim we can do this in a point release because we know<br>
the feature hasn't been used so far. As a consequence, the<br>
recommended discovery patterns have changed to include the new<br>
security_method_id columns (clients will unfortunately have to work<br>
out if they're dealing with RegTAP 1.1 services before they can use<br>
it).<br>
<br>
Please have a look at the WD and comment -- and if you're running<br>
a RegTAP service or plan on doing so, please have a paricularly close<br>
look.<br>
<br>
If you prefer looking at diffs, see the commits leading up to this:<br>
<br>
svn log -r 3676:HEAD <a href="https://volute.g-vo.org/svn/trunk/projects/registry/regtap" rel="noreferrer" target="_blank">https://volute.g-vo.org/svn/<wbr>trunk/projects/registry/regtap</a><br>
<br>
or use viewvc:<br>
<br>
<a href="https://volute.g-vo.org/viewvc/volute/trunk/projects/registry/regtap/RegTAP.tex?view=log&pathrev=4610" rel="noreferrer" target="_blank">https://volute.g-vo.org/<wbr>viewvc/volute/trunk/projects/<wbr>registry/regtap/RegTAP.tex?<wbr>view=log&pathrev=4610</a><br>
<span class="HOEnZb"><font color="#888888"><br>
-- Markus<br>
</font></span></blockquote></div><br></div></div></div>