<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hello, <br>
<br>
I agree we should update the definition of these fields in the
various specs , but I believe the problem is more complex than that.<br>
<br>
We did tackle this issue also on the semantics list , if you allow
me to point to a previous email <br>
<a moz-do-not-send="true"
href="http://mail.ivoa.net/pipermail/semantics/2022-February/002973.html"
class="moz-txt-link-freetext">http://mail.ivoa.net/pipermail/semantics/2022-February/002973.html</a>
.<br>
<br>
There has been some work about describing instruments, facilities ,
observatories , and relations between these metadata .<br>
This is a topic important for data providers, documentalists and
librarians who feed and check the data in the archives.<br>
<br>
There is no unique identifier for Instruments or Telescopes or
associations of telescopes, etc. today.<br>
Some space telescopes are called observatory (HST,...), or as in
your list, some are identified by different names .<br>
<br>
Ideally , all the models you are citing would like a uniq string as
a name for facility and instrument.<br>
if we use names, we will have to define name resolvers to handle
synonyms .<br>
Baptiste Cecconi and Laura Bischop will show some work in this
direction tomorrow at the semantics session.<br>
<br>
In a recent discussion we wanted also to clarify better by adding an
Organization column, which designates the organisation in charge of
the telescope.<br>
see the usefull example ZTF example, as proposed by Mathew .<br>
Having the organization name helps also to disentangle between
various synonyms, or fuzzy names filled for telescope, <br>
as some observatory sites may host telescopes from different
organizations.<br>
<br>
how can we proceed to go forward with the facility/instrument
updates in the ivoa specifications?<br>
<br>
Should we have a Dal/semantics/registry running meeting in the near
future? next month ? <br>
or a focus meeting on this specially with interested people from
each WG?<br>
<br>
thanks for follow up on the topic, <br>
cheers, Mireille<br>
<br>
<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">Le 27/04/2022 à 18:57, Tamara Civera a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:efe2dcb2-d9a4-e831-342b-c5d40b6616f6@cefca.es">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<p>Dear DAL, Registry,<br>
<br>
I am writing to you due to the definitions of the terms/fields
"facility" and "instrument" used in the different protocols
Obscore, SIAP v 2.0 and VoDataService. I have found that the
current ones can cause confusion, especially the "facility" term
(I send attached a "facility_name" list from different
Observatories Obscore services and in some, this field contains
the observatory name, in other the telescope name,...). So I
propose to clarify and unify them in these protocols.<br>
<br>
Current "Facility" definition according to the different VO
protocols documentation:</p>
<ul>
<li>Obscore "Facility" definition: <br>
</li>
<ul>
<li>"B7.1 The Facility class codes information about the
observatory or facility used to collect the data."</li>
<li>"C.3
<FIELDname="facility_name"datatype="char"ucd="meta.id;instr.tel"utype="obscore:Provenance.ObsConfig.Facility.name"xtype="adql:VARCHAR"arraysize="128*"><DESCRIPTION>telescope
name</DESCRIPTION></FIELD>"</li>
</ul>
<li>SIAP 2.0 "Facility" definition: "2.1.12 The FACILITY
parameter is a string-valued parameter that specifies the name
of the facility (usually telescope) where the data was
acquired. The value is compared with the facility_name from
the ObsCore [7] data model"</li>
<li>VoDataService "Facility" definition: "3.1.1 The observatory
or facility used to collect the data contained or managed by
this resource."<br>
</li>
</ul>
<p><br>
Current "Instrument" definition according to the different VO
protocols documentation:<br>
<br>
</p>
<ul>
<li>Obscore "Instrument" definition: "B7.2 The name of the
instrument used for the acquisition of the observation."</li>
<li>SIAP 2.0 "Instrument" definition: "2.1.13 The INSTRUMENT
parameter is a string-valued parameter that specifies the name
of the instrument with which the data was acquired. The value
is compared with the instrument_name from the ObsCore [7] data
model."</li>
<li>VoDataService "Instrument" definition: "3.1.1 The instrument
used to collect the data contain or managed by a resource."<br>
</li>
</ul>
<p>After discussing this topic with Markus Demleitner in the IVOA
Interoperability Meeting, we have thought these possible
definitions for facility and instrument:<br>
<br>
"Facility" should contain the name of the device that collected
the messenger particles (as opposed to the detector, which is in
"instrument"). In the optical, this would usually designate a
telescope, in the radio, it would be a dish or an array, for
space missions, usually the whole probe.<br>
<br>
"Instrument" should contain the name of the device used for
analysing and detecting the messenger particles. Instances of
such devices would include cameras, spectrographs, or particle
detectors.<br>
</p>
<p>Thanks,<br>
<br>
Tamara Civera</p>
<div class="moz-signature">-- <br>
<title></title>
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<meta http-equiv="content-style-type" content="text/css">
<style type="text/css">#signature {
color:#1f497d;
font-family: Calibri, sans-serif;
margin-top: 15px;
}#signature strong {
font-size: 12pt;
}#signature .cargo {
font-size: 10pt;
margin: 15px;
}#info {
margin-top: 15px;
font-size: 12pt;
font-family: Tahoma, sans-serif;
}#info ul {
list-style-type: none;
font-size: 8pt;
}#info .label {
color:#1f497d;
}#legal {
font-family: Arial, sans-serif;
font-size: 7pt;
}</style>
<div id="signature"> Tamara Civera Lorenzo<br>
<span class="cargo">Scientific Database and Web Access
Engineer</span> </div>
<div id="info">
<table>
<tbody>
<tr>
<td> <img src="cid:part1.0saQYmvE.sK12NUj1@unistra.fr"
alt="Logotipo CEFCA" class=""> </td>
<td> <strong>Centro de Estudios de Física del Cosmos de
Aragón</strong>
<ul>
<li>Plaza San Juan nº 1, piso 2º</li>
<li>44001 Teruel</li>
<li><span class="label">Tfno:</span> +34978221266 -
<span class="label">Ext: 1116</span> </li>
<li><span class="label">Fax:</span> +34978602334 </li>
<li><span class="label">Email:</span> <a
href="mailto:tcivera@cefca.es"
moz-do-not-send="true"
class="moz-txt-link-freetext">tcivera@cefca.es</a></li>
<li><span class="label">Url:</span> <a
href="http://www.cefca.es"
moz-do-not-send="true"
class="moz-txt-link-freetext">http://www.cefca.es</a></li>
</ul>
</td>
</tr>
</tbody>
</table>
</div>
<div id="legal"> Este correo electrónico y, en su
caso, cualquier archivo adjunto al mismo, contiene información
de carácter confidencial exclusivamente dirigida a
su destinatario. Queda prohibida su divulgación, copia o
distribución a terceros sin la previa autorización escrita
de nuestra entidad. En el caso de haber recibido este correo
electrónico por error, por favor, elimínelo de inmediato
y notifique esta circunstancia al remitente. En conformidad
con lo establecido en las normativas vigentes de Protección
de Datos a nivel nacional y europeo, le informamos que en la
Fundación CEFCA tenemos un interés legítimo para tratar sus
datos de contacto con la finalidad de informarle de nuestras
actividades y gestionar sus peticiones. Sus datos no serán
cedidos a terceros, y los conservaremos sólo mientras
sea necesario para el mantenimiento de nuestra relación o
la gestión de su solicitud. Puede ejercer sus derechos de
acceso, rectificación y supresión de sus datos, así como los
derechos de limitación y oposición a su tratamiento con
fines promocionales, escribiendo a <a
class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:rgpd@cefca.es" moz-do-not-send="true">rgpd@cefca.es</a>.
También puede dirigirse a nuestro Delegado de Protección
de Datos para cualquier consulta relacionada con nuestra
política de privacidad, escribiendo a <a
class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:dpd@cefca.es" moz-do-not-send="true">dpd@cefca.es</a>
.
<hr> This email and, when appropriate, any file attached to
it, contains confidential information exclusively addressed to
its recipient. It is forbidden the disclosure, copying or
distribution of this email to third parties without the prior
written authorization of our entity. Should you have received
this email by mistake, please delete it immediately and notify
the sender of this circumstance. According to the provisions
of current Data Protection regulations at national and
European level, we inform you that at CEFCA we have a
legitimate interest to process your contact data in order to
inform you of our activities and manage your requests. Your
data will not be transferred to third parties, and we will
keep it only as long as it is necessary for the maintenance of
our relationship or the management of your request. You can
exercise your rights of access, rectification and deletion of
your data, as well as the rights of limitation and opposition
to its treatment for promotional purposes, by writing to <a
class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:rgpd@cefca.es" moz-do-not-send="true">rgpd@cefca.es</a>.
You can also contact our Data Protection Officer for any query
related to our privacy policy, writing to <a
class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:dpd@cefca.es" moz-do-not-send="true">dpd@cefca.es</a>
. </div>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
--
Mireille Louys, MCF (Associate Professor)
Centre de données 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>