VOSpaceRFC < IVOA

---+ VOSpace service specification: Request for Comments

This document will act as *RFC* centre for the [[http://www.ivoa.net/Documents/PR/GWS/VOSpace-20070723.pdf][VOSpace service specification]] Proposed Recommendation V1.01. There is also an accompanying [[http://www.ivoa.net/internal/IVOA/VOSpace10schema/VOSpaceContract-v1.0.wsdl][WSDL]] and [[http://www.ivoa.net/internal/IVOA/VOSpace10schema/VOSpaceTypes-v1.0.xsd][schema]]. 

Review period: 23 July 2007 - 20 August 2007

In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your TWiki.WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. 

Discussions about any of the comments or responses should be conducted on the VOSpace mailing list, vospace@ivoa.net.

---++ Implementation details

Three implementations of VOSpace 1.0 have been produced:

   * Caltech 
      * Endpoint: http://nvo.caltech.edu:8080/vospace/VOSpaceServiceImpl
      * VOSpace apache: vos://nvo.caltech!vospace/
      * Secure: yes

   * ESO
      * Endpoint: http://vops1.hq.eso.org:8080/vospace/services/VOSpacePort
      * VOSpace apache: vos://org.eso!vospacetest/
      * Secure : yes

   * Astrogrid
      * Endpoint:
      * VOSpace apache: 
      * Secure: 

Although not fully documented, the Caltech VOSpace implements all features of the VOSpace 1.0 specification including StructuredDataNodes and the ability to request different views. 

Two VOSpace clients have also been produced at Caltech - one to talk to secure VOSpace services using digital signatures (WS-Security) and one to talk to unsecure services. These clients utilize a different underlying web service infrastructure to the one that the Caltech VOSpace implementation is based on (Apache Axis 1.2.1 Final vs. XFire 1.2.2). 

The secure client has successfully negotiated data storage at the ESO VOSpace, including a third party data transfer into the VOSpace from a cone search service. This demonstrates sufficient interoperability of the implementations.


---++ Comments from the Community
   * First sample comment (by MarSierra): ...
      * Response (by _authorname_): ... 

<br>
---



<br/>
<!--
      * Set ALLOWTOPICRENAME = %MAINWEB%.TWikiAdminGroup
-->
This topic: IVOA > WebHome > VOSpaceRFC
Topic revision: r3 - 2007-07-24 - BrunoRino