Difference: ObsCore-1_1-Erratum-1 (1 vs. 14)

Revision 142019-05-24 - MireilleLouys

 
META TOPICPARENT name="ObsCoreDMvOnedotOne"

ObsCore 1.1: Erratum 1

Author: DM WG

Date last changed: 2019-05-10 Update of errata page after tcg review . L. Michel , M.Louys.

Previous change : 2018-12-19

Date accepted:

Rationale

This erratum corrects a few issues noted in the ObsCore-1.1 document .

  1. Table 6 page 56 and table 7 page 58, list invalid UCD strings for certain elements (invalid with respect to the UCD1+ standard) in obstap columns definition.
  • obs_publisher_did: UCD = meta.ref.uri;meta.curation
    • The problem being that meta.curation is a primary word (P) being used as secondary. meta.ref.uri is indifferent (Q)
  • publisher_id: UCD = meta.ref.uri;meta.curation
    • Same as obs_publisher_did
  • o_stat_error UCD = stat.error;phot.flux
    • The issue here being that the addition of phot.flux is too specific for the usage.
Changed:
<
<
  • dataproduct_type and dataproduct_subtype : UCD = meta.id;class
    • The problem being that meta.id;class is incorrect UCD. It should be written meta.code.class
    • This must be corrected in the example presented in C.3
>
>
  • dataproduct_type and dataproduct_subtype : UCD = meta.id in the REC ObsCore1.1
    • The problem is that meta.id is more appropriate for an identifier while here we consider a class of products ; meta.code.class should be preferred
    • The example serialisation described in section C.3 had a bad meta.id;class UCD for dataproductype .
Added:
>
>
    • This must be corrected in the example presented in C.3
 

Erratum Content

Invalid UCDs in Table 6 page 56 and table 7 page 58: TAP_SCHEMA.columns

Original Wording (Invalid UCDs)
  • obs_publisher_did: UCD = meta.ref.uri;meta.curation
  • publisher_id: UCD = meta.ref.uri;meta.curation
  • o_stat_error: UCD = stat.error;phot.flux
Changed:
<
<
  • dataproduct_type: UCD = meta.id;class
  • dataproduct_subtype : UCD = meta.id;class
>
>
  • dataproduct_type: UCD = meta.id
  • dataproduct_subtype : UCD = meta.id
 
New Wording (correct UCDs)
  • obs_publisher_did : UCD = meta.ref.ivoid
  • publisher_id: UCD = meta.ref.ivoid
  • o_stat_error: UCD = stat.error
  • dataproduct_type: UCD = meta.code.class
  • dataproduct_subtype: UCD = meta.code.class
Changed:
<
<
C.3 example using dataproduct_type has been changed accordingly
>
>
C.3 example using dataproduct_type has been changed accordingly.
 

Impact Assessment

  • ObsCore clients normally use column names or perhaps utypes to identify data model members. The change of the UCDs proposed here should not impact them.
  • Clients not aware of ObsCore will profit from the proposed change; for obs_publisher_did and publisher_id, they will no longer produce diagnostics for invalid UCDs, and for o_stat_error they will not be mislead any more.
Changed:
<
<
  • This change may rise Taplint warnings.
>
>
  • This change may rise Taplint warning messages.
 

Notes

  1. The proposed changes are in the errata proposed document attached here REC-ObsCore-v1.1-20190510_errata.pdf
  2. It has been proposed, in this erratum, to extend the use of obs_publisher_did to others IDs than ivoids (DOI e.g.).
    Answer: Changing the role of an identifier is out of the scope of an errata. This issue could be discussed for Obscore 1.2.

<--  
-->

META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20180222_errata.pdf" attr="h" comment="Errata on Obscore 1.1" date="1519312955" name="REC-ObsCore-v1.1-20180222_errata.pdf" path="REC-ObsCore-v1.1-20180222_errata.pdf" size="1791997" user="MireilleLouys" version="2"
META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20181130_errata.pdf" attr="" comment="Obscore 1.1 errata included" date="1546862971" name="REC-ObsCore-v1.1-20181130_errata.pdf" path="REC-ObsCore-v1.1-20181130_errata.pdf" size="1183373" user="MireilleLouys" version="2"
META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20190510_errata.pdf" attr="" comment="Update for the REC - document including errata changes -M.Louys" date="1557494528" name="REC-ObsCore-v1.1-20190510_errata.pdf" path="REC-ObsCore-v1.1-20190510_errata.pdf" size="1186699" user="MireilleLouys" version="1"
META TOPICMOVED by="GiuliaIafrate" date="1542471442" from="IVOA.ObscoreErrata" to="IVOA.ObsCore-1_1-Erratum-1"

Revision 132019-05-10 - MireilleLouys

 
META TOPICPARENT name="ObsCoreDMvOnedotOne"

ObsCore 1.1: Erratum 1

Author: DM WG

Changed:
<
<
Date last changed: 2018-12-19
>
>
Date last changed: 2019-05-10 Update of errata page after tcg review . L. Michel , M.Louys.
 
Added:
>
>
Previous change : 2018-12-19
 Date accepted:

Rationale

This erratum corrects a few issues noted in the ObsCore-1.1 document .

  1. Table 6 page 56 and table 7 page 58, list invalid UCD strings for certain elements (invalid with respect to the UCD1+ standard) in obstap columns definition.
  • obs_publisher_did: UCD = meta.ref.uri;meta.curation
    • The problem being that meta.curation is a primary word (P) being used as secondary. meta.ref.uri is indifferent (Q)
  • publisher_id: UCD = meta.ref.uri;meta.curation
    • Same as obs_publisher_did
  • o_stat_error UCD = stat.error;phot.flux
    • The issue here being that the addition of phot.flux is too specific for the usage.
Added:
>
>
  • dataproduct_type and dataproduct_subtype : UCD = meta.id;class
    • The problem being that meta.id;class is incorrect UCD. It should be written meta.code.class
    • This must be corrected in the example presented in C.3
 

Erratum Content

