Simple Cone Search 1.1 - (new) internal WD

[Mark Taylor]

On Wed, 11 Oct 2017, Marco Molinaro wrote:

> > no, the client provide an epoch (ISO format or julian day) to the service
> > which uses it to compute the positions of the celestial objects (planets,
> > stars, ...) in order to select those which actually belong to the FOV, so
> > that the client can cross-match the sources and then identify them. In the
> > output the epoch is just recalled in a param element.
> >
> 
> So, I badly explained myself.
> You're really asking that server-side the response positions
> are re-calculated  based on the EPOCH value in the query.
> This is the additional effort that would be required to data providers
> if we add and/or mandate this parameter.

To me that sounds less like a job for *simple* cone search, and
more like something that could be done with a TAP query based on
some (user-defined? standard but optional?) function that willing
TAP implementations could provide for integrating known motions 
up to a given epoch.

--
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/