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.

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

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

1. VOSpace-v1.0.wsdl the main WSDL file.
2. VOSpaceBase-v1.0.xsd a subsidiary schema file that contains core types that might be useful in implementing a VOSpace server cf. the WSDL which contains types that are used only in the web service interface.

These file are packaged in a zip file which is named with the release candidate number for each sucessive release candidate. The exact release candidate number is also reflected in the files in

• the version attribute of the top level xsd:schema element in the schema file
• the name attribute of the top level wsdl:definitions element in the WSDL file

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'.

• I stilll find the data transfer operations confusing- I think that the basic problem is that the push and pull verbs are opposite in meaning and viewed from opposite perspectives. I have a new set of proposals

which I think are better because

1. the overall objective of the operation is the first verb
2. the active party in the transfer is identified
3. the direction of the transfer is then related to the active party.

-- PaulHarrison - 13 Jun 2006

Experiments

version-mg.01

[link]

version-dm.01

• Using separate namespaces for each schema file maps well to Java packages. Using separate schema files for the base node type and derived types makes it much easier to add new extension types later.

Astrogrid.VoSpace20060602

-- DaveMorris - 12 Jun 2006

version-dm.02

• Defining everything as complexType maps well to Java classes - it forces code generators to create full Java classes for all of the elements.
• Defining the messages types outside the main WSDL file may make it easier to to create JUnit tests, and possibly experiment with different transport mechnisms.

Astrogrid.VoSpace20060605

-- DaveMorris - 12 Jun 2006

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->