vospace - by subject
- 1.0rc1 WSDL issues
- 1.0rc1 WSDL issues (change requests)
- 1.0rc1 WSDL issues (create node params)
- 1.0rc1 WSDL issues (DIME and MTOM)
- 1.0rc1 WSDL issues (GetPropertyKeys)
- 1.0rc1 WSDL issues (Transports/Formats)
- 1.0rc1 WSDL issues - asynchronous calls
- 1.0rc1 WSDL issues [DIME vs. MTOM]
- [Fwd: Changes to VOSpace specification]
- Amazon VOStore?
- Amazon VOStore? - no its like a VOSpace...
- Changes to VOSpace specification
- Changes to VOSpace specification (properties)
- Changes to VOSpace specification]
- Corrections to the VOSpace specification
- Document promotions
- ESO VOSpace Pilot installation ready for Interoperability testing
- Exceptions missing text
- Fwd: Amazon VOStore?
- Import behaviour to StructuredDataNodes
- Java VOSpace implementation
- list setup
- Listing question
- Logical storage units in VOSpace 1.1
- Mandatory transports for VOSpace - why not?
- MTOM and Python
- Open Source Storage Management Project
- Optional elements with listing
- Refactored VOStore document
- remarks about VOSpace level 1
- Status of VOspace specification
- Test
- version 1.0rc2 of VOSpace WSDL
- VOSpace 1.1
- VOSpace 1.1 changes
- VOSpace 1.1 reference implementation
- VOSpace 1.1 specification
- VOSpace 1.1 Working Draft
- VOSpace 1.x session at Beijing
- VoSpace functional spec
- VOSpace operation names
- VoSpace progress (fwd)
- VOSpace property registration
- VOSpace URIs
- VOSpace Usage Note 0.1
- VOSpace users
- VOSpace WSDL
- VOSpace-1.0 schema
- VOStore as WS-Resource
- VoStore current status
- VOStore interface
- VOStore/VOSpace use cases
- Why not use Amazon S3?