Discussion page for the VOSpace 3.0

This is a discussion page for future enhancements and changes to VOSpace 2.1

Please edit this page directly to add comments or specification changes and additions.

Notes / Ideas

• In the transfer object, the 'direction' can conflict with the protocol URI. For example, the direction can be 'pullFromVoSpace' and the protocol can be 'HTTP-PUT'. This could be cleaned up to remove error cases.
• Should VOSpace should have it's own registry extension, VoSpaceRegEx?
• Section 4, Access Control: Version 3.0 should state access control policies at the Node level?
• Custom views: views that clients create and use to do work/data reduction at the physical storage location.
• JPEG2000 Interactive Protocol (JPIP) and VOSpace?

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Discussion page for the VOSpace 3.0

This is a discussion page for future enhancements and changes to VOSpace 2.1

Please edit this page directly to add comments or specification changes and additions.

Notes / Ideas

• In the transfer object, the 'direction' can conflict with the protocol URI. For example, the direction can be 'pullFromVoSpace' and the protocol can be 'HTTP-PUT'. This could be cleaned up to remove error cases.
• Should VOSpace should have it's own registry extension, VoSpaceRegEx?
• Section 4, Access Control: Version 3.0 should state access control policies at the Node level?
• Custom views: views that clients create and use to do work/data reduction at the physical storage location.
• JPEG2000 Interactive Protocol (JPIP) and VOSpace?

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->