International Virtual Observatory Alliance

Difference: VOSpace20140918 (1 vs. 2)

Revision 22014-09-19 - DaveMorris

  META TOPICPARENT 
  name="DaveMorris"  

Comments and suggestions on the VOSpace-2.1 working draft.

From the mailing list announcement :
 

 Summary of recent changes
  Line by line diff
 

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

rather than 
    <a id="0.1_sec1">1. Introduction</a>
- META TOPICPARENT
+  name="DaveMorris"
-<
<
+ Example node path 
In section 1.1 the node path in the node details XML does not match the path given in the text for the initial POT operation.
->
>
+ Create node path 
In the create node operation described in section 1.1,
->
>
+the path in the node XML
-<
<
+In the text description :
->
>
+    vos://nvo.caltech!vospace/mytable1
-<
<
+"Let's consider the first sequence: the user provides a XML description of the data file which they HTTP PUT to the appropriate VOSpace URI - this will be the HTTP identifier for the data file in the VOSpace, e.g. http://nvo.caltech.edu/vospace/myData/table123."
->
>
+does not match the path encoded
->
>
+in the target URL of the HTTP PUT request given in the text.
-<
<
+the URI target is given as http://nvo.caltech.edu/vospace/myData/table123
->
>
+    http://nvo.caltech.edu/vospace/myData/table123
-<
<
+In the example node XML :
->
>
+ Create endpoint URL/URI
-<
<
->
>
+If the service endpoint for the example VOSpace service is
-<
<
+    <node xmlns="http://www.ivoa.net/xml/VOSpaceTypes-v2.1"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
        uri="vos://nvo.caltech!vospace/mytable1"
        xsi:type="vost:UnstructuredDataNode">  
         
            text/xml
-<
<
+the URI target is given as vos://nvo.caltech!vospace/mytable1
->
>
+    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

Revision 12014-09-18 - DaveMorris

META TOPICPARENT	name="DaveMorris"

Comments and suggestions on the VOSpace-2.1 working draft.

From the mailing list announcement :

Summary of recent changes
Line by line diff

HTML anchors

The HTML anchors use name rather than id, is this intentional ?

    <a name="0.1_sec1">1. Introduction</a>

rather than

    <a id="0.1_sec1">1. Introduction</a>

Example node path

In section 1.1 the node path in the node details XML does not match the path given in the text for the initial POT operation.

In the text description :

"Let's consider the first sequence: the user provides a XML description of the data file which they HTTP PUT to the appropriate VOSpace URI - this will be the HTTP identifier for the data file in the VOSpace, e.g. http://nvo.caltech.edu/vospace/myData/table123."

the URI target is given as http://nvo.caltech.edu/vospace/myData/table123

In the example node XML :

    <node xmlns="http://www.ivoa.net/xml/VOSpaceTypes-v2.1"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
        uri="vos://nvo.caltech!vospace/mytable1"
        xsi:type="vost:UnstructuredDataNode">  
        <properties> 
            <property uri="ivo://ivoa.net/vospace/core#mimetype">text/xml</property>     
        </properties> 
    </node>

the URI target is given as vos://nvo.caltech!vospace/mytable1

View topic | History: r6 < r5 < r4 < r3 | More topic actions...