<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>hi all, <br>
</p>
<p>here is my suggestion for the term <b><i>catalog</i></b> as it
has been used so far in the VO</p>
<p><i>catalog</i>:<br>
</p>
<p>a set of physical quantities recorded from an
observing/simulation process and measured/computed for a set of
individual astronomical objects (sources).<br>
Each catalog entry corresponds to one individual source object. <br>
The usual representation is a table with columns figuring the
quantities and rows representing an entry.</p>
<p><i>source list:</i></p>
<p>a catalog where entries are derived from one or a restricted set
or data products : single image, multiband image, radio or
hyperspectral cube, eventlist for instance. <br>
</p>
<p>Typically, ObsTAP can handle source list as dataproducts, with
coverage inherited from the progenitor dataset.</p>
<p>On the contrary very large catalogs like survey, hips catalogs
with coverage='allsky' are managed within archives/datacenters and
searched on with keywords from the astronomical semantics, like
type of objects, regime, instrument types, survey name, etc.</p>
<p>Here is an interface example: <a moz-do-not-send="true"
href="http://cdsarc.unistra.fr/viz-bin/cat">http://cdsarc.unistra.fr/viz-bin/cat</a><br>
</p>
<p>Are there server applications distributing such all sky catalogs
with Obscore as one single dataproduct? <br>
</p>
<p>best , Mireille<br>
</p>
<pre class="moz-signature" cols="72">--
--
Mireille Louys, MCF (Associate Professor)
CDS IPSEO, Images, Laboratoire Icube
Observatoire de Strasbourg Telecom Physique Strasbourg
11 rue de l'Université 300, Bd Sebastien Brandt CS 10413
F- 67000-STRASBOURG F-67412 ILLKIRCH Cedex
Tel: +33 3 68 85 24 34</pre>
</body>
</html>