Fwd: Simple Cone Search 1.1 - (new) internal WD

[Marco Molinaro]

sorry...forgot a reply-all...

Marco
---------- Forwarded message ----------
From: Marco Molinaro <molinaro at oats.inaf.it>
Date: 2017-10-11 9:27 GMT+02:00
Subject: Re: Simple Cone Search 1.1 - (new) internal WD
To: Walter Landry <wlandry at caltech.edu>


Hi Walter, all,

2017-10-10 18:23 GMT+02:00 Walter Landry <wlandry at caltech.edu>:

> Markus Demleitner <msdemlei at ari.uni-heidelberg.de> wrote:
>

[... cut ...]


> >> > 4 - trying or not to use UCD1+
> >>
> >> Pretty please?  We allow access to our tables via a number of
> >> protocols (SIA2, SSA, SCS, TAP).  I really, really, really do not want
> >> to maintain different UCD's for each protocol.
> >
> > True, that's a wart, but changing the UCDs *would* actually break
> > clients.  Also, on the server side it's not *that* much of an issue.
> > In DaCHS, it's about 20 lines of relatively benign code -- essentially:
> >
> >               ucdCasts = {
> >                       "meta.id;meta.main": {"ucd": "ID_MAIN",
> "datatype": "char",
> >                               "arraysize": "*"},
> >                       "pos.eq.ra;meta.main": {"ucd": "POS_EQ_RA_MAIN",
> >                               "datatype": "double"},
> >                       "pos.eq.dec;meta.main": {"ucd": "POS_EQ_DEC_MAIN",
> >                               "datatype": "double"},
> >               }
> >
> > (and a bit of support code in the serialiser that's required for
> > SIAP, too)-- and with SCS 1.1, the datatype cast could go away.
>
> I would like to provide more than 3 UCD's.  They are kind of useful.
>

But, apart from the mandatory "trio" you can add whatever UCD you like,
actually you're more than welcome to do so.
Sorry, I don't understand the meaning of the last comment you made.

Marco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/apps/attachments/20171011/f002324c/attachment.html>