Invalid UCDs in Table 6 page 56 and table 7 page 58: TAP_SCHEMA.columns

Original Wording (Invalid UCDs)
  • obs_publisher_did: UCD = meta.ref.uri;meta.curation
  • publisher_id: UCD = meta.ref.uri;meta.curation
Changed:
<
<
  • o_stat_error UCD = stat.error;phot.flux
>
>
  • o_stat_error: UCD = stat.error;phot.flux
Added:
>
>
  • dataproduct_type: UCD = meta.id;class
  • dataproduct_subtype : UCD = meta.id;class
 
New Wording (correct UCDs)
  • obs_publisher_did : UCD = meta.ref.ivoid
  • publisher_id: UCD = meta.ref.ivoid
  • o_stat_error: UCD = stat.error
Added:
>
>
  • dataproduct_type: UCD = meta.code.class
  • dataproduct_subtype: UCD = meta.code.class
C.3 example using dataproduct_type has been changed accordingly
 

Impact Assessment

  • ObsCore clients normally use column names or perhaps utypes to identify data model members. The change of the UCDs proposed here should not impact them.
  • Clients not aware of ObsCore will profit from the proposed change; for obs_publisher_did and publisher_id, they will no longer produce diagnostics for invalid UCDs, and for o_stat_error they will not be mislead any more.
  • This change may rise Taplint warnings.

Notes

Changed:
<
<
  1. The proposed changes are in the errata proposed document attached here https://wiki.ivoa.net/internal/IVOA/ObsCore-1_1-Erratum-1/REC-ObsCore-v1.1-20181130_errata.pdf
>
>
  1. The proposed changes are in the errata proposed document attached here REC-ObsCore-v1.1-20190510_errata.pdf
 
  1. It has been proposed, in this erratum, to extend the use of obs_publisher_did to others IDs than ivoids (DOI e.g.).
    Answer: Changing the role of an identifier is out of the scope of an errata. This issue could be discussed for Obscore 1.2.

<--  
-->

META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20180222_errata.pdf" attr="h" comment="Errata on Obscore 1.1" date="1519312955" name="REC-ObsCore-v1.1-20180222_errata.pdf" path="REC-ObsCore-v1.1-20180222_errata.pdf" size="1791997" user="MireilleLouys" version="2"
META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20181130_errata.pdf" attr="" comment="Obscore 1.1 errata included" date="1546862971" name="REC-ObsCore-v1.1-20181130_errata.pdf" path="REC-ObsCore-v1.1-20181130_errata.pdf" size="1183373" user="MireilleLouys" version="2"
Added:
>
>
META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20190510_errata.pdf" attr="" comment="Update for the REC - document including errata changes -M.Louys" date="1557494528" name="REC-ObsCore-v1.1-20190510_errata.pdf" path="REC-ObsCore-v1.1-20190510_errata.pdf" size="1186699" user="MireilleLouys" version="1"
 
META TOPICMOVED by="GiuliaIafrate" date="1542471442" from="IVOA.ObscoreErrata" to="IVOA.ObsCore-1_1-Erratum-1"

Revision 122019-05-10 - LaurentMichel

 
META TOPICPARENT name="ObsCoreDMvOnedotOne"

ObsCore 1.1: Erratum 1

Author: DM WG

Date last changed: 2018-12-19

Date accepted:

Rationale

This erratum corrects a few issues noted in the ObsCore-1.1 document .

  1. Table 6 page 56 and table 7 page 58, list invalid UCD strings for certain elements (invalid with respect to the UCD1+ standard) in obstap columns definition.
Added:
>
>
  • obs_publisher_did: UCD = meta.ref.uri;meta.curation
    • The problem being that meta.curation is a primary word (P) being used as secondary. meta.ref.uri is indifferent (Q)
  • publisher_id: UCD = meta.ref.uri;meta.curation
    • Same as obs_publisher_did
  • o_stat_error UCD = stat.error;phot.flux
    • The issue here being that the addition of phot.flux is too specific for the usage.
 

Erratum Content

Invalid UCDs in Table 6 page 56 and table 7 page 58: TAP_SCHEMA.columns

Original Wording (Invalid UCDs)
Changed:
<
<
  • obs_publisher_did: UCD = meta.ref.uri;meta.curation
    • The problem being that meta.curation is a primary word (P) being used as secondary. meta.ref.uri is indifferent (Q)
  • publisher_id: UCD = meta.ref.uri;meta.curation
>
>
  • obs_publisher_did: UCD = meta.ref.uri;meta.curation
  • publisher_id: UCD = meta.ref.uri;meta.curation
  • o_stat_error UCD = stat.error;phot.flux
Deleted:
<
<
    • Same as obs_publisher_did
  • o_stat_error UCD = stat.error;phot.flux
    • The issue here being that the addition of phot.flux is too specific for the usage.
 
New Wording (correct UCDs)
  • obs_publisher_did : UCD = meta.ref.ivoid
  • publisher_id: UCD = meta.ref.ivoid
  • o_stat_error: UCD = stat.error

Impact Assessment

  • ObsCore clients normally use column names or perhaps utypes to identify data model members. The change of the UCDs proposed here should not impact them.
  • Clients not aware of ObsCore will profit from the proposed change; for obs_publisher_did and publisher_id, they will no longer produce diagnostics for invalid UCDs, and for o_stat_error they will not be mislead any more.
  • This change may rise Taplint warnings.

Notes

  1. The proposed changes are in the errata proposed document attached here https://wiki.ivoa.net/internal/IVOA/ObsCore-1_1-Erratum-1/REC-ObsCore-v1.1-20181130_errata.pdf
  2. It has been proposed, in this erratum, to extend the use of obs_publisher_did to others IDs than ivoids (DOI e.g.).
    Answer: Changing the role of an identifier is out of the scope of an errata. This issue could be discussed for Obscore 1.2.

<--  
-->

