(r4) ObsCore-1_1-Erratum-1 < IVOA

IVOA Web>IvoaDataModel>ObsDMCoreComponents>ObsCoreDMvOnedotOne>ObsCore-1_1-Erratum-1 (revision 4) (raw view)~~EditAttach~~
---+ ObsCore 1.1: Erratum 1

Author: DM WG

Date last changed: 2018-11-18

Date accepted:
---++ <span style="background-color: transparent;">Rationale</span>

<span style="background-color: transparent;">This erratum corrects a few issues noted in the </span> [[http://www.ivoa.net/documents/ObsCore/20170509/REC-ObsCore-v1.1-20170509.pdf][ObsCore-1.1 document ]]. Since most are small typo level items, it we include multiple items in one erratum.

   1 <span style="background-color: transparent;">Table 6 lists </span><span style="background-color: transparent;">invalid UCD strings for certain elements (invalid with respect to the UCD1+ standard) </span><span style="background-color: transparent;">in obstap columns definition.</span>
   1 <span style="background-color: transparent;">Implementation feedback from Marco Molinary, see http://mail.ivoa.net/pipermail/dm/2017-August/005604.html</span>

---++ Erratum Content
---++++ Invalid UCDs in Table 6

page 56, Table 6: TAP_SCHEMA.columns
   * Invalid UCDs
      * <strong>obs_publisher_did</strong> - <span style="background-color: transparent;">meta.ref.uri;meta.curation</span>
         * The problem being that 'meta.curation' is a primary word (P) being used as secondary. 'meta.ref.uri' is indifferent (Q)
      * <strong>publisher_id</strong> - <span style="background-color: transparent;">meta.ref.uri;meta.curation</span>
         * <span style="background-color: transparent;">same as obs_publisher_did</span>
      * <strong style="font-weight: bold;">o_stat_error</strong> - <span style="background-color: transparent;">stat.error;phot.flux</span>
         * the issue here being that the addition of 'phot.flux' is too specific for the usage.
   * <span style="background-color: transparent;">Correct UCDs</span>
      * <strong>obs_publisher_did</strong><span style="background-color: transparent;"> - meta.ref.ivoid;meta.curation</span>
      * <strong>publisher_id</strong><span style="background-color: transparent;"> - meta.ref.ivoaid;meta.curation</span>
      * <strong>o_stat_error</strong><span style="background-color: transparent;"> - stat.error</span>
---++++ pol_states

   * <span style="background-color: transparent;">Incorrect text</span>
      * <span style="background-color: transparent;">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. This looks like simply a typo.</span>
   * correction
      * Correct setting in Appendix B: Table 5 on page 42, to show pol_states as MAN=YES
---++++ t_refpos

   * <span style="background-color: transparent;">issue</span>
      * <span style="background-color: transparent;">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. </span><span style="background-color: transparent;">This one looks like a simple forgetfulness.</span>
   * <span style="background-color: transparent;">answer</span>
      * <span style="background-color: transparent;">as we are considering Time series to be handled by ObsCore for discovery, this reference for the time system has to be re worked. </span><span style="background-color: transparent;">Feedback from the dm list is welcome for this</span>
   * correction
      * It seems this is a placeholder for future expansion of ObsCore, it seems appropriate to remove this item from the Table 5, and restore it when the full specification can be provided in an update to the REC.

---++++ units for strings

   * <span style="background-color: transparent;">issue</span>
      * <span style="background-color: transparent;">Table 5 (pages 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).</span>
   * correction
      * correct proposal_id entry in Table 5 to reflect unit=unitless
---++++ Inconsistency in 'principal' settings

   * <span style="background-color: transparent;">issue</span>
      * <span style="background-color: transparent;">The following fields, all declared as optional (with a MAN = NO) in the TABLE 5, </span><span style="background-color: transparent;">have &lsquo;principal&rsquo; set to 1 in TABLE 6. It should be 0 for optional fields.</span>
         * <span style="background-color: transparent;">dataproduct_subtype</span>
         * <span style="background-color: transparent;">o_calib_status</span>
         * <span style="background-color: transparent;">obs_creator_name</span>
         * <span style="background-color: transparent;">obs_release_date</span>
         * <span style="background-color: transparent;">obs_title</span>
         * <span style="background-color: transparent;">s_pixel_scale</span>
         * <span style="background-color: transparent;">target_class</span>
         * <span style="background-color: transparent;">obs_creation_date</span>
         * <span style="background-color: transparent;">publisher_id</span>
         * <span style="background-color: transparent;">s_ucd</span>
         * <span style="background-color: transparent;">s_unit</span>
         * <span style="background-color: transparent;">s_resolution_max</span>
         * <span style="background-color: transparent;">s_resolution_min</span>
         * <span style="background-color: transparent;">em_ucd</span>
         * <span style="background-color: transparent;">em_res_power_max</span>
         * <span style="background-color: transparent;">em_res_power_min</span>
         * <span style="background-color: transparent;">em_resolution</span>
         * <span style="background-color: transparent;">o_unit</span>
   * correction
      * Update Table 6 principal value to 0 for each of the above entries.
---++ Impact Assessment 

Implementations which follow the ObsCore specification for these UDS are compliant with the model spec, but produce a validation error by taplint which validates the UCD value against the UCD specification.
---++ Notes

   1 <span style="background-color: transparent;">I do not see 'meta.ref.ivoaid' in the UCD list.. </span>
   1 <span style="background-color: transparent;">The proposed changes are in the errata proposed document attached here http://wiki.ivoa.net/internal/IVOA/ObsCore-1_1-Erratum-1/REC-ObsCore-v1.1-20180222_errata.pdf</span>
   1 <span style="background-color: transparent;">In the above, it is not clear that all errata have been incorporated, needs review by WG.</span>
<span style="color: #0000ff;"><span style="caret-color: #0000ff;"><span style="text-decoration: underline;"> </span></span></span>

<!--
      * Set ALLOWTOPICRENAME =<span class="WYSIWYG_PROTECTED"><span class="WYSIWYG_PROTECTED"><span class="WYSIWYG_PROTECTED"> IVOA.TWikiAdminGroup</span></span></span>
-->
Attachments
Topic attachments
I	Attachment	History	Action	Size	Date	Who	Comment
pdf	REC-ObsCore-v1.1-20180222_errata.pdf	r2 r1	manage	1750.0 K	2018-02-22 - 15:22	MireilleLouys	Errata on Obscore 1.1
Topic revision: r4 - 2018-11-18 - MarkCresitelloDittmar
IVOA
Log in or Register
IVOA.net
Wiki Home
WebChanges
WebTopicList
WebStatistics
Twiki Meta & Help
IVOA
Know
Main
Sandbox
TWiki
TWiki intro
TWiki tutorial
User registration
Notify me
Working Groups
Interest Groups
Time Domain
Committees
Stds&Procs
www.ivoa.net
Documents
Events
Members
XML Schema