Three cheers for GET services

[Markus Dolensky]

Hi Wil,

Your response triggered a question concerning SSA:

 > Pointed out many times and by Tony again. Making what you call a GET over SOAP
 > is very simple if the service is simple enough. In .NET if it is simple
 > enough it does this for you automatically hence this is a SOAP service to the
 > registry
 > 
http://nvo.stsci.edu/voregistry/registry.asmx/QueryResource?predicate=servicetype%20like%20'%siap%'

One case where we need this is when embedding an access reference in the query 
output of an SSA service. In the case of SIA the access reference is a URI that 
tells the client how to retrieve the actual data. SIA was restricted to the GET 
method, but we don't want to stop there when defining SSA.

What your example above tells me is that a service can put an access reference 
to a data access method into a Votable <TD> element similar to the way it's 
currently done in SIA for HTTP GET services. Is this true in the given context 
or do you think we need anything more sophisticated?

Cheers,
Markus