On Sun, 14 Oct 2007, Guy Rixon wrote:
> Similarly, a service presented with a vos:// URL knows it's dealing with
> VOSpace, but it has to go to the registry (or to its cache of registry
> information) to find out which version.
>
> The pattern is that a data URL is either for a data stream or for a service
> that is a generator of data streams, and the only supported cases of the
> latter are MySpace and VOSpace. We can't exchaneg data with an arbitrary SOAPm
> or REST service unless we know its protocol.
So does the vos:// URI tell us the VOSpace service endpoint directly, or do we have to involve the registry to resolve this?
Also, it should be possible to query the VOSpace directly (via getCapabilities or whatever, if not now in a later version) to find out what version of the VOSpace protocol it supports.
Sevices can be used both in a Grid/Internet-based mode and locally; it should not be required to involve a remote Internet-based registry for basic operation of a service.