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.

---

---

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

This is the main section for schema and WSDL files.

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

Change Requests

Rename bulk data transfer operations

• 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

old name	new name"
pushDataToVoSpace	importDataClientPush
pullDataToVoSpace	importDataServerPull
pushDataFromVoSpace	exportDataServerPush
pullDataFromVoSpace	exportDataClientPull

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

Votes

name	vote	comment
PaulHarrison	+1
MatthewGraham	0

Use namespaces in release candidates that include release number

Votes

name	vote	comment
PaulHarrison	-1
DaveMorris	+1
GuyRixon	+1
MatthewGraham	+1

Make sure that the naming of operations/parameters more closely matches the written specification

Votes

name	vote	comment
PaulHarrison	+1
DaveMorris	+1
GuyRixon	+1
MatthewGraham	+1

Remove enumerations for security related types

Votes

name	vote	comment
GuyRixon	+1
PaulHarrison	+1

Remove enumerations of transport keys

Votes

name	vote	comment
GuyRixon	+1
PaulHarrison	+1	iff this issue is better specified in the standard document

Remove enumerations of parameter key values

Votes

name	vote	comment
GuyRixon	+1
PaulHarrison	+1	iff this issue is better specified in the standard document

Remove any idea of callbacks

Votes

name	vote	comment
PaulHarrison	+1	iff this issue is better specified in the standard document
GuyRixon	+1

Remove the use of ChangeOwner operation

Votes

name	vote	comment
PaulHarrison	0	we do want this concept in 2.0 definitely and 2.0 servers are supposed to be able to talk to 1.0 servers - if we remove it now, we need to have a 1.1 release that does have different WSDL - however if we accept that 1.1 could have different WSDL then it can be dropped from 1.0.
MatthewGraham	+1

Keep Transports/Formats as separate opertation

Keep new GetPropertyKeys operation

not in the spec and an idea that I have had basically because I am still a little worried about interoperability problems with the completely untyped nature of the property-key pairs - particularly as they are expected to carry some fundamental metadata about the data objects in the current implementation. This call would return the complete list of key names that have been used in the VOSpace, which would then allow clients to attempt to be consistent in the use of key names - it is not much but at least it does provide a mechanism to voluntarily avoid complete anarchy.

Votes

name	vote	comment
PaulHarrison	+1
DaveMorris	+1
GuyRixon	+1
MatthewGraham	+1

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

Add new createTempNode operation

related to refactoring use of DataObjectReference - still need a way to "support server generated name" use case.

Consider use of Status responses for some operations