roadmap

[Tony Linde]

Thanks Bob & Ray (great double act!).

The question is: what is in the registry? A) does it conform to the schema?
B) what records does it contain?

If we added an AstroGrid datacentre service, would it know that this service
needed to be invoked using the SkyService methods using ADQL v0.8.1 (or
whichever version we're using in AstroGrid at the moment)? And if not, would
it recognise that it could not use this service even if it found it via the
registry query criteria?

Also, given the results:

   Images (FITS/GIF)
Optical 		DSS1 SV
X-ray 		RASS B
   Observations (VOTable)
Optical 		HST(100)
Radio 		NCSA ADIL(9)
X-ray 		ROSAT(2) 		ROSPUBLC(2)
UV 			Copernicus(2) 		EUVE(3)
FUSE(4)
   Objects (VOTable)
Surveys 		USNO-A2.0(3) 		GSC1(88)
GSC2.2(649)
Stars 		HIP(1) 

Which registry fields are being used to make the above subdivisions?

> -----Original Message-----
> From: owner-registry at eso.org [mailto:owner-registry at eso.org] 
> On Behalf Of Ray Plante
> Sent: 10 March 2004 14:24
> To: registry at ivoa.net
> Subject: RE: roadmap
> 
> On Wed, 10 Mar 2004, Tony Linde wrote:
> > Has the NVO project (or anyone else) built or prototyped any way in 
> > which users can submit a registry query (in whatever form) and have 
> > the resultant services (even if only data services) 
> automatically invoked?
> 
> The NVO Data Invetory service
> (http://heasarc.gsfc.nasa.gov/vo/data-inventory.html) does 
> just this.  
> Given a position in the sky, the registry is queried via a 
> web service requesting SIA and ConeSearch services.  These 
> are then invoked to determine what data is available at the 
> given position.
> 
> > - including
> > AstroGrid data services, VizieR services etc? 
> 
> In theory, there is sufficient metadata to query 
> GLU-registered services, but we have not yet tested this.  We 
> also could, in principle, automatically invoke traditional, 
> arbitrary GET HTTP services; how practical this is depends on 
> the how sufficiently describable the output is.  Web services 
> can also be registered; accessing these should be trivial, 
> but we don't have an demonstration involving the registry, yet.  
> This will likely change this spring with the growing work on 
> SkyNode.  
> 
> Do AstroGrid services fall into any of the above catagories?  
> Part of automatically invoking a service effectively is 
> making use of the Capability metadata, which (as you recall) 
> are specific for a particular type of "standard" service.  
> You could consider defining a set of capability metadata for 
> AstroGrid services, similar to SIA-v0.X.xsd and ConeSearch-v0.X.xsd.
> 
> > If so, can you point us to it
> > - would help to be able to see how this works.
> 
> I think we can provide more information about how DIS uses 
> the resource metadata to choose and invoke its service if 
> need be.  I don't know if these specifics are published 
> anywhere at the moment.  
> 
> cheers,
> Ray
> 
>