VOSpace home page
VOSpace  1.1 specification
 Discussion of the VOSpace 1.1 specification 
This is a discussion page for the VOSpace 1.1 service specification.
 VOSpace data model 
 
-  Should capabilities only exist on the ContainerNode?
 
 
 Inheritable properties 
 
-  If a property is also declared on a child, which value takes priority? 
  -  How are properties registered as inheritable?
 
 
 Container views 
 
-  What are the names of the children nodes (for a container format  that is imported to a container node)?
  -  Are the children nodes Structured_/_UnstructuredDataNodes?
  -  What is the default and is this settable?
  -  How does the service identify what it considers to be archive formats?
 
 
 Capabilities 
 
-  What members other than uri and endpoint should a Capability have, e.g. param to specify additional arguments that might be required for access?
 
 
 Web service operations 
 getCapabilities 
 
-  Do we want this operation?
 
 
 createNode 
 
-  Do we need both a LinkFound and a ContainerNotFound exception or does the latter work for both cases?
 
 
 findNodes 
 
-  Are wildcards allowed in the property URIs - find me all nodes where any property matches this regular expression?
 
 
 pushToVoSpace 
 
-  If a Node already exists at the target URI and it is a ContainerNode, should it be overwritten by the target Node or should the target Node become a chld of the ContainerNode? This also applies to pullToVoSpace.