META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20180222_errata.pdf" attr="h" comment="Errata on Obscore 1.1" date="1519312955" name="REC-ObsCore-v1.1-20180222_errata.pdf" path="REC-ObsCore-v1.1-20180222_errata.pdf" size="1791997" user="MireilleLouys" version="2"
META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20181130_errata.pdf" attr="" comment="Obscore 1.1 errata included" date="1546862971" name="REC-ObsCore-v1.1-20181130_errata.pdf" path="REC-ObsCore-v1.1-20181130_errata.pdf" size="1183373" user="MireilleLouys" version="2"
META TOPICMOVED by="GiuliaIafrate" date="1542471442" from="IVOA.ObscoreErrata" to="IVOA.ObsCore-1_1-Erratum-1"

Revision 112019-01-23 - LaurentMichel

 
META TOPICPARENT name="ObsCoreDMvOnedotOne"

ObsCore 1.1: Erratum 1

Author: DM WG

Date last changed: 2018-12-19

Date accepted:

Rationale

This erratum corrects a few issues noted in the ObsCore-1.1 document .

  1. Table 6 page 56 and table 7 page 58, list invalid UCD strings for certain elements (invalid with respect to the UCD1+ standard) in obstap columns definition.

Erratum Content

Invalid UCDs in Table 6 page 56 and table 7 page 58: TAP_SCHEMA.columns

Original Wording (Invalid UCDs)
  • obs_publisher_did: UCD = meta.ref.uri;meta.curation
    • The problem being that meta.curation is a primary word (P) being used as secondary. meta.ref.uri is indifferent (Q)
  • publisher_id: UCD = meta.ref.uri;meta.curation
    • Same as obs_publisher_did
  • o_stat_error UCD = stat.error;phot.flux
    • The issue here being that the addition of phot.flux is too specific for the usage.
New Wording (correct UCDs)
  • obs_publisher_did : UCD = meta.ref.ivoid
  • publisher_id: UCD = meta.ref.ivoid
  • o_stat_error: UCD = stat.error

Impact Assessment

  • ObsCore clients normally use column names or perhaps utypes to identify data model members. The change of the UCDs proposed here should not impact them.
  • Clients not aware of ObsCore will profit from the proposed change; for obs_publisher_did and publisher_id, they will no longer produce diagnostics for invalid UCDs, and for o_stat_error they will not be mislead any more.
  • This change may rise Taplint warnings.

Notes

  1. The proposed changes are in the errata proposed document attached here https://wiki.ivoa.net/internal/IVOA/ObsCore-1_1-Erratum-1/REC-ObsCore-v1.1-20181130_errata.pdf
Added:
>
>
  1. It has been proposed, in this erratum, to extend the use of obs_publisher_did to others IDs than ivoids (DOI e.g.).
    Answer: Changing the role of an identifier is out of the scope of an errata. This issue could be discussed for Obscore 1.2.

 

<--  
-->

META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20180222_errata.pdf" attr="h" comment="Errata on Obscore 1.1" date="1519312955" name="REC-ObsCore-v1.1-20180222_errata.pdf" path="REC-ObsCore-v1.1-20180222_errata.pdf" size="1791997" user="MireilleLouys" version="2"
META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20181130_errata.pdf" attr="" comment="Obscore 1.1 errata included" date="1546862971" name="REC-ObsCore-v1.1-20181130_errata.pdf" path="REC-ObsCore-v1.1-20181130_errata.pdf" size="1183373" user="MireilleLouys" version="2"
META TOPICMOVED by="GiuliaIafrate" date="1542471442" from="IVOA.ObscoreErrata" to="IVOA.ObsCore-1_1-Erratum-1"

Revision 102019-01-07 - MireilleLouys

 
META TOPICPARENT name="ObsCoreDMvOnedotOne"

ObsCore 1.1: Erratum 1

Author: DM WG

Date last changed: 2018-12-19

Date accepted:

Rationale

This erratum corrects a few issues noted in the ObsCore-1.1 document .

  1. Table 6 page 56 and table 7 page 58, list invalid UCD strings for certain elements (invalid with respect to the UCD1+ standard) in obstap columns definition.

Erratum Content

Invalid UCDs in Table 6 page 56 and table 7 page 58: TAP_SCHEMA.columns

Original Wording (Invalid UCDs)
  • obs_publisher_did: UCD = meta.ref.uri;meta.curation
    • The problem being that meta.curation is a primary word (P) being used as secondary. meta.ref.uri is indifferent (Q)
  • publisher_id: UCD = meta.ref.uri;meta.curation
    • Same as obs_publisher_did
  • o_stat_error UCD = stat.error;phot.flux
    • The issue here being that the addition of phot.flux is too specific for the usage.
New Wording (correct UCDs)
  • obs_publisher_did : UCD = meta.ref.ivoid
  • publisher_id: UCD = meta.ref.ivoid
  • o_stat_error: UCD = stat.error

Impact Assessment

  • ObsCore clients normally use column names or perhaps utypes to identify data model members. The change of the UCDs proposed here should not impact them.
  • Clients not aware of ObsCore will profit from the proposed change; for obs_publisher_did and publisher_id, they will no longer produce diagnostics for invalid UCDs, and for o_stat_error they will not be mislead any more.
  • This change may rise Taplint warnings.

Notes

Changed:
<
<
  1. 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
>
>
  1. The proposed changes are in the errata proposed document attached here https://wiki.ivoa.net/internal/IVOA/ObsCore-1_1-Erratum-1/REC-ObsCore-v1.1-20181130_errata.pdf
 

<--  
-->

META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20180222_errata.pdf" attr="h" comment="Errata on Obscore 1.1" date="1519312955" name="REC-ObsCore-v1.1-20180222_errata.pdf" path="REC-ObsCore-v1.1-20180222_errata.pdf" size="1791997" user="MireilleLouys" version="2"
Changed:
<
<
META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20181130_errata.pdf" attr="" comment="Obscore 1.1 errata" date="1543588844" name="REC-ObsCore-v1.1-20181130_errata.pdf" path="REC-ObsCore-v1.1-20181130_errata.pdf" size="1133826" user="LaurentMichel" version="1"
>
>
META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20181130_errata.pdf" attr="" comment="Obscore 1.1 errata included" date="1546862971" name="REC-ObsCore-v1.1-20181130_errata.pdf" path="REC-ObsCore-v1.1-20181130_errata.pdf" size="1183373" user="MireilleLouys" version="2"
 
