<div dir="auto"><div>Huh? Principal, perhaps? <br><div class="gmail_extra"><br><div class="gmail_quote">On Sep 26, 2017 2:09 PM, "alberto micol" <<a href="mailto:amicol.ivoa@googlemail.com">amicol.ivoa@googlemail.com</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Dear Mireille,</div><div><br></div>I need to complement Sonia’s and Marco’s feedback with a very similar issue<div>for the following fields, all declared as optional (with a MAN = NO) in the TABLE 5</div><div>but all having ‘principle’ set to 1 in TABLE 6:<br><div><div><br></div><div>ObsCore field name principle</div><div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"><div style="margin:0px;line-height:normal"><span style="font-variant-ligatures:no-common-ligatures">------------------- -------</span></div><div style="margin:0px;line-height:normal"><span style="font-variant-ligatures:no-common-ligatures">dataproduct_subtype 1 </span></div><div style="margin:0px;line-height:normal"><span style="font-variant-ligatures:no-common-ligatures">o_calib_status 1 </span></div><div style="margin:0px;line-height:normal"><span style="font-variant-ligatures:no-common-ligatures">obs_creator_name 1 </span></div><div style="margin:0px;line-height:normal"><span style="font-variant-ligatures:no-common-ligatures">obs_release_date 1 </span></div><div style="margin:0px;line-height:normal"><span style="font-variant-ligatures:no-common-ligatures">obs_title 1 </span></div><div style="margin:0px;line-height:normal"><span style="font-variant-ligatures:no-common-ligatures">s_pixel_scale 1 </span></div><div style="margin:0px;line-height:normal"><span style="font-variant-ligatures:no-common-ligatures">target_class 1 </span></div><div style="margin:0px;line-height:normal"><span style="font-variant-ligatures:no-common-ligatures">obs_creation_date 1 </span></div><div style="margin:0px;line-height:normal"><span style="font-variant-ligatures:no-common-ligatures">publisher_id 1 </span></div><div style="margin:0px;line-height:normal"><span style="font-variant-ligatures:no-common-ligatures">s_ucd 1 </span></div><div style="margin:0px;line-height:normal"><span style="font-variant-ligatures:no-common-ligatures">s_unit 1 </span></div><div style="margin:0px;line-height:normal"><span style="font-variant-ligatures:no-common-ligatures">s_resolution_max 1 </span></div><div style="margin:0px;line-height:normal"><span style="font-variant-ligatures:no-common-ligatures">s_resolution_min 1 </span></div><div style="margin:0px;line-height:normal"><span style="font-variant-ligatures:no-common-ligatures">em_ucd 1 </span></div><div style="margin:0px;line-height:normal"><span style="font-variant-ligatures:no-common-ligatures">em_res_power_max 1 </span></div><div style="margin:0px;line-height:normal"><span style="font-variant-ligatures:no-common-ligatures">em_res_power_min 1 </span></div><div style="margin:0px;line-height:normal"><span style="font-variant-ligatures:no-common-ligatures">em_resolution 1 </span></div><div style="margin:0px;line-height:normal"><span style="font-variant-ligatures:no-common-ligatures">o_unit 1</span></div><div style="margin:0px;line-height:normal"><br></div></div></div><div><span style="font-variant-ligatures:no-common-ligatures">Should not the principle field be set to 0 for all optional fields?</span></div><div><span style="font-variant-ligatures:no-common-ligatures"><br></span></div><div><span style="font-variant-ligatures:no-common-ligatures">Many thanks,</span></div><div><span style="font-variant-ligatures:no-common-ligatures">Alberto</span></div><div class="elided-text"><div><span style="font-variant-ligatures:no-common-ligatures"><br></span></div><div><br><div><blockquote type="cite"><div>On 22 Aug 2017, at 11:24, Mireille Louys <<a href="mailto:mireille.louys@unistra.fr" target="_blank">mireille.louys@unistra.fr</a>> wrote:</div><br class="m_-955120785207286094Apple-interchange-newline"><div>
<div text="#000000" bgcolor="#FFFFFF">
<font face="Times New Roman, Times, serif">Hi </font><font face="Times New Roman, Times, serif"><font face="Times New Roman,
Times, serif">Sonia & </font>Marco, Hi all, <br>
</font><br>
<font face="Times New Roman, Times, serif">Thanks for your feedback
in this precise implementation of the Obscore 1.1 specification. <br>
</font><br>
<font face="Times New Roman, Times, serif">Apologies for these typos
and missing descriptions terms that went through our vigilance as
authors and editors. <br>
</font><font face="Times New Roman, Times, serif">We are aware that
when a model offers many fields, many implementations are needed
to test all the fields precisely and extensively.</font><br>
<font face="Times New Roman, Times, serif"><font face="Times New
Roman, Times, serif"><br>
I have not experienced the errata process yet, but it seems
appropriate here.<br>
<br>
Cheers , Mireille.<br>
</font></font><p><font face="Times New Roman, Times, serif"><br>
</font></p>
<br>
<div class="m_-955120785207286094moz-cite-prefix">Le 22/08/2017 à 10:29, Marco Molinaro a
écrit :<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Dear DM,</div>
<div>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><br>
</div>
<div>1 - pol_states</div>
<div>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><br>
</div>
<div>This looks like simply a typo.</div>
<div><br>
</div>
<div>2 - t_refpos</div>
<div>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><br>
</div>
<div>This one looks like a simple forgetfulness.</div>
<div><br>
</div>
<div>3 - units for strings</div>
<div>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><br>
</div>
<div>We think this is, again, only a minor typo since strings
are unitless (blank in VOUnits).</div>
<div><br>
</div>
<div>Sorry for reporting this after ObsCore-1.1 reached REC.</div>
<div>How do you think we can fix this? Would an erratum (even a
single encompassing one) do?</div>
<div><br>
</div>
<div>Cheers,</div>
<div> Sonia & Marco</div>
<div><br>
</div>
</div>
</blockquote>
<br>
<pre class="m_-955120785207286094moz-signature" cols="72">--
--
Mireille Louys
CDS Laboratoire Icube
Observatoire de Strasbourg Telecom Physique Strasbourg
11 rue de l'Université <a href="https://maps.google.com/?q=300,+Bd+Sebastien&entry=gmail&source=g">300, Bd Sebastien</a> Brandt CS 10413
F- 67000-STRASBOURG F-67412 ILLKIRCH Cedex
tel: <a href="tel:+33%203%2068%2085%2024%2034" value="+33368852434" target="_blank">+33 3 68 85 24 34</a></pre>
</div>
</div></blockquote></div><br></div></div></div></div></div></blockquote></div><br></div></div></div>