<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
Dear VOSpacers,<br>
<br>
With an intern, Grégory Adam, we are starting to look into the
VOSpace spec. and we have some (simple, I hope) questions on the
document (2.1).<br>
<br>
--------------<br>
<b><br>
1. About getNode and its parameter `detail=min`:</b><br>
<br>
The VOSpace document says:<br>
<blockquote>
<blockquote type="cite">- min: the returned record for the node
contains minimum detail<br>
with all optional parts removed – the node type should
be re-<br>
turned</blockquote>
</blockquote>
If I try to sum up: the "optional parts" are everything except
<vos:nodes> in case of a ContainerNode. So, it means that
apart from the node type (attribute xsi:type) a non-ContainerNode
will be empty.<br>
<br>
Is it correct?<br>
<br>
If yes, there is a mistake in the example given in 6.3.1: the
XML elements <vos:properties>, <vos:accepts>,
<vos:provides> and <vos:capabilities> should not be
returned. According to the XML schema they are optional.<br>
Or are they optional only if empty?<br>
Or because "SHALL" is used instead of "MAY" (in 3.1, page 13) it
make them mandatory if not empty?<br>
<br>
--------------<br>
<br>
<b>2. About getNode and its parameters `uri` and `offset`:</b><br>
<br>
The VOSpace document says:<br>
<blockquote>
<blockquote type="cite">If a “uri” and “offset” are specified in
the request then the returned list<br>
will consist of the subset of children which begins at the node
matching<br>
the specified value of the “uri” parameter and with cardinality
matching the<br>
specified value of the “offset” parameter drawn from an ordered
sequence<br>
of all children. The ordering is determined by the server but
results must<br>
always be drawn from the same ordered sequence.</blockquote>
</blockquote>
When it is said "which begins at the node matching the specified
value of the “uri” parameter",<br>
does "begin" mean "the string begins" or "the returned sublist
must starts with"?<br>
<br>
For instance, in the given example:<br>
<br>
<tt><a class="moz-txt-link-freetext" href="http://server.example.com/vospace/nodes/mydir?detail=min&">http://server.example.com/vospace/nodes/mydir?detail=min&</a></tt><b><tt>uri=vos://example.com!vospace/mydir/file3401</tt><br>
</b><br>
* Should the `uri` filter be interpreted as all files whose name
begins with "file3401" in the directory
"vos://example.com!vospace/mydir"?<br>
<i>(e.g. "file3401a", "file3401b", ...)<br>
<br>
</i>* If yes, the example in 6.3.1. should be fixed.<i><br>
</i><br>
* Or should it be the sublist of all children starting from the
child "file3401"?<br>
<i>(e.g. if the complete ordered list is [file3399, file3400,
file3401, file3402, file3403], the returned list would be
[file3401, file3402, file3403])</i><br>
<br>
--------------<br>
<br>
<b>3. About getNode</b><br>
<br>
Using the same example as in the document, if I run the
following request:<br>
<br>
<tt>curl -v <a class="moz-txt-link-rfc2396E" href="http://server.example.com/vospace/nodes">"http://server.example.com/vospace/nodes"</a></tt><br>
<br>
Should it give me the list of all child nodes at the root of the
VOSpace (as if the root is itself a ContainerNode)?<br>
<br>
Sorry for the possibly stupid question, but it is just to be
sure.<br>
<br>
<br>
--------------<br>
<br>
<b>4. About Properties, Capabilities and Views</b><br>
<br>
Properties, Capabilities and Views may have the following
attributes:<br>
<br>
- DisplayName<br>
- Description<br>
- UCD <i>(only for Properties)</i><br>
- Unit <i>(only for Properties)<br>
</i> - MimeType <i>(only for Views)<br>
</i><br>
But none of these elements appear in the XML schema (and they
appear in no example). The XML schema does not give enough
flexibility to insert additional information like these.<br>
<br>
So, we wonder how to represent them in the XML and where? How
can they be discovered?<br>
Have we missed something?<br>
<br>
--------------<br>
<br>
<b>5. Existing VOSpace services and clients</b><br>
<br>
<br>
I searched in the VO Registries, but I did not find a lot of
(still) active VOSpaces apart from the following ones:<br>
<br>
- ESA (<a class="moz-txt-link-freetext" href="https://vospace.esac.esa.int/vospace/">https://vospace.esac.esa.int/vospace/</a>)<br>
- CADC/Canfar (<a class="moz-txt-link-freetext" href="https://www.canfar.net/storage/list/">https://www.canfar.net/storage/list/</a><a spellcheck="false" href="https://vospace.esac.esa.int/vospace/" style="box-sizing: border-box; cursor: pointer; color: rgb(65, 131, 196); -webkit-user-drag: none; font-family: "Open Sans", "Clear Sans", "Helvetica Neue", Helvetica, Arial, sans-serif; font-size: 16px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 4; text-align: left; text-indent: 0px; text-transform: none; white-space: pre-wrap; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);"><span class="md-plain" style="box-sizing: border-box;"></span></a>)<br>
<br>
Are there more?<br>
<br>
Similarly, is there any know (generic) client?<br>
<br>
--------------<br>
<br>
Thank you in advance for your help.<br>
<br>
Cheers,<br>
Grégory<br>
<br>
</body>
</html>