VOSpace home page
Discussion page for the VOSpace 2.1 specification
This is a discussion page for the VOSpace-2.1 service specification.
Since this is a minor revision, all changes to the specification must be backwards compatible with the VOSpace-2.0 specification.
Matters arising from IVOA Waikoloa (September 2013)
Parameter based sync transfer negotiation
This is a proposal to support the ability to perform a transfer negotiation by posting transfer parameters to the /sync endpoint. This would be functionally equivalent to posting the transfer XML document to the /sync endpoint. For example:
Parameter based POST:
curl -X POST -d "TARGET=vos://nvo.caltech!vospace/mydata1&DIRECTION=pullFromVoSpace&PROTOCOL=ivo://ivoa.net/vospace/core#httpget" "http://localhost:8000/sync"
Would be equivalent to:
curl -X POST -d @job.xml "http://localhost:8000/sync"
Where job.xml is a file containing:
<vos:transfer xmlns:vos="http://www.ivoa.net/xml/VOSpace/v2.1">
<vos:target>vos://nvo.caltech!vospace/mydata1</vos:target>
<vos:direction>pullFromVoSpace</vos:direction>
<vos:protocol>ivo://ivoa.net/vospace/core#httpget</vos:protocol>
</vos:transfer>
The motivation for adding this behaviour is to allow the negotiation of a transfer to happen with a single URL without having a smart client or having to generate an XML document. This is convenient when referring to VOSpace nodes from web interfaces.
Deprecation of view=data
Link Node documentation clarity