Data and services

[Tony Linde]

I'd forgotten about Coverage. Maybe SkyService should stay so that when
solar and stp people create their schemas they can have a SolarService and
STPService.

Maybe we need a DataService which includes a pointer to the root data
collection plus any other data-ish metadata and then SkyService,
SolarService and STPService can inherit from that?

And should Coverage be renamed to SkyCoverage? Or is there enough
commonality between 'coverage' in the disciplines to deal with the
differences with one or two optional elements?

Cheers,
Tony. 

> -----Original Message-----
> From: owner-registry at eso.org [mailto:owner-registry at eso.org] 
> On Behalf Of Ray Plante
> Sent: 12 September 2003 19:49
> To: Robert Hanisch
> Cc: registry at ivoa.net
> Subject: Re: Data and services
> 
> 
> On Fri, 12 Sep 2003, Robert Hanisch wrote:
> > > A sky service is a service which provides access to a data 
> > > collection.
> 
> > I would prefer to not use "sky service" -- not all of astronomy is 
> > about the sky.  (Really!)  For example, we would want 
> collections of 
> > spectral line identifications, oscillator strengths, etc., 
> available 
> > as VO resources as well.  I think the term "data service" 
> is logically 
> > more consistent.
> 
> I'm good with "data service", but I should clarify something.  The 
> "SkyService" resource is distinguished from a generic service 
> in that it 
> has "Coverage".  That is, the data maps somehow to the sky, 
> frequency, 
> and/or time.  So a question is, should a "data service" be 
> defined such 
> that it is *required* to map to at least one of the three?  
> Or should the 
> definition be broader than that, making "Coverage" optional.  
> 
> I like accepting Tony's definition, substituting "sky" with 
> "data", and 
> making "Coverage" optional.  
> 
> cheers,
> Ray
> 
>