META TOPICMOVED by="GiuliaIafrate" date="1542471442" from="IVOA.ObscoreErrata" to="IVOA.ObsCore-1_1-Erratum-1"

Revision 92018-12-19 - LaurentMichel

 
META TOPICPARENT name="ObsCoreDMvOnedotOne"

ObsCore 1.1: Erratum 1

Author: DM WG

Date last changed: 2018-12-19

Date accepted:

Rationale

This erratum corrects a few issues noted in the ObsCore-1.1 document .

Changed:
<
<
  1. Table 6, page 56, lists invalid UCD strings for certain elements (invalid with respect to the UCD1+ standard) in obstap columns definition.
>
>
  1. Table 6 page 56 and table 7 page 58, list invalid UCD strings for certain elements (invalid with respect to the UCD1+ standard) in obstap columns definition.
 

Erratum Content

Changed:
<
<

Invalid UCDs in Table 6 page 56: TAP_SCHEMA.columns

>
>

Invalid UCDs in Table 6 page 56 and table 7 page 58: TAP_SCHEMA.columns

 
Original Wording (Invalid UCDs)
  • obs_publisher_did: UCD = meta.ref.uri;meta.curation
    • The problem being that meta.curation is a primary word (P) being used as secondary. meta.ref.uri is indifferent (Q)
  • publisher_id: UCD = meta.ref.uri;meta.curation
    • Same as obs_publisher_did
  • o_stat_error UCD = stat.error;phot.flux
    • The issue here being that the addition of phot.flux is too specific for the usage.
New Wording (correct UCDs)
  • obs_publisher_did : UCD = meta.ref.ivoid
  • publisher_id: UCD = meta.ref.ivoid
  • o_stat_error: UCD = stat.error

Impact Assessment

  • ObsCore clients normally use column names or perhaps utypes to identify data model members. The change of the UCDs proposed here should not impact them.
  • Clients not aware of ObsCore will profit from the proposed change; for obs_publisher_did and publisher_id, they will no longer produce diagnostics for invalid UCDs, and for o_stat_error they will not be mislead any more.
  • This change may rise Taplint warnings.

Notes

  1. 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

<--  
-->

META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20180222_errata.pdf" attr="h" comment="Errata on Obscore 1.1" date="1519312955" name="REC-ObsCore-v1.1-20180222_errata.pdf" path="REC-ObsCore-v1.1-20180222_errata.pdf" size="1791997" user="MireilleLouys" version="2"
META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20181130_errata.pdf" attr="" comment="Obscore 1.1 errata" date="1543588844" name="REC-ObsCore-v1.1-20181130_errata.pdf" path="REC-ObsCore-v1.1-20181130_errata.pdf" size="1133826" user="LaurentMichel" version="1"
META TOPICMOVED by="GiuliaIafrate" date="1542471442" from="IVOA.ObscoreErrata" to="IVOA.ObsCore-1_1-Erratum-1"

Revision 82018-12-19 - LaurentMichel

 
META TOPICPARENT name="ObsCoreDMvOnedotOne"

ObsCore 1.1: Erratum 1

Author: DM WG

Changed:
<
<
Date last changed: 2018-11-18
>
>
Date last changed: 2018-12-19
  Date accepted:

Rationale

Changed:
<
<
This erratum corrects a few issues noted in the ObsCore-1.1 document . Since most are small typo level items, it we include multiple items in one erratum.
>
>
This erratum corrects a few issues noted in the ObsCore-1.1 document .
 
Changed:
<
<
  1. Table 6 lists invalid UCD strings for certain elements (invalid with respect to the UCD1+ standard) in obstap columns definition.
>
>
  1. Table 6, page 56, lists invalid UCD strings for certain elements (invalid with respect to the UCD1+ standard) in obstap columns definition.
Deleted:
<
<
  1. Implementation feedback from Marco Molinaro, see http://mail.ivoa.net/pipermail/dm/2017-August/005604.html
 

Erratum Content

Changed:
<
<

Invalid UCDs in Table 6

page 56, Table 6: TAP_SCHEMA.columns

  • Invalid UCDs
    • obs_publisher_did - meta.ref.uri;meta.curation
      • The problem being that 'meta.curation' is a primary word (P) being used as secondary. 'meta.ref.uri' is indifferent (Q)
    • publisher_id - meta.ref.uri;meta.curation
      • same as obs_publisher_did
    • o_stat_error - stat.error;phot.flux
      • the issue here being that the addition of 'phot.flux' is too specific for the usage.
  • Correct UCDs
    • obs_publisher_did - meta.ref.ivoid
>
>

Invalid UCDs in Table 6 page 56: TAP_SCHEMA.columns

Original Wording (Invalid UCDs)
  • obs_publisher_did: UCD = meta.ref.uri;meta.curation
    • The problem being that meta.curation is a primary word (P) being used as secondary. meta.ref.uri is indifferent (Q)
  • publisher_id: UCD = meta.ref.uri;meta.curation
    • Same as obs_publisher_did
  • o_stat_error UCD = stat.error;phot.flux
    • The issue here being that the addition of phot.flux is too specific for the usage.
New Wording (correct UCDs)
  • obs_publisher_did : UCD = meta.ref.ivoid
  • publisher_id: UCD = meta.ref.ivoid
  • o_stat_error: UCD = stat.error
Deleted:
<
<
      • 'meta.curation' cannot be preserved because it is a primary word (P) being used as secondary. 'meta.ref.ivoid' is indifferent (Q)
      • ivoid already refers to a curation context
    • publisher_id - meta.ref.ivoid
      • Same as above
    • o_stat_error - stat.error

pol_states

  • Incorrect text
    • 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.
  • correction
    • Correct setting in Appendix B: Table 5 on page 42, to show pol_states as MAN=YES

