<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
tt
{mso-style-priority:99;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.md-plain
{mso-style-name:md-plain;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-AU" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hi <span style="font-size:12.0pt;color:black">Grégory,<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">also with respect to your last question ICRAR has published a server and client implementation in python as well, providing a flexible backend plugin mechanism to connect to your own storage backend (posix filesystem backend is included).
Full documentation is here: <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">https://pyvospace.readthedocs.io/en/latest/<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">repo here:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a href="https://github.com/ICRAR/pyvospace">https://github.com/ICRAR/pyvospace</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Cheers,<o:p></o:p></p>
<p class="MsoNormal">Andreas<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black"><grid-bounces@ivoa.net> on behalf of Grégory Mantelet <gregory.mantelet@astro.unistra.fr><br>
<b>Date: </b>Wednesday, 6 May 2020 at 21:30<br>
<b>To: </b>Grid and Web Services WG <grid@ivoa.net><br>
<b>Cc: </b>Grégory ADAM <gregory.adam@etu.unistra.fr><br>
<b>Subject: </b>VOSpace questions<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">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:<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">- min: the returned record for the node contains minimum detail<br>
with all optional parts removed – the node type should be re-<br>
turned<o:p></o:p></p>
</blockquote>
</blockquote>
<p class="MsoNormal"> 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:<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">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.<o:p></o:p></p>
</blockquote>
</blockquote>
<p class="MsoNormal"> 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><span style="font-size:10.0pt"><a href="http://server.example.com/vospace/nodes/mydir?detail=min&">http://server.example.com/vospace/nodes/mydir?detail=min&</a><b>uri=vos://example.com!vospace/mydir/file3401</b></span></tt><b><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><span style="font-size:10.0pt">curl -v <a href="http://server.example.com/vospace/nodes">
"http://server.example.com/vospace/nodes"</a></span></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 href="https://vospace.esac.esa.int/vospace/">https://vospace.esac.esa.int/vospace/</a>)<br>
- CADC/Canfar (<a href="https://www.canfar.net/storage/list/">https://www.canfar.net/storage/list/</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>
<br>
<o:p></o:p></p>
</div>
</body>
</html>