VOSpace 1.1

Hi,

With VOSpace 1.0 in its RFC phase now, the time has come to start thinking seriously about VOSpace 1.1.

VOSpace 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^? <http://www.ivoa.net/twiki/bin/edit/IVOA/LinkNode?topicparent=IVOA.VOSpace11Spec>
  • this is like a Node but also has a URI to where the link is pointing
• ContainerNode^? <http://www.ivoa.net/twiki/bin/edit/IVOA/ContainerNode?topicparent=IVOA.VOSpace11Spec>
  • 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

I have posted this also to the VOSpace 1.1 discussion page (http://www.ivoa.net/twiki/bin/view/IVOA/VOSpace11Spec). I would like these to be resolved by the end of the IVOA in September so that we can produce a Working Draft specification in early October. If you have any thoughts on the above then please post them to this mailing list and the discussion page.

    Cheers,

    Matthew Received on 2007-07-26Z00:33:13