t_refpos

  • issue
    • 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. This one looks like a simple forgetfulness.
  • answer
    • as we are considering Time series to be handled by ObsCore for discovery, this reference for the time system has to be re worked. Feedback from the dm list is welcome for this
  • 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.
    • t_refpos entry has been removed from table5

units for strings

  • issue
    • 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).
  • correction
    • correct both proposal_id s_region entries in Table 5 to reflect unit=unitless

missing facility_name

  • issue
    • facility_name missing in table 5
  • correction
    • added as mandatory field

Inconsistency in 'principal' settings

  • issue
    • The following fields, all declared as optional (with a MAN = NO) in the TABLE 5, have ‘principal’ set to 1 in TABLE 6. It should be 0 for optional fields.
      • dataproduct_subtype
      • o_calib_status
      • obs_creator_name
      • obs_release_date
      • obs_title
      • s_pixel_scale
      • target_class
      • obs_creation_date
      • publisher_id
      • s_ucd
      • s_unit
      • s_resolution_max
      • s_resolution_min
      • em_ucd
      • em_res_power_max
      • em_res_power_min
      • em_resolution
      • o_unit
  • correction
    • The meaning of the 'principal' column is explained in C2 page 55. Its is not equivalent to mandatory status of the field. All mandatory fields are principal and some optional fields can be principal either (table7).
    • The definition of the 'principal' column has been updated in P55.
 

Impact Assessment

Changed:
<
<
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.
>
>
  • ObsCore clients normally use column names or perhaps utypes to identify data model members. The change of the UCDs proposed here should not impact them.
  • Clients not aware of ObsCore will profit from the proposed change; for obs_publisher_did and publisher_id, they will no longer produce diagnostics for invalid UCDs, and for o_stat_error they will not be mislead any more.
Added:
>
>
  • This change may rise Taplint warnings.
 

Notes

Deleted:
<
<
  1. I do not see 'meta.ref.ivoaid' in the UCD list ( 'meta.ref.ivoaid' has been replaced with 'meta.ref.ivoid')
 
  1. 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
Deleted:
<
<
  1. In the above, it is not clear that all errata have been incorporated, needs review by WG.
 

<--  
-->

META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20180222_errata.pdf" attr="h" comment="Errata on Obscore 1.1" date="1519312955" name="REC-ObsCore-v1.1-20180222_errata.pdf" path="REC-ObsCore-v1.1-20180222_errata.pdf" size="1791997" user="MireilleLouys" version="2"
META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20181130_errata.pdf" attr="" comment="Obscore 1.1 errata" date="1543588844" name="REC-ObsCore-v1.1-20181130_errata.pdf" path="REC-ObsCore-v1.1-20181130_errata.pdf" size="1133826" user="LaurentMichel" version="1"
META TOPICMOVED by="GiuliaIafrate" date="1542471442" from="IVOA.ObscoreErrata" to="IVOA.ObsCore-1_1-Erratum-1"

Revision 72018-12-19 - LaurentMichel

 
META TOPICPARENT name="ObsCoreDMvOnedotOne"

ObsCore 1.1: Erratum 1

Author: DM WG

Date last changed: 2018-11-18

Date accepted:

Rationale

This erratum corrects a few issues noted in the ObsCore-1.1 document . Since most are small typo level items, it we include multiple items in one erratum.

  1. Table 6 lists invalid UCD strings for certain elements (invalid with respect to the UCD1+ standard) in obstap columns definition.
  2. Implementation feedback from Marco Molinaro, see http://mail.ivoa.net/pipermail/dm/2017-August/005604.html

Erratum Content

Invalid UCDs in Table 6

page 56, Table 6: TAP_SCHEMA.columns

  • Invalid UCDs
    • obs_publisher_did - meta.ref.uri;meta.curation
      • The problem being that 'meta.curation' is a primary word (P) being used as secondary. 'meta.ref.uri' is indifferent (Q)
    • publisher_id - meta.ref.uri;meta.curation
      • same as obs_publisher_did
    • o_stat_error - stat.error;phot.flux
      • the issue here being that the addition of 'phot.flux' is too specific for the usage.
  • Correct UCDs
    • obs_publisher_did - meta.ref.ivoid
      • 'meta.curation' cannot be preserved because it is a primary word (P) being used as secondary. 'meta.ref.ivoid' is indifferent (Q)
      • ivoid already refers to a curation context
    • publisher_id - meta.ref.ivoid
      • Same as above
    • o_stat_error - stat.error

pol_states

  • Incorrect text
    • 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.
  • correction
    • Correct setting in Appendix B: Table 5 on page 42, to show pol_states as MAN=YES

t_refpos

  • issue
    • 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. This one looks like a simple forgetfulness.
  • answer
    • as we are considering Time series to be handled by ObsCore for discovery, this reference for the time system has to be re worked. Feedback from the dm list is welcome for this
  • 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.
    • t_refpos entry has been removed from table5

units for strings

  • issue
    • 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).
  • correction
    • correct both proposal_id s_region entries in Table 5 to reflect unit=unitless

missing facility_name

  • issue
    • facility_name missing in table 5
  • correction
    • added as mandatory field

Inconsistency in 'principal' settings

  • issue
    • The following fields, all declared as optional (with a MAN = NO) in the TABLE 5, have ‘principal’ set to 1 in TABLE 6. It should be 0 for optional fields.
      • dataproduct_subtype
      • o_calib_status
      • obs_creator_name
      • obs_release_date
      • obs_title
      • s_pixel_scale
      • target_class
      • obs_creation_date
      • publisher_id
      • s_ucd
      • s_unit
      • s_resolution_max
      • s_resolution_min
      • em_ucd
      • em_res_power_max
      • em_res_power_min
      • em_resolution
      • o_unit
  • correction
    • The meaning of the 'principal' column is explained in C2 page 55. Its is not equivalent to mandatory status of the field. All mandatory fields are principal and some optional fields can be principal either (table7).
    • The definition of the 'principal' column has been updated in P55.

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

