On Wednesday 02 May 2007 19:23, Doug Tody wrote:
> ---------- Forwarded message ----------
> Date: Tue, 1 May 2007 17:37:31 -0400 (EDT)
> From: Maria A. Nieto-Santisteban <nieto-at-skysrv.pha.jhu.edu>
> Subject: TAP issues
> 1) How does the service say which ADQL constructs support and which not?
> 2) What is needed to describe a TAP service so users/clients can do
> decent queries in terms of content and performance?
Yes, we do need to tackle this at some point but right now I think it is more important to determine what the constructs are first (the ADQL doc is now in pretty good shape w.r.t. reserved words and that is the bulk of it), so #1 should follow after the ADQL spec is pretty much done.
As for the "content metadata", that also has to follow the ADQL spec too because inclusion of some things in ADQL is what complicates the metadata. For example, with JOIN in the ADQL spec, we now have to include in the metadata enough info so users can actually write a decent/correct join. Thus, I think it fits the priorities (1-ADQL, 2-TAP) and the dependencies that we have deferred the capabilties and metadata discussion(s) until we know what we need to cover... but we know we have to do this :)
-- Patrick Dowler Tel/Tél: (250) 363-6914 | fax/télécopieur: (250) 363-0045 Canadian Astronomy Data Centre | Centre canadien de donnees astronomiques National Research Council Canada | Conseil national de recherches Canada Government of Canada | Gouvernement du Canada 5071 West Saanich Road | 5071, chemin West Saanich Victoria, BC | Victoria (C.-B.)Received on 2007-05-03Z19:56:57