How to stop divergence of Parameter-TAP and ADQL-TAP?

Comments from ChristopheArviset
I would like to propose that after the discussions about this topic at Trieste interop and the conclusion from Keith at the closing plenary we don't need to put that topic in the 2008 Roadmap

Would people agree ?

There are two versions of TAP under development, one based on parameters, one based on the ADQL language, and the danger is for these to diverge into two overlapping, but incompatible, mechanisms. The diagram on the DAL blog shows an eventual convergence, but I would like to know how it will work.

I would state this more strongly: neither the Param or QL documents are so far along that they cannot be joined now. The Param document actually includes the ADQL queries. There are minor differences in the interface specifications, but these could be resolved now quite easily, I would think. If we wait until later, when groups have done implementations, there will be a lot of resistance to making changes. (Bob)

cosponsor BobHanisch

I thought that it had been decided a year ago at Beijing to focus on the QL version of TAP - see page 5 of the Plenary summary for documentary proof - Quoting

"Remove explicit data model support (POS, SIZE, etc.)•Will use ADQL plus UTYPE plus REGION instead (etc.) "

My "solution" is in - in summary Parameter-TAP is not TAP, but Simple Cone Search V2.

So I third this motion... PaulHarrison

I agree with you all. It seems to me that people do NOT take into account priorities in development. The primary purpose of the IVOA would be to realize interoperability among the VO projects in the world, and we need "non-paper" standards as early as possible. ... MasatoshiOhishi

Topic revision: r6 - 2008-06-25 - ChristopheArviset
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback