<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Dave,<br>
<br>
ok we add this topic to
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<font color="#000066"> the "VOSpace 3.0 or ??" section of the
session<br>
<br>
regards<br>
<br>
André<br>
</font><br>
Le 21/05/14 18:22, Dave Morris a écrit :<br>
</div>
<blockquote
cite="mid:48024c8161dd406b7e50fd15905149b6@metagrid.co.uk"
type="cite">Hiya,
<br>
<br>
A suggestion for the GWS VOSpace session which may help us to move
forward.
<br>
<br>
Rather than framing the discussion as VOSpace vs WebDAV. We would
like to suggest the GWS group look at creating a new VO protocol,
VODAV, designed to meet the requirements for a new generation of
applications.
<br>
<br>
VODAV would be based on the existing 3rd party WebDAV
specification, and work to define any extensions we need to meet
the VO requirements.
<br>
<br>
In terms of service registration, a service could register its
WebDAV capability using a std: capability URI to represents the
WebDAV protocol, and its VODAV capability using a std: capability
URI which represents the VODAV protocol.
<br>
<br>
In addition, if required, we could define two new URL prefixes,
'dav:' for resources in a standard WebDAV service and 'vodav:'
could be used to refer to resources in a VODAV service.
<br>
<br>
<br>
Hope this helps,
<br>
Dave
<br>
</blockquote>
<br>
</body>
</html>