thoughts on TAP-1.2

[Dave Morris]

This is indeed one of the use cases that we had in mind for VOSpace.

A section of space in a VOSpace service where the directory structure 
maps to the catalog/schema/table hierarchy of a writable database.

Creating a 'file' called 'mytable' in 'mycatalog/myschema' would create 
a new table.

All of the object construction and access control rules map fairly well 
onto a virtual directory structure and from a user's perspective it can 
be made really simple.

To create a new database table, just drag a VOTable file from my desktop 
into 'mycatalog/myschema', and the service takes care of the rest.

As a side effect, you get all of the 3rd party asynchronous transfer 
capabilities needed to transfer a multi-Tbyte result set from one 
service to another.

Cheers,
-- Dave

--------
Dave Morris
Research Software Engineer
Wide Field Astronomy Unit
Institute for Astronomy
University of Edinburgh
--------

On 2022-03-17 07:22, Markus Demleitner wrote:
> 
> The thing that worries me a bit about the current proposal is that
> the operations *are* fairly similar to what we offer in VOSpace, and
> if we have two rather different APIs for what's straightforwardly
> subsumed as remote data management, I think we should have strong
> reasons.
> 
> Have you considered employing VOSpace for this?  If so, why did you
> discard it?  Could it perhaps be fixed to work for this use case?
>