<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=""><div class="">Dear Mireille,</div><div class=""><br class=""></div>I need to complement Sonia’s and Marco’s feedback with a very similar issue<div class="">for the following fields, all declared as optional (with a MAN = NO) in the TABLE 5</div><div class="">but all having ‘principle’ set to 1 in TABLE 6:<br class=""><div class=""><div class=""><br class=""></div><div class="">ObsCore field name principle</div><div class=""><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><div style="margin: 0px; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">------------------- -------</span></div><div style="margin: 0px; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">dataproduct_subtype 1 </span></div><div style="margin: 0px; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">o_calib_status 1 </span></div><div style="margin: 0px; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">obs_creator_name 1 </span></div><div style="margin: 0px; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">obs_release_date 1 </span></div><div style="margin: 0px; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">obs_title 1 </span></div><div style="margin: 0px; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">s_pixel_scale 1 </span></div><div style="margin: 0px; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">target_class 1 </span></div><div style="margin: 0px; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">obs_creation_date 1 </span></div><div style="margin: 0px; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">publisher_id 1 </span></div><div style="margin: 0px; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">s_ucd 1 </span></div><div style="margin: 0px; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">s_unit 1 </span></div><div style="margin: 0px; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">s_resolution_max 1 </span></div><div style="margin: 0px; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">s_resolution_min 1 </span></div><div style="margin: 0px; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">em_ucd 1 </span></div><div style="margin: 0px; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">em_res_power_max 1 </span></div><div style="margin: 0px; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">em_res_power_min 1 </span></div><div style="margin: 0px; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">em_resolution 1 </span></div><div style="margin: 0px; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">o_unit 1</span></div><div style="margin: 0px; line-height: normal;" class=""><br class=""></div></div></div><div class=""><span style="font-variant-ligatures: no-common-ligatures" class="">Should not the principle field be set to 0 for all optional fields?</span></div><div class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><div class=""><span style="font-variant-ligatures: no-common-ligatures" class="">Many thanks,</span></div><div class=""><span style="font-variant-ligatures: no-common-ligatures" class="">Alberto</span></div><div class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 22 Aug 2017, at 11:24, Mireille Louys <<a href="mailto:mireille.louys@unistra.fr" class="">mireille.louys@unistra.fr</a>> wrote:</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="">
<font face="Times New Roman, Times, serif" class="">Hi </font><font face="Times New Roman, Times, serif" class=""><font face="Times New Roman,
Times, serif" class="">Sonia & </font>Marco, Hi all, <br class="">
</font><br class="">
<font face="Times New Roman, Times, serif" class="">Thanks for your feedback
in this precise implementation of the Obscore 1.1 specification. <br class="">
</font><br class="">
<font face="Times New Roman, Times, serif" class="">Apologies for these typos
and missing descriptions terms that went through our vigilance as
authors and editors. <br class="">
</font><font face="Times New Roman, Times, serif" class="">We are aware that
when a model offers many fields, many implementations are needed
to test all the fields precisely and extensively.</font><br class="">
<font face="Times New Roman, Times, serif" class=""><font face="Times New
Roman, Times, serif" class=""><br class="">
I have not experienced the errata process yet, but it seems
appropriate here.<br class="">
<br class="">
Cheers , Mireille.<br class="">
</font></font><p class=""><font face="Times New Roman, Times, serif" class=""><br class="">
</font></p>
<br class="">
<div class="moz-cite-prefix">Le 22/08/2017 à 10:29, Marco Molinaro a
écrit :<br class="">
</div>
<blockquote type="cite" cite="mid:CABiOC77z+Mfsu93ki5uJTif--uKbP1dPTzh6k5fALOniWv4YFA@mail.gmail.com" class="">
<div dir="ltr" class="">
<div class="">Dear DM,</div>
<div class="">working on ObsCore-1.1 in the development of a tool to try
to help administering that table we found a few discrepancies
in the REC text.</div>
<div class=""><br class="">
</div>
<div class="">1 - pol_states</div>
<div class="">This field is listed as mandatory in §3.2 (Table 1, page
21) but then, Appendix B page 42, in Table 5 the MANdatory
column says NO. After that, Table 6 on page 57 lists
pol_states again among the mandatory fields.</div>
<div class=""><br class="">
</div>
<div class="">This looks like simply a typo.</div>
<div class=""><br class="">
</div>
<div class="">2 - t_refpos</div>
<div class="">This field is listed in Table 5 (Appendix B) page 41 as an
optional one, but has no other entry in the specification,
e.g. it has no entry in Table 7 (Appendix C.2) so that no
Utype or UCD is defined for it.</div>
<div class=""><br class="">
</div>
<div class="">This one looks like a simple forgetfulness.</div>
<div class=""><br class="">
</div>
<div class="">3 - units for strings</div>
<div class="">Table 5 (pagg. 40-43) reports units for the various fields.
However it defines string-type fields to be unitless except
for s_region (no value is reported) and proposal_id (which is
set as unit=string).</div>
<div class=""><br class="">
</div>
<div class="">We think this is, again, only a minor typo since strings
are unitless (blank in VOUnits).</div>
<div class=""><br class="">
</div>
<div class="">Sorry for reporting this after ObsCore-1.1 reached REC.</div>
<div class="">How do you think we can fix this? Would an erratum (even a
single encompassing one) do?</div>
<div class=""><br class="">
</div>
<div class="">Cheers,</div>
<div class=""> Sonia & Marco</div>
<div class=""><br class="">
</div>
</div>
</blockquote>
<br class="">
<pre class="moz-signature" cols="72">--
--
Mireille Louys
CDS                                                 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>
</div>
</div></blockquote></div><br class=""></div></div></div></body></html>