Changed:
<
<
  1. I do not see 'meta.ref.ivoaid' in the UCD list..
>
>
  1. I do not see 'meta.ref.ivoaid' in the UCD list ( 'meta.ref.ivoaid' has been replaced with 'meta.ref.ivoid')
 
  1. 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
  2. In the above, it is not clear that all errata have been incorporated, needs review by WG.

<--  
-->

META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20180222_errata.pdf" attr="h" comment="Errata on Obscore 1.1" date="1519312955" name="REC-ObsCore-v1.1-20180222_errata.pdf" path="REC-ObsCore-v1.1-20180222_errata.pdf" size="1791997" user="MireilleLouys" version="2"
META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20181130_errata.pdf" attr="" comment="Obscore 1.1 errata" date="1543588844" name="REC-ObsCore-v1.1-20181130_errata.pdf" path="REC-ObsCore-v1.1-20181130_errata.pdf" size="1133826" user="LaurentMichel" version="1"
META TOPICMOVED by="GiuliaIafrate" date="1542471442" from="IVOA.ObscoreErrata" to="IVOA.ObsCore-1_1-Erratum-1"

Revision 62018-12-12 - MarkusDemleitner

 
META TOPICPARENT name="ObsCoreDMvOnedotOne"

ObsCore 1.1: Erratum 1

Author: DM WG

Date last changed: 2018-11-18

Date accepted:

Rationale

This erratum corrects a few issues noted in the ObsCore-1.1 document . Since most are small typo level items, it we include multiple items in one erratum.

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

Erratum Content

Invalid UCDs in Table 6

page 56, Table 6: TAP_SCHEMA.columns

  • Invalid UCDs
    • obs_publisher_did - meta.ref.uri;meta.curation
      • The problem being that 'meta.curation' is a primary word (P) being used as secondary. 'meta.ref.uri' is indifferent (Q)
    • publisher_id - meta.ref.uri;meta.curation
      • same as obs_publisher_did
    • o_stat_error - stat.error;phot.flux
      • the issue here being that the addition of 'phot.flux' is too specific for the usage.
  • Correct UCDs
    • obs_publisher_did - meta.ref.ivoid
      • 'meta.curation' cannot be preserved because it is a primary word (P) being used as secondary. 'meta.ref.ivoid' is indifferent (Q)
      • ivoid already refers to a curation context
    • publisher_id - meta.ref.ivoid
      • Same as above
    • o_stat_error - stat.error

pol_states

  • Incorrect text
    • 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.
  • correction
    • Correct setting in Appendix B: Table 5 on page 42, to show pol_states as MAN=YES

t_refpos

  • issue
    • 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. This one looks like a simple forgetfulness.
  • answer
    • as we are considering Time series to be handled by ObsCore for discovery, this reference for the time system has to be re worked. Feedback from the dm list is welcome for this
  • 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.
    • t_refpos entry has been removed from table5

units for strings

  • issue
    • 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).
  • correction
    • correct both proposal_id s_region entries in Table 5 to reflect unit=unitless

missing facility_name

  • issue
    • facility_name missing in table 5
  • correction
    • added as mandatory field

Inconsistency in 'principal' settings

  • issue
    • The following fields, all declared as optional (with a MAN = NO) in the TABLE 5, have ‘principal’ set to 1 in TABLE 6. It should be 0 for optional fields.
      • dataproduct_subtype
      • o_calib_status
      • obs_creator_name
      • obs_release_date
      • obs_title
      • s_pixel_scale
      • target_class
      • obs_creation_date
      • publisher_id
      • s_ucd
      • s_unit
      • s_resolution_max
      • s_resolution_min
      • em_ucd
      • em_res_power_max
      • em_res_power_min
      • em_resolution
      • o_unit
  • correction
    • The meaning of the 'principal' column is explained in C2 page 55. Its is not equivalent to mandatory status of the field. All mandatory fields are principal and some optional fields can be principal either (table7).
    • The definition of the 'principal' column has been updated in P55.

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. I do not see 'meta.ref.ivoaid' in the UCD list..
  2. 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
  3. In the above, it is not clear that all errata have been incorporated, needs review by WG.

<--  
-->

META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20180222_errata.pdf" attr="h" comment="Errata on Obscore 1.1" date="1519312955" name="REC-ObsCore-v1.1-20180222_errata.pdf" path="REC-ObsCore-v1.1-20180222_errata.pdf" size="1791997" user="MireilleLouys" version="2"
META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20181130_errata.pdf" attr="" comment="Obscore 1.1 errata" date="1543588844" name="REC-ObsCore-v1.1-20181130_errata.pdf" path="REC-ObsCore-v1.1-20181130_errata.pdf" size="1133826" user="LaurentMichel" version="1"
META TOPICMOVED by="GiuliaIafrate" date="1542471442" from="IVOA.ObscoreErrata" to="IVOA.ObsCore-1_1-Erratum-1"

Revision 52018-11-30 - LaurentMichel

 
META TOPICPARENT name="ObsCoreDMvOnedotOne"

ObsCore 1.1: Erratum 1

Author: DM WG

Date last changed: 2018-11-18

Date accepted:

Rationale

This erratum corrects a few issues noted in the ObsCore-1.1 document . Since most are small typo level items, it we include multiple items in one erratum.

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

Erratum Content

Invalid UCDs in Table 6

page 56, Table 6: TAP_SCHEMA.columns

Changed:
<
<
  • Invalid UCDs
    • obs_publisher_did - meta.ref.uri;meta.curation
>
>
  • Invalid UCDs
    • obs_publisher_did - meta.ref.uri;meta.curation
 
      • The problem being that 'meta.curation' is a primary word (P) being used as secondary. 'meta.ref.uri' is indifferent (Q)
Changed:
<
<
    • publisher_id - meta.ref.uri;meta.curation
>
>
    • publisher_id - meta.ref.uri;meta.curation
 
      • same as obs_publisher_did
Changed:
<
<
    • o_stat_error - stat.error;phot.flux
