(r26) VOSpace10Spec < IVOA

IVOA Web>IvoaGridAndWebServices>VOSpace10Spec (revision 26) (raw view)~~EditAttach~~

---+ Discussion of the VOSpace 1.0 specification Document


This is a discussion page for the VOSpace-1.0 service specification document.

This is somewhere where we can post proposals and to enable interested parties to discuss the different versions.

For each version there is a Change request section - please add to this and vote on other suggestions
   * +1 if you agree
   * -1 if you disagree
   * 0 if you have no particular preference

Details and discussion of implementation plans are [[VOSpace10Impl][here]].

---
%TOC%
---
---+ Version 0.22
   * [[http://www.ivoa.net/internal/IVOA/IvoaGridAndWebServices/vospace-0.22.doc][vospace-0.22.doc]]

This document was produced as a result of the discussions that have occured since the Victoria Interop meeting.

---++ Change Requests

---+++ Make the destination of <nop>CopyNode and <nop>MoveNode a simple uri

The advantage is it simplifies the standard doc (so many restrictions on node) and is much easier for client to use... as does not have to  create a node object - simply create a uri for the destination.

---++++ Votes
| *name* | *vote*| *comment* |
| IVOA.PaulHarrison | +1 |proposer|

---+++ Re-assess what metadata should be returned with various faults

Some faults need to return metadata beyond simply their type to convery meaningful information about exactly what has gone wrong. e.g. for a setDataNodeProperties call could specify several read-only properties amongst a larger number of properties, and the client would not know which were the properties in error without a list being returned in the fault.

---++++ Votes
| *name* | *vote*| *comment* |
| IVOA.PaulHarrison | +1 |proposer|
| IVOA.GuyRixon | +1 | |


---+ Version 0.21
   * [[http://www.ivoa.net/internal/IVOA/IvoaGridAndWebServices/vospace-0.21.doc][vospace-0.21.doc]]

This document was produced as a result of the discussions that occured at the Victoria Interop meeting.

---++ Changes
[[VOspace10Spec21Archive]]

---+ Changes for later versions of VOSpace

---+++ Consider adding an optional wildcard matching identifier to parameters for ListNodes
This would allow the client to specifly a subset of the VOSpace to be listed - in effect the behaviour would be similar to the "ls" command in unix, with typical simle shell wildcard semantics. 

Reason for change: improved efficiency - if ListNodes always has to list the _whole_ VOSpace then it is a pretty blunt instrument, especially as the number of data objects in the space increases.


---++++ Use Case
Suppose that there is a 1.0 VOSpace containing 5000 data items and a workflow step is writing results into the VOSpace using a common prefix. The next step in the workflow wants to process all of the files produced, but only knows the prefix - without wild card matching the whole of the VOSpace needs to be listed to find the files.

-- IVOA.PaulHarrison 19 Jun 2006

---++++ Votes
| *name* | *vote*| *comment* |
| IVOA.PaulHarrison | +1 |proposer|
_*Result*_:  consider for later version

---+++ Add a <nop>FindNodes operation

This operation would allow a simple search on the VOSpace - the level of functionality would be similar to the unix "find" command.
<br/>
<!--
      * Set ALLOWTOPICRENAME = %MAINWEB%.TWikiAdminGroup
-->

Topic revision: r26 - 2006-07-20 - PaulHarrison

IVOA

Log in or Register

IVOA.net
Wiki Home
WebChanges
WebTopicList
WebStatistics

Twiki Meta & Help
IVOA
Know
Main
Sandbox
TWiki

TWiki intro
TWiki tutorial
User registration
Notify me

Working Groups

Interest Groups

Time Domain

Committees

Stds&Procs

www.ivoa.net
Documents
Events
Members
XML Schema