ObsCore 1.1: Erratum 2Author: DM WG Date last changed: 2018-11-18 Date accepted:RationaleThis 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 - 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. >> 2 - t_refpos 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. >> 3 - units for strings 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). Author answers about t_refpos :
Erratum Contentpol_statesOriginal Wording
New Wording
t_refposOriginal Wording
New Wording
units for stringsOriginal Wording
New Wording
missing _facility_nameOriginal Wording
New Wording
Inconsistency in 'principal' settingsOriginal Wording
New Wording
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Impact Assessment
Notes
* Set ALLOWTOPICRENAME =<span class="WYSIWYG_PROTECTED"> TWikiAdminGroup</span> --> | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
ObsCore 1.1: Erratum 2Author: DM WG Date last changed: 2018-11-18 Date accepted:RationaleThis 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 - 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. >> 2 - t_refpos 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. >> 3 - units for strings 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). Author answers about t_refpos :
Erratum Contentpol_statesOriginal Wording | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
New Wording
t_refposOriginal Wording
New Wording
units for stringsOriginal Wording
New Wording
missing _facility_nameOriginal Wording
New Wording
Inconsistency in 'principal' settingsOriginal Wording
New Wording
Impact Assessment
Notes
* Set ALLOWTOPICRENAME =<span class="WYSIWYG_PROTECTED"> TWikiAdminGroup</span> -->
|
ObsCore 1.1: Erratum 2Author: DM WG Date last changed: 2018-11-18 Date accepted:RationaleThis 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 - 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. >> 2 - t_refpos 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. >> 3 - units for strings 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). Author answers about t_refpos :
Erratum Contentpol_statesOriginal Wording
New Wording
t_refposOriginal Wording
New Wording
units for stringsOriginal Wording
New Wording
missing _facility_nameOriginal Wording
New Wording
Inconsistency in 'principal' settingsOriginal Wording
New Wording
Impact Assessment
Notes | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
* Set ALLOWTOPICRENAME =<span class="WYSIWYG_PROTECTED"> TWikiAdminGroup</span> --> | |||||||
Changed: | ||||||||
< < | <!-- * Set ALLOWTOPICRENAME =<span class="WYSIWYG_PROTECTED"><span class="WYSIWYG_PROTECTED"><span class="WYSIWYG_PROTECTED"> TWikiAdminGroup</span></span></span> --> | |||||||
> > |
| |||||||
ObsCore 1.1: Erratum 2Author: DM WG Date last changed: 2018-11-18 Date accepted:RationaleThis 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 - 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. >> 2 - t_refpos 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. >> 3 - units for strings 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). Author answers about t_refpos :
Erratum Contentpol_statesOriginal Wording
New Wording
t_refposOriginal Wording
New Wording
units for stringsOriginal Wording
New Wording
missing _facility_nameOriginal Wording
New Wording
Inconsistency in 'principal' settingsOriginal Wording
New Wording
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. | |||||||
> > |
| |||||||
Deleted: | ||||||||
< < | Clients using t_refpos are non longer compliant with the spec. This column must be now considered as an Obscore extension. Implementation not using pol_states must add this column to be compliant | |||||||
Notes
| ||||||||
Deleted: | ||||||||
< < |
| |||||||
<!-- * Set ALLOWTOPICRENAME =<span class="WYSIWYG_PROTECTED"><span class="WYSIWYG_PROTECTED"><span class="WYSIWYG_PROTECTED"> TWikiAdminGroup</span></span></span> --> |
ObsCore 1.1: Erratum 2Author: DM WG Date last changed: 2018-11-18 Date accepted:RationaleThis 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: | ||||||||
< < |
| |||||||
> > |
| |||||||
Added: | ||||||||
> > | cite: >> 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. >> 2 - t_refpos 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. >> 3 - units for strings 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). | |||||||
Added: | ||||||||
> > | Author answers about t_refpos :
| |||||||
Erratum Contentpol_states | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > | Original Wording
| |||||||
Added: | ||||||||
> > | New Wording
| |||||||
t_refpos | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > | Original Wording
New Wording
| |||||||
Deleted: | ||||||||
< < |
| |||||||
units for strings | ||||||||
Added: | ||||||||
> > | Original Wording
New Wording
| |||||||
Changed: | ||||||||
< < |
missing facility_name | |||||||
> > | missing _facility_nameOriginal Wording
New Wording
| |||||||
Deleted: | ||||||||
< < |
| |||||||
Inconsistency in 'principal' settings | ||||||||
Added: | ||||||||
> > | Original Wording
| |||||||
Changed: | ||||||||
< < |
| |||||||
> > | New Wording
| |||||||
Deleted: | ||||||||
< < |
| |||||||
Impact AssessmentImplementations 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. | ||||||||
Added: | ||||||||
> > | Clients using t_refpos are non longer compliant with the spec. This column must be now considered as an Obscore extension. Implementation not using pol_states must add this column to be compliant | |||||||
Notes
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
<!-- * Set ALLOWTOPICRENAME =<span class="WYSIWYG_PROTECTED"><span class="WYSIWYG_PROTECTED"><span class="WYSIWYG_PROTECTED"> TWikiAdminGroup</span></span></span> --> |
ObsCore 1.1: Erratum 2Author: DM WG Date last changed: 2018-11-18 Date accepted:RationaleThis 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.
Erratum Contentpol_states
t_refpos
units for strings
missing facility_name
Inconsistency in 'principal' settings
Impact AssessmentImplementations 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
* Set ALLOWTOPICRENAME =<span class="WYSIWYG_PROTECTED"><span class="WYSIWYG_PROTECTED"><span class="WYSIWYG_PROTECTED"> TWikiAdminGroup</span></span></span> --> |