>
>
    • o_stat_error - stat.error;phot.flux
 
      • the issue here being that the addition of 'phot.flux' is too specific for the usage.
Changed:
<
<
  • Correct UCDs
    • obs_publisher_did - meta.ref.ivoid;meta.curation
    • publisher_id - meta.ref.ivoaid;meta.curation
    • o_stat_error - stat.error
>
>
  • Correct UCDs
    • obs_publisher_did - meta.ref.ivoid
      • 'meta.curation' cannot be preserved because it is a primary word (P) being used as secondary. 'meta.ref.ivoid' is indifferent (Q)
Added:
>
>
      • ivoid already refers to a curation context
    • publisher_id - meta.ref.ivoid
      • Same as above
    • o_stat_error - stat.error
 

pol_states

Changed:
<
<
  • Incorrect text
>
>
  • Incorrect text
 
    • 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.
Changed:
<
<
  • correction
>
>
  • correction
 
    • Correct setting in Appendix B: Table 5 on page 42, to show pol_states as MAN=YES

t_refpos

Changed:
<
<
  • issue
>
>
  • issue
 
    • 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. This one looks like a simple forgetfulness.
Changed:
<
<
  • answer
>
>
  • answer
 
    • as we are considering Time series to be handled by ObsCore for discovery, this reference for the time system has to be re worked. Feedback from the dm list is welcome for this
Changed:
<
<
  • correction
>
>
  • 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.
Changed:
<
<
>
>
    • t_refpos entry has been removed from table5
 

units for strings

Changed:
<
<
  • issue
    • 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).
  • correction
    • correct proposal_id entry in Table 5 to reflect unit=unitless
>
>
  • issue
    • 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).
  • correction
    • correct both proposal_id s_region entries in Table 5 to reflect unit=unitless
Added:
>
>

missing facility_name

  • issue
    • facility_name missing in table 5
  • correction
    • added as mandatory field
 

Inconsistency in 'principal' settings

Changed:
<
<
  • issue
    • The following fields, all declared as optional (with a MAN = NO) in the TABLE 5, have ‘principal’ set to 1 in TABLE 6. It should be 0 for optional fields.
>
>
  • issue
    • The following fields, all declared as optional (with a MAN = NO) in the TABLE 5, have ‘principal’ set to 1 in TABLE 6. It should be 0 for optional fields.
 
      • dataproduct_subtype
      • o_calib_status
      • obs_creator_name
      • obs_release_date
      • obs_title
      • s_pixel_scale
      • target_class
      • obs_creation_date
      • publisher_id
      • s_ucd
      • s_unit
      • s_resolution_max
      • s_resolution_min
      • em_ucd
      • em_res_power_max
      • em_res_power_min
      • em_resolution
      • o_unit
Changed:
<
<
  • correction
    • Update Table 6 principal value to 0 for each of the above entries.

Impact Assessment

>
>
  • correction
    • The meaning of the 'principal' column is explained in C2 page 55. Its is not equivalent to mandatory status of the field. All mandatory fields are principal and some optional fields can be principal either (table7).
    • The definition of the 'principal' column has been updated in P55.
Added:
>
>

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. I do not see 'meta.ref.ivoaid' in the UCD list..
  2. 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
  3. In the above, it is not clear that all errata have been incorporated, needs review by WG.

<--  
-->
Changed:
<
<
META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20180222_errata.pdf" attr="" comment="Errata on Obscore 1.1" date="1519312955" name="REC-ObsCore-v1.1-20180222_errata.pdf" path="REC-ObsCore-v1.1-20180222_errata.pdf" size="1791997" user="MireilleLouys" version="2"
>
>
META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20180222_errata.pdf" attr="h" comment="Errata on Obscore 1.1" date="1519312955" name="REC-ObsCore-v1.1-20180222_errata.pdf" path="REC-ObsCore-v1.1-20180222_errata.pdf" size="1791997" user="MireilleLouys" version="2"
Added:
>
>
META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20181130_errata.pdf" attr="" comment="Obscore 1.1 errata" date="1543588844" name="REC-ObsCore-v1.1-20181130_errata.pdf" path="REC-ObsCore-v1.1-20181130_errata.pdf" size="1133826" user="LaurentMichel" version="1"
 
META TOPICMOVED by="GiuliaIafrate" date="1542471442" from="IVOA.ObscoreErrata" to="IVOA.ObsCore-1_1-Erratum-1"

Revision 42018-11-18 - MarkCresitelloDittmar

 
META TOPICPARENT name="ObsCoreDMvOnedotOne"
Changed:
<
<

Obscore v1.1 Errata on REC-ObsCore-v1.1-20170509.pdf

>
>

ObsCore 1.1: Erratum 1

 
Changed:
<
<
Updates of the UCD tags in obstap columns definition
>
>
Author: DM WG
 
Changed:
<
<
Rationale :
>
>
Date last changed: 2018-11-18
 
Changed:
<
<
  • Invalid UCDs/ checked by Taplint
UCD in obs_publisher_did and publisher_did meta.ref.uri;meta.curation not valid / checked in taplint
>
>
Date accepted:

Rationale

 
Changed:
<
<
Following UCD updates we propose meta.ref.ivoid instead
>
>
This erratum corrects a few issues noted in the ObsCore-1.1 document . Since most are small typo level items, it we include multiple items in one erratum.
 
Changed:
<
<
o_stat_error was tagged with UCD stat.error;phot.flux too restrictive --> changed to stat.error
>
>
  1. Table 6 lists invalid UCD strings for certain elements (invalid with respect to the UCD1+ standard) in obstap columns definition.
Added:
>
>
  1. Implementation feedback from Marco Molinary, see http://mail.ivoa.net/pipermail/dm/2017-August/005604.html
 
Changed:
<
<
  • Marco Molinaro feedback from implementation
see http://mail.ivoa.net/pipermail/dm/2017-August/005604.html
>
>

Erratum Content

Invalid UCDs in Table 6

Deleted:
<
<
  1. - pol_states
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.
 
