Discussion page for the VOSpace 2.1 specificationThis is a discussion page for the VOSpace-2.1 service specification. Please edit this page directly to add comments or specification changes and additions.Changes and Enhancements for VOSpace 2.1Parameter based sync transfer negotiationThis is a proposal to support the ability to perform a simplified transfer negotiation by executing an HTTP GET with transfer parameters to the /sync endpoint. For example: Parameter based GET:curl -d "TARGET=vos://nvo.caltech!vospace/mydata1&DIRECTION=pullFromVoSpace&PROTOCOL=ivo://ivoa.net/vospace/core#httpget" "http://localhost:8000/sync"
Would be somewhat 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">
Instead of returning a redirect to the transferDetails (which will contain the endpoint URL(s)), it would return a single, preferred endpoint URL directly. This is an optimization that reduces the number of redirects.
Since there is no job associated with the optimized GET, there less ability to do correct error handling. Upon error, clients should revert to the POST to /sync for full transfer negotiation and error handling capability. This is an optimistic approach and assumes that there is a low error rate in the service and this fallback would not happen frequently.
Add desired authentication method to transfer documentIn certain cases, there isn't enough information in the transfer negotiation document to produce URLs to the data store correctly. The missing piece of information is authentication method they wish to use on the URLs. For example, if they wish to use userid/password to authenticate, the URLs must be pointed at a resource that will block and collect that information. If a cookie is to be used, the resource must not block. Authentication method options should include, but are not limited to:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Capabilities: dynamic capabilities and error handlingPlease refer to this threadAddressing changes from VOSpace 2.1Please refer to this page Dave Morris has identified a number of inconsistencies in the document, most dating back to the v1.1 -> v2.0 conversion. There is the question as to how these should be addressed, considering VOSpace 2.0 has been a proposed recommendation for some time. Here are three options:
New document formatThe existing document is in html format and needs to be converted to a more editable medium. Should this be XHTML or ivotex?VOSpace interoperable clients and serversI would like to propose the goal of having a working interoperability of two or more VOSpace implementations (version 2.1?) by Oct 2015. Please update the implementations table on the VOSpace home page if your institution has built a VOSpace. | ||||||||
Deleted: | ||||||||
< < |
Notes / Questions / Discussion Items / Ideas
| |||||||
The 2.1 Working Draft
Change NotesFrom version 2.0-20130329 (in progress):
For future VOSpace versions:Please see The VOSpace 3.0 Discussion Page for future changes and enhancements to VOSpace beyond version 2.1.<--
|