ObsCore and extensions

[Patrick Dowler]

At the last interOp and while comparing the radio extension to
CAOM-2.4 and some new features in WD-CAOM-2.5, it became increasingly
clear that some of the proposed fields for the radio extension are
more generally applicable and in my opinion should be promoted to
"core". I kind of volunteered to write down the details of that, so
here it is that proposal:

** core **
s_resolution_min
s_resolution_max
s_fov_min
s_fov_max: I still feel the existing s_fov is already the same as
s_fov_max and not a representative value; it is nominally the size of
the s_region
t_exp_min
t_exp_max
t_exp_mean: In CAOM exposure is already the mean exposure time per
pixel and I feel strongly that the existing ObsCore.t_exptime is
already the same thing (well, it suggests "median exposure time per
pixel" which I think I may have contributed, but median breaks down in
some common nearly degenerate cases and is less useful than mean; we
may need to clarify the definition in ObsCore
f_resolution: absolute spectral resolution is useful, but this should
be named em_resolution

** radio extension **
s_maxiumum_angular_scale - I have been convinced by radio people that
maximum_recoverable_scale is more explicit and a better term for this
uv_distance_min
uv_distance_max
uv_distribution_ecc
uv_distribution_fill

Questions:
1. How does this impact the time extension?
2. How does this impact the high energy extension?

Work:
1. ObsCore needs to be ported to ivoatex (from docx?) and included in ivoa-std
2. I can set aside time necessary to write the the changes for WD-ObsCore-1.2


--
Patrick Dowler
Canadian Astronomy Data Centre
Victoria, BC, Canada