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?


  • 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


  • Do we want this operation?


  • Do we need both a LinkFound and a ContainerNotFound exception or does the latter work for both cases?


  • Are wildcards allowed in the property URIs - find me all nodes where any property matches this regular expression?


  • 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.

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r2 - 2008-02-05 - MatthewGraham
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback