Discussion of the VOSpace 1.1 specification

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

Version 1.1 aims to extend the VOSpace-1.0 specification to include links and containers. The proposed mechanism is that we introduce two new node types:

• LinkNode - this is like a Node but also has a URI to where the link is pointing
• ContainerNode - this cannot hold any data (no bytes) but can have children nodes (of any type) and views for container level formatting (aggregate zip/gzip).

At the May 2007 interop, we identified the following items as requiring resolution for VOSpace 1.1:

• Container level metadata - how to distinguish those that relate to the contents of the container through inheritance and those to the container itself
• Generated names - vos://null does not work for containers so use ".auto" or "/" as an alternative
• Typing of protocol and view parameters - these are currently designated as "string" but normal parameters are "URI"
• ACL - although this forms part of a wider SSO context, should VOSpace have some notions of ACL control
• Find - a equivalent to the Unix command is desired

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

Please add your suggestion to this page and vote on other suggestions

• +1 if you agree
• 0 if you think the proposal is useful but needs more work
• -1 if you disagree with the proposal

If you register a 0 or -1 vote, then please add a link to a page outlining your objections or comments.