NULL-valued TAP_SCHEMA boolean columns?

[Marco Molinaro]

Hi Mark,
it is true it is not explicit, but I always read the descriptive text at
the end of the columns description in TAP§2.6.3 as true/false flags, so to
me it makes no sense to have NULLs in there.
I consider it can happen that a provider is undecided whether to put a 0 or
a 1, but in that case I'd put a 0, not a NULL, i.e. I may loose some
information on indexing or standardization but keep the boolean flagging
solution for those fields.

Cheers,
   Marco

ps - should this go in the errata system (when ready) to explicit the
eventual decision on it?

2014-06-10 14:39 GMT+02:00 Mark Taylor <m.b.taylor at bristol.ac.uk>:

> Hi TAPistas,
>
> Another TAP validation quibble.
>
> The TAP_SCHEMA.columns table (TAP section 2.6.3) contains three required
> integer columns (std, principal, indexed) annotated thus:
>
>    "1 means true, 0 means false"
>
> Question: is it legal to have NULL values in these columns?
> The implication of the text seems to be that this is not permitted
> (since other column descriptions say things like "if known" where
> NULL is permitted), but it's not explicit.
>
> Thanks
>
> Mark
>
> --
> Mark Taylor   Astronomical Programmer   Physics, Bristol University, UK
> m.b.taylor at bris.ac.uk +44-117-9288776  http://www.star.bris.ac.uk/~mbt/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ivoa.net/pipermail/dal/attachments/20140610/45fab243/attachment.html>