<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Pierre, <div class=""><br class=""></div><div class="">thanks for pointing this out. This is a topic we have been thinking of in VESPA, without a definitive solution yet, but we have ideas.</div><div class=""> </div><div class=""><div><blockquote type="cite" class=""><div class="">Le 12 févr. 2019 à 12:12, Pierre Fernique <<a href="mailto:Pierre.Fernique@astro.unistra.fr" class="">Pierre.Fernique@astro.unistra.fr</a>> a écrit :</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="content-type" content="text/html; charset=UTF-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class=""><p class=""><br class="">
</p><p class="">Dear Ssig, Apps and VESPA members<br class="">
</p><p class="">As you probably saw, we have more and more Solar System resources
available in the VO.<br class="">
This is a really good news (notably hanks to Europlanet effort)<br class="">
</p><p class="">But for client point of view, and notably Aladin, it is more and
more difficult to display and use correctly these new resources as
there is presently no standard way to specify the celestial body
concerned by each of these resources. Actually, in Aladin, we are
face to two issues :</p>
<ol class="">
<li class="">How to build correctly the data discovery tree ? Concretely,
how to move the good TAP, CS and other services to the Solar
System branch ?</li></ol></div></div></blockquote><div>One option would to have a dedicated mandatory <SUBJECT> item value in the registry record, e.g., "solar system". </div><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class=""><ol class="" start="2">
<li class="">How to handle the incompatible projections (sky resources over
planets, or the opposite, or Mars data over Io, etc...) ?</li></ol></div></div></blockquote><div>Here, we would need to provide the target body name also in the registry record. This could be done through the <subject>, naming the target body here, as well as the target region. For instance:</div><div><br class=""></div><div><content></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><subject>Solar Sytem</subject></div><div><span class="Apple-tab-span" style="white-space: pre;"> </span><subject>Mars</subject></div><div><span class="Apple-tab-span" style="white-space: pre;"> </span><subject>Planetary Surface</subject></div><div>…</div><div></content></div><blockquote type="cite" class=""><div text="#000000" bgcolor="#FFFFFF" class=""><ol class="" start="2"></ol></div></blockquote><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class=""><ol class="" start="2">
</ol><p class="">I progressed a little. For the first point, I made a very bad
hack based on the ivoid. We're lucky, most solar system resources
use EPN-core + DACHS server... and DACHS automatically uses an
ivoid containing the substring "/epn". By magic, 35 resources are
now placed in the Solar System branch. I also had to manually add
3 others resources ( jacobsuni/tap, pvol/tap and
<a href="http://vo-plasma.oeaw.ac.at/tap" class="">vo-plasma.oeaw.ac.at/tap</a>). The result is not bad (see below) but
this method is clearly debatable. And there is no distinction
between planets.<br class=""></p></div></div></blockquote><div>I don't think this should be the way to do it, as this relies on the specific implementation of TAP and EPNcore in DaCHS. For instance, the Vizier EPNcore table would not be identified with your hack.</div><div> </div><div>Identifying the EPNcore table should rely on the utype of the epncore table, which must be "<a href="ivo://vopdc.obspm/std/epncore#schema-2.0" class="">ivo://vopdc.obspm/std/epncore#schema-2.0</a>". This requires VODataService 1.1. At the moment, this is the assumption of the VESPA client. </div><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class=""><p class="">
</p><p class="">For the second point, I have not found a solution. Only Solar
System HiPS maps have a dedicated keyword for each body. But as
it is not the case for other resources of the Solar System, I can
not presently use this keyword.</p><p class=""><b class="">So the question : How to characterize Solar System resources
in the VO ? </b><br class="">
</p>
<ol class="">
<li class="">For the VO registry, do we have to invent a dedicated field
such as <obsbody>mars</obsbody> ?</li></ol></div></div></blockquote><div>Does the content/subject proposal fits this need ? </div><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class=""><ol class="" start="2">
<li class="">For TAP tables, how to specify that this table concerns this
body, or the sky ?</li></ol></div></div></blockquote>I think this is a bit more tricky than this, as a table may include data records concerning several planets of solar system bodies. <br class=""><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class=""><ol class="" start="3">
<li class="">How to handle the list of celestial bodies ? Do we have to
provide a list (mercury, venus, earth, moon, mars, io,...)
somewhere in the VO ?<br class=""></li></ol></div></div></blockquote><div>In the VO, not really (in STC, there is a list, but not complete). The reference should be the list maintained by the IAU list.</div><br class=""><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class=""><p class="">Reactions ? Suggestions ? Do we have time to discuss this point
during Paris Interop ?<br class=""></p></div></div></blockquote><div><br class=""></div>I think this is a very nice topic for Paris: it's overlapping with SSIG, Apps, DM, Registry and Semantics.</div><div><br class=""></div><div>Cheers</div><div>Baptiste<br class=""><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class=""><p class="">
Cheers<br class="">
Pierre Fernique<br class="">
</p><p class=""><br class="">
</p><p class=""><span id="cid:part1.5DF2A65D.3EF35516@astro.unistra.fr"><cgpjigkioblcbnll.png></span></p>
</div>
</div></blockquote></div><br class=""></div></body></html>