VOSpace 1.1 specification: Request for Comments

This document completed its RFC period in October 2008. It is now undergoing TCG review. The specification is currently at Proposed Recommendation v.1.15. There are also machine readable files (WSDL and schema) available at the URL given in Appendix 1 of this document.

In order to add a comment to the document, please edit this page and add your comment to the list below (include your 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.

Comments from the community

• There's something wrong with both the URL and the error handler of the server given above. Who can help? -- MarkusDemleitner

• The WSDL VOSpaceContract-v1.1-rc3.wsdl from the VOSpaceHome contains

some mistake. We have to add PropertyNotFoundFault to CreateNode operation and NodeNotFoundFault to FindNodes operation.

The utility wsdl2java from Axis2 doesn't work if these faults are missing. -- CyrilPestel

• These have been corrected now -- MatthewGraham

TCG Review (from 06/05/2009 to 18/09/2009)

During the TCG review, Working and Interest Group chairs should add their comments under their name:

Applications (Tom McGlynn, Mark Taylor)

I approve this document. However I have been confused by the mismatch between the nominal VOSpace standard numbers and the document version. I don't know if that could be addressed in some simple way. TAM

Data Access Layer (Keith Noddle, Jesus Salgado)

I welcome and heartily approve this document! (Keith Noddle)

Data Model (Mireille Louys, Anita Richards)

I approve this document .(MireilleLouys)

Grid & Web Services (Matthew Graham, Paul Harrison)

I approve this document (MatthewGraham)

Registry (Ray Plante, Aurelien Stebe)

I approve this document (RayPlante)

Semantics (Sebastien Derriere, Norman Gray)

I've added some comments on the GWS list

VOEvent (Rob Seaman, Alasdair Allan)

Approved.

VO Query Language (Pedro Osuna, Yuji Shirasaki)

I approve (PedroOsuna)

VOTable (Francois Ochsenbein)

As already mentioned by Bob, Severin, Christophe, a pdf or html document is a requirement. "Andreas" is not the correct first name of the 6th author. Otherwise I approve the document. (FrancoisOchsenbein - 17 Sep 2009)

Standard and Processes (Francoise Genova)

Approved provided that the remarks provided by other WGs/IGs are addressed, including provision of a pdf version.

Astro RG (Masatoshi Ohishi)

I approve this nice document.

Data Curation & Preservation (Bob Hanisch)

Approved with the caveats as noted by Christophe and Severin below, and providing that a PDF version of the document is made available.

Theory (Herve Wozniak, Claudio Gheller)

Approved.

TCG (Christophe Arviset, Severin Gaudet)

I appreciate the efforts from the editors for the updates between v1.14 and v1.15, so the VOSpace 1.15 document is self standing.

Although VOSpace 1.15 should probably be VOSpace 2.0 as it is not compatible with the previous REC VOSpace 1.0, I also mention here publicly that we agreed to leave this version to VOSpace 1.15 as it would be too difficult to change the existing implementations. This incompatibility is stated in page 1 so this is clear.

I approve the document with the minor questions/editorial comments:

• please add page numbers to the document so it is easier to read and reference

Done

• [page 2, 1 Introduction, last paragraph] Replace VOSpace 2.0 by VOSpace 1.1

Done

• [page 10, model] Should we use standard UML notation as in the VOSpace 1.0 document ?

I don't have the source for this diagram anymore but will switch back to standard UML notation in the version.

• [page 15 3.4.1] Probably Heading "Simple File Store" should get section number 3.4.1.1 and "Database store" should get 3.4.1.2

Done

• [page 25 5.1.1 getProtocols] Is there somewhere a fixed list of allowed/supported protocols ?

VOSpace 1.15 is transport protocol agnostic and does not mandate any particular protocol: these are understood to be implementation dependent. Protocols can be registered in the registry as VOStandards. The list of 'standard' protocols is given in section 3.5.

• [page 38 5.4.2 pullToVoSpace] Shouldn't this be pullFromVoSpace to also be compatible with section 5.4.2.3 ?

No.

• [page 46 References] In the light of the agreement to clearly identify dependencies amongst IVOA standard, please add
  • reference to the Registry Interface standard as it is mentioned in page 14 section 3.3.2
  • reference to SSO standard as it is mentioned in page 25 section 4 Access Control

Reference added to SSO but there is no explicit mention of the RI standard in page 14 section 3.3.2.