Discussion page for the VOSpace 2.1 specificationThis 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. | ||||||||
Changed: | ||||||||
< < | Matters arising from IVOA Waikoloa (September 2013) | |||||||
> > | Enhancements for VOSpace 2.1 | |||||||
Parameter based sync transfer negotiationThis 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: | ||||||||
Changed: | ||||||||
< < | <vos:transfer xmlns:vos="http://www.ivoa.net/xml/VOSpace/v2.1"> | |||||||
> > | <vos:transfer xmlns:vos="http://www.ivoa.net/xml/VOSpace/v2.1"> | |||||||
Changed: | ||||||||
< < | 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. | |||||||
> > | The motivation for adding this functionality 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. | |||||||
Deleted: | ||||||||
< < | Deprecation of view=data | |||||||
Link Node documentation clarity | ||||||||
Added: | ||||||||
> > | For the benefit of implementers, clarify the expected behaviour of the operations in Section 5 when the operation can pertain to LinkNodes. | |||||||
<--
|