Changed:
<
<
>
>
page 56, Table 6: TAP_SCHEMA.columns
Added:
>
>
  • Invalid UCDs
    • obs_publisher_did - meta.ref.uri;meta.curation
      • The problem being that 'meta.curation' is a primary word (P) being used as secondary. 'meta.ref.uri' is indifferent (Q)
    • publisher_id - meta.ref.uri;meta.curation
      • same as obs_publisher_did
    • o_stat_error - stat.error;phot.flux
      • the issue here being that the addition of 'phot.flux' is too specific for the usage.
  • Correct UCDs
    • obs_publisher_did - meta.ref.ivoid;meta.curation
    • publisher_id - meta.ref.ivoaid;meta.curation
    • o_stat_error - stat.error

pol_states

  • Incorrect text
    • 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.
  • correction
    • Correct setting in Appendix B: Table 5 on page 42, to show pol_states as MAN=YES

t_refpos

  • issue
    • 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. This one looks like a simple forgetfulness.
  • answer
    • as we are considering Time series to be handled by ObsCore for discovery, this reference for the time system has to be re worked. Feedback from the dm list is welcome for this
  • 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

  • issue
    • 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).
  • correction
    • correct proposal_id entry in Table 5 to reflect unit=unitless

Inconsistency in 'principal' settings

  • issue
    • The following fields, all declared as optional (with a MAN = NO) in the TABLE 5, have ‘principal’ set to 1 in TABLE 6. It should be 0 for optional fields.
      • dataproduct_subtype
      • o_calib_status
      • obs_creator_name
      • obs_release_date
      • obs_title
      • s_pixel_scale
      • target_class
      • obs_creation_date
      • publisher_id
      • s_ucd
      • s_unit
      • s_resolution_max
      • s_resolution_min
      • em_ucd
      • em_res_power_max
      • em_res_power_min
      • em_resolution
      • o_unit
  • 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. I do not see 'meta.ref.ivoaid' in the UCD list..
  2. 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
  3. In the above, it is not clear that all errata have been incorporated, needs review by WG.
 
<--  
-->

META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20180222_errata.pdf" attr="" comment="Errata on Obscore 1.1" date="1519312955" name="REC-ObsCore-v1.1-20180222_errata.pdf" path="REC-ObsCore-v1.1-20180222_errata.pdf" size="1791997" user="MireilleLouys" version="2"
META TOPICMOVED by="GiuliaIafrate" date="1542471442" from="IVOA.ObscoreErrata" to="IVOA.ObsCore-1_1-Erratum-1"

Revision 32018-11-17 - GiuliaIafrate

 
META TOPICPARENT name="ObsCoreDMvOnedotOne"

Obscore v1.1 Errata on REC-ObsCore-v1.1-20170509.pdf

Updates of the UCD tags in obstap columns definition

Rationale :

  • Invalid UCDs/ checked by Taplint
UCD in obs_publisher_did and publisher_did meta.ref.uri;meta.curation not valid / checked in taplint

Following UCD updates we propose meta.ref.ivoid instead

o_stat_error was tagged with UCD stat.error;phot.flux too restrictive --> changed to stat.error

  • Marco Molinaro feedback from implementation
see http://mail.ivoa.net/pipermail/dm/2017-August/005604.html
  1. - pol_states
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.
Changed:
<
<
>
>
 
<--  
-->

META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20180222_errata.pdf" attr="" comment="Errata on Obscore 1.1" date="1519312955" name="REC-ObsCore-v1.1-20180222_errata.pdf" path="REC-ObsCore-v1.1-20180222_errata.pdf" size="1791997" user="MireilleLouys" version="2"
Added:
>
>
META TOPICMOVED by="GiuliaIafrate" date="1542471442" from="IVOA.ObscoreErrata" to="IVOA.ObsCore-1_1-Erratum-1"
 

Revision 22018-11-16 - MarkCresitelloDittmar

Changed:
<
<
META TOPICPARENT name="ObscCore1dot1RFC"
>
>
META TOPICPARENT name="ObsCoreDMvOnedotOne"
 

Obscore v1.1 Errata on REC-ObsCore-v1.1-20170509.pdf

Updates of the UCD tags in obstap columns definition

Rationale :

  • Invalid UCDs/ checked by Taplint
UCD in obs_publisher_did and publisher_did meta.ref.uri;meta.curation not valid / checked in taplint

Following UCD updates we propose meta.ref.ivoid instead

o_stat_error was tagged with UCD stat.error;phot.flux too restrictive --> changed to stat.error

  • Marco Molinaro feedback from implementation
see http://mail.ivoa.net/pipermail/dm/2017-August/005604.html
  1. - pol_states
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.

<--  
-->

META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20180222_errata.pdf" attr="" comment="Errata on Obscore 1.1" date="1519312955" name="REC-ObsCore-v1.1-20180222_errata.pdf" path="REC-ObsCore-v1.1-20180222_errata.pdf" size="1791997" user="MireilleLouys" version="2"

Revision 12018-02-22 - MireilleLouys

 
META TOPICPARENT name="ObscCore1dot1RFC"

Obscore v1.1 Errata on REC-ObsCore-v1.1-20170509.pdf

Updates of the UCD tags in obstap columns definition

Rationale :

  • Invalid UCDs/ checked by Taplint
UCD in obs_publisher_did and publisher_did meta.ref.uri;meta.curation not valid / checked in taplint

Following UCD updates we propose meta.ref.ivoid instead

o_stat_error was tagged with UCD stat.error;phot.flux too restrictive --> changed to stat.error

  • Marco Molinaro feedback from implementation
see http://mail.ivoa.net/pipermail/dm/2017-August/005604.html
  1. - pol_states
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.

<--  
-->

META FILEATTACHMENT attachment="REC-ObsCore-v1.1-20180222_errata.pdf" attr="" comment="Errata on Obscore 1.1" date="1519312955" name="REC-ObsCore-v1.1-20180222_errata.pdf" path="REC-ObsCore-v1.1-20180222_errata.pdf" size="1791997" user="MireilleLouys" version="2"
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback