TAP RFC [VOSI]

[Patrick Dowler]

Unless anyone has any immediate objections/issues, I think this is a good 
compromise and intend to adopt it as I make the necessary changes to the TAP 
document. I expect to get to this item on about thursday.

If anyone feels like reading the final document before Keith puts it up for the 
TCG review, let me know and I will send a copy late this week for some nice 
weekend reading :-)

thanks,

Pat

On Sunday 27 September 2009 10:11:22 Douglas Tody wrote:
>      1)  We add resource endpoints for the VOSI operations.  Hence for base
>          resources we have the following (all with the same baseURL):
> 
>              sync
>              async
>              capabilities
>              availability
>              tableMetadata
> 
>      2)  We retain REQUEST and VERSION to specify the logical (service
>          specific) service operations.  These use either the sync or
>          async endpoints.  Hence we have
> 
>              async/REQUEST=doQuery&VERSION=1.0&...       # TAP
>              sync/REQUEST=queryData&VERSION=1.0&...      # Other DAL
>                  (etc.)
> 
>      3)  We require that getCapabilities be provided as a service
>          operation as well as as a base resource:
> 
>              sync/REQUEST=getCapabilities
> 

-- 

Patrick Dowler
Tel/Tél: (250) 363-0044
Canadian Astronomy Data Centre
National Research Council Canada
5071 West Saanich Road
Victoria, BC V9E 2M7

Centre canadien de donnees astronomiques
Conseil national de recherches Canada
5071, chemin West Saanich
Victoria (C.-B.) V9E 2M7