<html><head></head><body><p dir="ltr">Hi</p>
<p dir="ltr">We have multi-resource notables in datalink, don't we?</p>
<p dir="ltr">Besides that, i agree on everything. In particular i also guess that this info element is better placed as a child of votable.</p>
<p dir="ltr">Carlos</p>
<p dir="ltr"><!-- tmjah_g_1299s -->Enviado desde <a href="http://www.typeapp.com/r">TypeApp<!-- tmjah_g_1299e --></a><br><br></p>
<div class="gmail_quote" >En 30 de mar. de 2017, en 11:58, Mark Taylor <<a href="mailto:M.B.Taylor@bristol.ac.uk" target="_blank">M.B.Taylor@bristol.ac.uk</a>> escribió:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="blue">Marco,<br><br>On Mon, 27 Mar 2017, Marco Molinaro wrote:<br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> 2017-03-23 10:40 GMT+01:00 François Bonnarel<br> <francois.bonnarel@astro.unistra.fr>:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><br> 1 ) Having the standardID of the protocol in an INFO tag of the response is<br> definitely a good idea.<br></blockquote> <br> Regarding this topic, Pierre lighted a discussion at last week's<br> ASTERICS DADI Tech Forum.<br> The general opinion was that it's a good idea indeed, and that an INFO<br> element (as a <votable><br> child) could take care of this information.<br> <br> Some hesitation whether this info should be <resource> related was<br> expressed, but it seems<br> that, for now at least something like:<br> <br> <info name="STANDARD_ID"
value="ivo://<a href="http://ivoa.net/TAP">ivoa.net/TAP</a>"/><br> <br> may be ok.<br> <br> Now, while looking at DALI-1.1, I realized that it's already there<br> (§4.4.3) and it's there since DALI-1.0.<br></blockquote><br>Good catch! And apologies that (as a listed DALI author) I didn't<br>realise that was in place.<br> <br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> The changes to make would be<br> - move it from a MAY clause into some more robust recommendation (not<br> a MUST, of course)<br></blockquote><br>Yes, I'd say it should get promoted to a SHOULD.<br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> - define if it should be "standardID" (as it is now in the text) or<br> "STANDARD_ID",<br> as proposed by Markus following the QUERY_STATUS format<br></blockquote><br>Since it's already present as "standardID" I do!
n't
think there<br>is a good argument to change the capitalisation.<br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> - consider if we have to move that <info> from being child of<br> <resource> (DALI-1.1 currently)<br> to a child of <votable> directly<br></blockquote><br>Not so sure about this. I *think* it's more logical to have it as<br>a direct child of the VOTable document, since that's what's<br>coming from the service. On the other hand, DALI 4.4 says that<br>anything outside of the RESOURCE labelled type="results" is outside<br>the scope of DALI. At present, we don't have multi-resource VOTable<br>documents from any service, but one or the other option might look<br>more sensible if at some time in the future we do.<br>But on balance, I'd say leave the DALI text as it is and work with that.<br><br>Mark<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></pre></blockquote></div></body></html>