<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><br></div>Please note that the SSA standard already provide a solution to this problem.<div>It defines, in §4.2:<div><span style="text-align: justify;"><br></span></div><div style="text-align: start;"><span style="text-align: justify;">"Another INFO</span><span style="text-align: justify;"> with </span><span style="text-align: justify; font-family: 'Courier New';">name="SERVICE_PROTOCOL" </span><span style="text-align: justify;">should contain the protocol version number in its value attribute and the
name of the service protocol as the fixed string </span><span style="text-align: justify;">”</span><span style="text-align: justify; font-family: 'Courier New';">SSAP</span><span style="text-align: justify;">”</span><span style="text-align: justify;"> </span><span style="text-align: justify;">(see
version negotiation </span><span style="text-align: justify;">8.2.4)."</span></div><div><p class="MsoNormal" style="margin-left:0in;text-align:justify"> </p>
<table class="MsoNormalTable" style="width: 492.5pt; border-collapse: collapse; position: static; z-index: auto;" width="493" cellspacing="0" cellpadding="0" border="0">
<tbody><tr>
<td style="width:100.0%;border:double #7F7F7F 4.5pt;background:
silver;padding:0in 3.75pt 0in 3.75pt" width="100%"><p class="MsoNormal" style="margin-left:0in"><b>Example:</b><b><o:p></o:p></b></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:"Courier New";mso-bidi-font-family:"MS Mincho""><INFO
name="SERVICE_PROTOCOL" value="1.02">SSAP</INFO></span></p></td></tr></tbody></table><div><br></div><div><br></div><div>We are implementing SSA here at ESO as we speak… </div><div>so I guess I will ask to have implemented BOTH the SERVICE_PROTOCOL</div><div>AND the STANDARD_ID, so to be compliant to both SSA and DALI standards.</div><div><br></div><div>Alberto</div><div><br></div><div><br></div><div><div>On 21 Mar 2017, at 12:08, Pierre Fernique <<a href="mailto:Pierre.Fernique@astro.unistra.fr">Pierre.Fernique@astro.unistra.fr</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div bgcolor="#FFFFFF" text="#000000"><p><br>
</p>
Dear DAL and App contributors,<br>
and especially SIAv2 and Datalink authors,
<p>In the contexte of the Aladin v10 developments, we are facing to
a recurrent issue in the IVOA protocol suite. <br>
</p><p><b>Most of IVOA protocols return VOTable, but without any
signature or magic code. </b><br>
The consequence: IVOA clients can not easily recognize that this
VOTable stream comes from a CS, a SIAv1, a SIAv2, a SSA, a
Datalink, a TAP, an obsTAP or any other IVOA VOTable query result.<br>
</p><p>Based on the presence of some UCDs or utypes or INFO tags, Aladin
tries to recognize the original protocol in order to have the
adequat actions (basic table display, fov supports, popup menus,
column display filtering...). But we fail to find such a method
for SIAv2. We are, more or less able to recognize obsCore results
(based on utypes list => "obscore:ObsDataset.dataProductType",
"obscore:Access.Reference" and "obscore:Access.Format"
, but it is not specifical to SIAv2.</p><p>We are facing to the same difficulty for Datalink results. In
this case, it is worse in the sense that some providers have
already inserted Datalink links inside SIAv1 or CS results (see
examples below). So in these cases,<b> we cannot know "a priori"
that such link will return Datalink VOTable stream</b>. Without
this knowledge, at the end, Aladin can only try to display on the
sky view the VOTable Datalink result as a regular astronomical
catalog (sad !).<br>
</p><p>So, how can we do ? Thanks for any help.</p><p><b>For the future standard releases, may we just think to
systematically add the standardID of the original protocol
inside an INFO tag, or something equivalent ?</b><br>
</p><p>Pierre Fernique & Chaitra (in charge of SIAv2/Datalink/...
implementation in Aladin v10)</p><p>---<br>
</p><p>Datalink examples:</p><p><b>GAVO SIAv1</b></p>
<ul>
<li><a class="moz-txt-link-freetext" href="http://dc.zah.uni-heidelberg.de/lswscans/res/positions/siap/siap.xml?POS=210.8431667,54.2961666667&SIZE=0.1323&FORMAT=image/fits">http://dc.zah.uni-heidelberg.de/lswscans/res/positions/siap/siap.xml?POS=210.8431667,54.2961666667&SIZE=0.1323&FORMAT=image/fits</a></li>
<li>=> Example of Datalink URL inside the result :
<a class="moz-txt-link-freetext" href="http://dc.zah.uni-heidelberg.de/lswscans/res/positions/dl/dlmeta?ID=ivo%3A//org.gavo.dc/%7E%3Flswscans/data/part2/Schmidtplatten/FITS/A82.fits">http://dc.zah.uni-heidelberg.de/lswscans/res/positions/dl/dlmeta?ID=ivo%3A//org.gavo.dc/%7E%3Flswscans/data/part2/Schmidtplatten/FITS/A82.fits</a></li>
</ul><p><b>VizieR CS</b></p>
<ul>
<li><a class="moz-txt-link-freetext" href="http://vizier.u-strasbg.fr/viz-bin/votable?-source=B%2Fcfht%2Fobscore&-c=09+55+33.17+%2B69+03+55.1&-out.add=_RAJ,_DEJ&-oc.form=dm&-out.meta=DhuL&-out.max=999999&-c.rm=10.81&-out=_VizieR,*Mime(image/fits),*&-mime=TSV&-out.all">http://vizier.u-strasbg.fr/viz-bin/votable?-source=B%2Fcfht%2Fobscore&-c=09+55+33.17+%2B69+03+55.1&-out.add=_RAJ,_DEJ&-oc.form=dm&-out.meta=DhuL&-out.max=999999&-c.rm=10.81&-out=_VizieR,*Mime(image/fits),*&-mime=TSV&-out.all</a></li>
<li>=> Example of Datalink URL inside the result :
<a class="moz-txt-link-freetext" href="http://www.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/caom2ops/datalink?runid=ejkaxv927qnvu4ef&ID=caom%3ACFHT%2F469601%2F469601o">http://www.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/caom2ops/datalink?runid=ejkaxv927qnvu4ef&ID=caom%3ACFHT%2F469601%2F469601o</a><br>
</li>
</ul>
</div>
</blockquote></div><br></div></div></body></html>