SSA v1.1 Erratum 2: Invalid UCDs required in specification 1.0Author: Mireille Louys Date last changed: 2022-01-17 Date accepted: - Github Issue: SSA Issue #1RationaleAppendix D: SSA Data Model Summary, PDF page 64, lists the data model elements supported by the SSA specification with Utypes and UCDs. | |||||||||||||||||
Changed: | |||||||||||||||||
< < | Some of the UCDs proposed lead to ambiguous interpretation and do not follow the combination rules of the UCD specification. Specifically, instr.fov must be secondary. Hence, the UCDs for the fields with utypes | ||||||||||||||||
> > | Some of the UCDs proposed lead to ambiguous interpretation and do not follow the combination rules of the UCD specification. Specifically, instr.fov must be secondary. Hence, the UCDs for the fields with utypes | ||||||||||||||||
| |||||||||||||||||
Changed: | |||||||||||||||||
< < |
| ||||||||||||||||
> > |
| ||||||||||||||||
Deleted: | |||||||||||||||||
< < | |||||||||||||||||
as prescribed by SSAP 1.1 are invalid and need to be repaired.
This erratum provides valid UCDs, which not only have proper semantics but also enable UCD-aware clients to determine the nature of the fields if they do not know the SSAP data model.
Erratum ContentThis erratum makes the following changes in the table P. 64:
Impact AssessmentSSAP clients do not identify fields by UCDs and hence are unaffected by this change. Clients relying on UCDs to determine how to treat individual columns will now be able to gain some basic understanding of the affected columns, which they could not before (as the UCDs were invalid and hence meaningless). Most importantly, valid SSAP services will raise fewer errors in UCD validation. | |||||||||||||||||
Changed: | |||||||||||||||||
< < | Topic_action | ||||||||||||||||
> > | |||||||||||||||||
Deleted: | |||||||||||||||||
< < |
UCDList EN-1.4 defines /instr.fov/ as
S | instr.fov | Field of view
This definition is fuzzy, and can be clarified and replaced by
|