International Virtual Observatory Alliance

Difference: VOSpace10schema (5 vs. 6)

Revision 62006-06-16 - PaulHarrison

META TOPICPARENT	name="IvoaGridAndWebServices"

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.

Added:

>
>

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.

Changed:

<
<

Core schema

>
>

Core schema

This is the main section for schema and WSDL files.

The files for the 1.0 VOSpace release are

VOSpace-v1.0.wsdl the main WSDL file.
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

Changed:

<
<

Version 1.0rc1

>
>

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

Added:

>
>

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

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

-- PaulHarrison - 13 Jun 2006

Added:

>
>

Votes

name	vote	comment
PaulHarrison	+1

Changed:

<
<

Experiments

moved to separate page This section is for experiments and examples. Schema posted here are examples of techniques and styles that may me useful in the main schema.

>
>

Use namespaces in release candidates that include release number

Votes

name	vote	comment
PaulHarrison	-1

Changed:

<
<

version-mg.01

An experimental schema, looking at how SOAP overriding works, and if it would be useful for adding VOSpace-2.0 functionality to a VOSpace-1.0 service.

>
>

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

Votes

Added:

>
>

name	vote	comment
PaulHarrison	+1

Changed:

<
< [link]

>
>

Remove enumerations for security related types

Added:

>
>

Votes

name	vote	comment
PaulHarrison	+1

Changed:

<
<

version-dm.01

An experimental schema, splitting things up into small schema files.

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.

>
>

Remove enumerations of transport keys

Votes

name	vote	comment

Added:

>
>

PaulHarrison

iff this issue is better specified in the standard document

Changed:

<
< Astrogrid.VoSpace20060602

>
>

Remove enumerations of parameter key values

Added:

>
>

Votes

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

Changed:

<
< -- DaveMorris - 12 Jun 2006

>
>

Remove any idea of callbacks

Added:

>
>

Votes

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

Deleted:

<
<

version-dm.02

An experimental schema, using compleType for all of the elements, and moving as much as possible out of the main WSDL file.

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.

Changed:

<
< Astrogrid.VoSpace20060605

>
>

Remove the use of ChangeOwner operation

Changed:

<
< -- DaveMorris - 12 Jun 2006

>
>

Added:

>
>

<-- 
 
 
 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

META FILEATTACHMENT	attr="" comment="vospace-interface-1.0rc1.zip" date="1150212841" name="vospace-interface-1.0rc1.zip" path="vospace-interface-1.0rc1.zip" size="7450" user="PaulHarrison" version="1.1"

View topic | History: r25 < r24 < r23 < r22 | More topic actions...