I want to make a comment just for clarifying something)
> in the TSAP url at:
>
> http://www.laeff.inta.es/projects/svo/theory/tsap/
This page only works right for previous versions of SSAP. In the new version, when asking for the format=metadata, the answer contains, as params, both the inputs and outputs of the model (with a INPUT: or OUTPUT: prefix).
The web application that Miguel recommends is not prepared for that. It expects that the outputs come as fields of a table with no data (some old espcification of this format=metadata dialog).
The service that you have developed is compliant to the new SSAP recommendation (congratulations :-) and thus, when checked by my web application, it does not work properly (my application thinks that all the parameters are inputs).
It's obviously my fault, not yours. I will upgrade to the new version as soon as posible.
Sorry for the confusion.
Carlos
> (However, it does not produce the final set of spectra, and the TSAP
> query form is quite
> different in the fields than the one at:
> http://vo.ari.uni-heidelberg.de/ssatr-0.01/TrSpectra.jsp
> I suppouse that in this last address you assume some defaults that are
> not in the
> format=metadata query, isn't it?)
>
> I want to recall that this service is just a TSAP ( == format=metadata
> part of SSAP) service.
>
>
> Another issue is how VOSpec manage the TSAP service and specta in general
> (VOSpec also need other fields in the VOTable, like VOX etc and the
> dimensional analisys posted at IVOA and astro-ph
> by Pedro Osuna and Jesus Salgado maybe a year or more ago... you can see
> documentation in
> VOSpec it self I think and look to their warpper of VO tables).
>
> Summing up: TSAP only means the format=metadata part of SSAP (no more)
> and you can tested your TSAP service (following the SSAP) at the address
> pointed before :)
>
> cheers
>
> m
>
>
Received on 2007-10-15Z15:43:30