VOSpace-1.0 WSDL and schema

This is a discussion page for the WSDL and schema for the VOSpace-1.0 service.

This is somewhere where we can post proposals for schema and WSDL to enable interested parties to discuss the different versions.

For each version there is a Change request section - please add to this and vote on other suggestions

• +1 if you agree
• -1 if you disagree
• 0 if you have no particular preference

Once we have finalised the WSDL and schema, the final versions will be posted on the main Grid & Web Services page.

The experiments that were on this page have been moved

News

• Mailing list for discussions of VOStore and associated protocols: vospace@ivoa.net
  Messages archive: http://ivoa.net/forum/vospace/

• Schema discussion page created.

Core schema

The files for the 1.0 VOSpace release are

• VOSpaceContract-v1.0rc4.wsdl the service WSDL contract
• VOSpaceTypes-v1.0rc4.xsd the XSD schema file containing the XML type definitions.

Version 1.0rc4

• VOSpace-v1.0rc4.zip: Updated to rc4

Version 1.0rc3

vospace-interface-1.0rc3.zip

This matches v0.22 of the specification document.

Version 1.0rc2

• vospace-interface-1.0rc2.zip: vospace-interface-1.0rc2.zip

This release attempts to follow the interface described in version 0.21 of the specification document as closely as possible.

Changes from previous version

• Use namespaces in release candidates that include release number
• Make sure that the naming of operations/parameters more closely matches the written specification
• Remove enumerations for security related types
• Remove enumerations of transport keys
• Remove enumerations of parameter key values
• Remove any idea of callbacks
• Remove the use of ChangeOwner operation

Change Requests

Keep Transports/Formats as separate opertation

-- PaulHarrison - 13 Jun 2006

I agree with adding the new methods. However, this should be changed in the specification first, not the WSDL. Move this to the specification change page.

-- DaveMorris - 16 Jun 2006

Votes

Refactor use of DataObjectReference

This construct was there principally to get round difficulties in specifying the use-case "create a file with a server generated name" before the vos: URI scheme was approved. Not needed any more.

-- PaulHarrison - 16 Jun 2006

Needs to be much clearer what this represents.

-- DaveMorris - 16 Jun 2006

Consider use of Status responses for some operations

Changing the method signatures to return status codes should be defined in the specification first, not the WSDL. Move this to the specification change page.

-- DaveMorris - 16 Jun 2006

Votes

Include WSDL for VO Standard Interfaces

Votes

Version 1.0rc1

• vospace-interface-1.0rc1.zip: vospace-interface-1.0rc1.zip

This is the first 'official' release candidate of the VOSpace interface definition, and is based on version 0.21 of the specification document, though is known not to follow this document exactly, as there are areas still to be finalized for which the WSDL is the best 'source'.