SSA v1.1 Erratum 4: Make coverage optional
Author: James Dempsey
Date last changed: 2023-12-04
Date accepted: 2024-08-28
Github Issue:
SSA Issue #8
Rationale
SSA 1.1 sec 4.2.5.10 states MANdatory coverage information (Char.SpatialAxis.Coverage.Location.Value + 2 others), but they are missing from the example in Appendix A. Theoretical services cannot provide coverage information so these columns should be made optional to support theoretical services.
Erratum Content
In section 4.2.5.10, add the following text at the end of the introductory sentence.
Where coverage information is
available, such as in observational services, the columns Char.SpatialAxis.Coverage.Location.Value,
Char.SpatialAxis.Coverage.Bounds.Extent,
Char.TimeAxis.Coverage.Location.Value,
Char.SpectralAxis.Coverage.Location.Value, and Char.SpectralAxis.Coverage.Bounds.Extent should be provided.
However, this component is optional to support theoretical services and other services which do not have coverage information.
and in the table in that section change the value in the Req column from MAN to REC for the following rows:
UTYPE |
Description |
Req |
Default |
Char.SpatialAxis.Coverage.Location.Value |
Observed position, e.g., RA DEC |
REC |
|
Char.SpatialAxis.Coverage.Bounds.Extent |
Aperture angular diameter, deg |
REC |
|
Char.TimeAxis.Coverage.Location.Value |
Midpoint of exposure (MJD) |
REC |
|
Char.SpectralAxis.Coverage.Location.Value |
Midpoint of Spectral coord range |
REC |
|
Char.SpectralAxis.Coverage.Bounds.Extent |
Width of spectrum in meters |
REC |
|
Impact Assessment
By loosening the requirements for positional description of the spectra,
existing theory services will be able to be compliant. Clients will need
to allow for the coverage fields to be missing. However, they already
need to do that for established SSA theory services, of which there are
at least five at this point; RegTAP query:
select count(ivoid)
from rr.res_detail
where detail_xpath='/capability/dataSource'
and detail_value like 'theor%'