Obscore 1.1 Erratum 3: Drop obs_id non-NULL requirement

[Patrick Dowler]

This errata looks fine to me, except:

In the very last sentence with advice for query writers, "obs_id is not
null" will omit results which is likely not what people want. Instead, they
just need to treat NULL obs_id as not equal to another NULL obs_id, which
is normal database semantics for NULL values. Thus, NULL obs_id(s) always
indicates distinct observations.

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


On Tue, 12 Apr 2022 at 08:41, Markus Demleitner <
msdemlei at ari.uni-heidelberg.de> wrote:

> Dear DAL, dear DM,
>
> [followups again suggested to DAL only]
>
> Given that the discussion on the non-NULL requirement on obscore's
> obs_id column did not show a convincing need for the requirement and
> it is an implementation burden in particular in the presence of
> validators (see the erratum's rationale), I've written up a proposed
> erratum for Obscore 1.1; see
>
> https://wiki.ivoa.net/twiki/bin/view/IVOA/ObsCore-1_1-Erratum-3
>
> Does anyone have major qualms with this?  Have I perhaps missed
> material in the Obscore document that would also need changes?
>
>       -- Markus
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/dm/attachments/20220426/b17e5555/attachment.html>