SODA erratum 3 proposal

[Patrick Dowler]

Hi Markus,

I guess I was clear in my intent. I think either approach can work and we
have one (scalar MIN and MAX) in examples and use and another that's
not, so I am fine with staying where we are for the existing cases. I agree
that
future cases should aim for consistency and only use extra rules when
necessary.

I will make a point to clarify in WD-DALI

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


On Tue, 14 Feb 2023 at 01:36, Markus Demleitner <
msdemlei at ari.uni-heidelberg.de> wrote:

> Hi Pat,
>
> On Mon, Feb 13, 2023 at 10:35:27AM -0800, Patrick Dowler wrote:
> > I feel like the change in wording in WD-VOTable means that DALI (where
> > xtype="interval" is defined) could (could have) defined min/max behaviour
> > to be more like that pointed out by Adrian in the PyVO context. That is:
> > use a 2D array value for MAX to specify the minimum bounding interval.
>
> But why would want to introduce magic behaviour (over the standard
> array interpretation) when we don't absolutely need to (which
> arguably is the case when we do geometries as we ended up doing
> them)?
>
> > So in my opinion MIN/MAX scalars like we already have, a MAX array
> (bounds)
> > would work, WD-VOTable defers to the xtype-definition but seems to allow
> > both (in principle), and DALI needs to be clarified.
>
> True -- but I'd generally argue the fewer special rules the better.
> Call it Occam's Editor :-)
>
>          -- Markus
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/dal/attachments/20230214/ec559d49/attachment-0001.htm>