i v o a . n e t

/ WebHome / IvoaGridAndWebServices / IVOA.VOSpaceHome

This Web


Trieste Interop 

WebHome 
WebChanges 
WebTopicList 
WebStatistics

All Webs


Astrodata
IVOA
Know
Sandbox
TWiki
Trash

TWiki intro
TWiki tutorial
User registration
Notify me

W/I Groups


Data Access
Data Model
GWS
Query Language
Registry
Stds&Procs
Semantics
VOEvent
VOTable

Applications
Astro-RG
Data Curation
Theory

ivoa.net


www.ivoa.net
Doc. Repository
Events
Projects
XML Schema

IVOA Grid & Web Services: VOSpace

Contents


Overview

Users want to be able to easily publish and share their own data as well as have data reside close to computation nodes when large-scale processing or dynamic caches for intermediate data products in workflows are involved. Three modes of data transfer need to be supported: client-server (the client pushes data to, or pulls data from, the server), server-client (the server pushes data to, or pulls data from, the client) and server-server (one server pushes data to, or pulls data from, another server in response to a client request) also known as third-party transfer.

There are many solutions already to these problems so instead of inventing our own we specify a lightweight interface, VOSpace, that sits on top of existing storage solutions, providing a common interface to an underlying heterogeneity of implementations from local file systems to bulk data grids. VOSpace can distinguish between unstructured data, which is just a collection of bytes, and structured data where there is knowledge about how the bytes are arranged and so additional operations are possible. Individual VOSpace instances can also be federated into a peer network so that the user just interacts with a single data space.

VOSpace 1.x specifications relate to a SOAP-based web service.

VOSpace 1.0

VOSpace 1.0 defines an unconnected flat file space and is now an IVOA Recommendation:

Specification

VOSpace 1.1

VOSpace 1.1 extends the existing 1.0 specification to support containers, links between individual VOSpace instances, third party APIs and a "find" mechanism.

Specification

Discussion

History

VOSpace 2.0

VOSpace 2.0 defines a RESTful interface.

Specification

Nothing ready quite yet.

Discussion

Implementations

group version endpoint VOSpace root Notes
Caltech v1.1 testnvo.cacr.caltech.edu vos://nvo.caltech!vospace/ HTTP transports, supports structured nodes and archive formats (tar, tar.gz)
ESO v1.0 vops1.hq.eso.org vos://org.eso!vospacetest/ HTTP transports
Astrogrid

Mailing list

The mailing list for discussion of the VOSpace specifications and related issues is: vospace@ivoa.net which is archived at: http://ivoa.net/forum/vospace/index.htm

VOSpace 1.0 history

Discussion

The discussion pages that lead up to the V1.0 working draft are available here :


Attachment sort Action Size Date Uploaded by Comment
VOSpace-Usage.odt manage 201.5 K 01 Oct 2007 - 16:18 PaulHarrison vospace usage note version 0.1
vospace.wsdl manage 50.5 K 11 Mar 2008 - 16:58 MatthewGraham VOSpace 1.1 RC1 WSDL
VOSpaceTypes-v1.1rc1.xsd manage 52.2 K 11 Mar 2008 - 16:59 MatthewGraham VOSpace 1.1 RC1 Message Schema

 
 
© 2003-2007 by the contributing authors.  - You are TWikiGuest