VOSpace20140918 < IVOA

Comments and suggestions on the [[http://www.ivoa.net/documents/VOSpace/20140805/WD-VOSpace-2.1-20140805.html][VOSpace-2.1 working draft]].

From the mailing list [[http://mail.ivoa.net/pipermail/grid/2014-August/002637.html][announcement]] :

   * Summary of [[http://volute.googlecode.com/svn/trunk/projects/grid/vospace/doc/VOSpace.html#sec6][recent changes]]
   * Line by line [[https://code.google.com/p/volute/source/diff?spec=svn2701&r=2690&format=side&path=/trunk/projects/grid/vospace/doc/VOSpace.html&old_path=/trunk/projects/grid/vospace/doc/VOSpace.html&old=2654][diff]]

---+++ HTML anchors
The HTML anchors use =name= rather than =id=, is this intentional ? 
<verbatim>
    <a name="0.1_sec1">1. Introduction</a>
</verbatim>
rather than 
<verbatim>
    <a id="0.1_sec1">1. Introduction</a>
</verbatim>

---+++ Create node path
In the create node operation described in section 1.1,
the path in the node XML

    =vos://nvo.caltech!vospace/mytable1=

does not match the path encoded
in the target URL of the =HTTP PUT= request given in the text.

    =http://nvo.caltech.edu/vospace/myData/table123=

---+++ Create endpoint URL/URI

If the service endpoint for the example VOSpace service is 

    =http://nvo.caltech.edu/vospace/=

then the target URL for the =HTTP PUT= request should be

    =http://nvo.caltech.edu/vospace/nodes/myData/table123=

and the =uri= in the node XML should either be blank, or it
should match the path in the =HTTP PUT= target URL

    =vos://nvo.caltech!vospace/myData/table123=

---+++ Create node clarification
There are a number of places where the description of how the create node operation works could be clarified.

   * The current specification does not state clearly how the intended node path is encoded in the target URL of the =HTTP PUT= request.
   * The current specification does not state clearly whether or not the node URI should be included in the create node message.
   * The current specification does not state clearly whether the service should issue an error if the path in the node URI does not match the path encoded in the target URL of the =HTTP PUT= request

---+++ Transfer endpoint URL
In the example transfer described in section 1.1, 
the target URL of the =HTTP POST= operation given in the text points to
a location within the tree of nodes below the target node.

    =http://nvo.caltech.edu/vospace/myData/table123/transfers=

In VOSpace-2.1 transfer operations should be initiated by a =HTTP POST= request to
the ={service}/transfers= endpoint, outside the ={service}/nodes= tree.

If the service endpoint for the example VOSpace service is 

    =http://nvo.caltech.edu/vospace/=

then the target URL for =HTTP POST= request should be

    =http://nvo.caltech.edu/vospace/transfers=

---+++ Transfer target URI
The path of the =target= in the body of the =HTTP POST= request
should match the path of the node created in the first step
of the example.

    =vos://nvo.caltech!vospace/myData/table123=
This topic: IVOA > TWikiUsers > DaveMorris > VOSpace20140918
Topic revision: r2 - 2014-09-19 - DaveMorris