IVOA Grid & Web Services: VOSpaceContentsOverviewUsers 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.0VOSpace 1.0 defines an unconnected flat file space and is now an IVOA Recommendation:SpecificationVOSpace 1.1VOSpace 1.1 extends the existing 1.0 specification to support containers, links between individual VOSpace instances, third party APIs and a "find" mechanism.SpecificationStandard URIsThe VOSpace specification refers to a number of standard URIs for properties, views and protocols. The following URIs will be used to represent the standard protocols:
Discussion
HistoryVOSpace 2.0VOSpace 2.0 defines a RESTful interface.SpecificationThe proposed recommendation is available here.DiscussionVOSpace 2.1VOSpace 2.1 contains minor additions and corrections to the RESTful version 2.0.SpecificationThe current Working draft is available here.DiscussionCustom URIsThe VOSpace specification allows 3rd parties to define custom properties, protocols and views simply by choosing a unique URI to represent them. The following URLs link to some examples of custom properties, protocols and views.
| ||||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||
< < | ||||||||||||||||||||||||||||||||||||
Note - this list is for information only, and is not intended to be a definitive list of approved properties, protocols or views. | ||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||
< < | It is possibly to use custom properties, protocols and views in VOSpace messages that are not in this list. | |||||||||||||||||||||||||||||||||||
> > | It is possibly to use custom properties, protocols and views in VOSpace messages that are not in this list. However, if you want other people to use your custom URIs, then adding them to this list will enable people to find out about them. | |||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||
< < | However, if you want other people to use your custom URIs, then adding them to this list will enable people to find out about them. | |||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||
< < | VOSpace 3.0 | |||||||||||||||||||||||||||||||||||
> > | VOSpace 2.1 or 3.0 | |||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||
< < | This area acts as a placeholder for future VOSpace changes and enhancements. | |||||||||||||||||||||||||||||||||||
> > | A list of future VOSpace changes or enhancements are listed here: | |||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||
DiscussionImplementations
Mailing listThe mailing list for discussion of the VOSpace specifications and related issues is: grid@ivoa.net which is archived at: http://mail.ivoa.net/pipermail/gridVOSpace 1.0 historyDiscussion
<--
|