Re: VOSpace WSDL

From: Paul Harrison <pharriso-at-eso.org>
Date: Wed, 14 Jun 2006 15:59:23 +0200

On 14.06.2006, at 12:17, Guy Rixon wrote:

>>> 6. VOSpaceResponse: where do the message and status elements come
>>> from? I
>>> can't see them in spec for, e.g., deleteNode, for which the
>>> response message is a VOSpaceResponse. If we're going to have a
>>> VOSpaceResponse (and I'd prefer a named response message for each
>>> operation,
>>> for symmetry), then it should be an empty type.
>> A deliberate ploy to provoke such a response - I too think that some
>> sort of status message would be more generally useful in other
>> operations - this sort of thing did exist in VOStore, but then got
>> replaced in many operations by a VOSpaceNode as a return value - so
>> yes I think that both a VOSpaceNode and a VOSpaceResponse would be
>> appropriate in many cases - however, I am unclear about what you mean
>> by an empty type...
>
> Empty type instantiated like this <VOResponse/> and enforced to be
> that way
> in schema: written as a xsd:ComplexType with no children IIRC.

Still confused - if it has no content - what is the purpose? Received on 2006-06-14Z15:59:52