Drop SkyService?

[Wil O'Mullane]

My initial reaction would be search both - but it does lead to a problem of which you give precedence to.
A service may also have more than one datacollection so you would have to do a combination of coverage from all collections to get the services coverage.
Hence it would seem to lay with the service to answer this question
If however I was searching for collections I would not even look at the service.

Hence I feel it makes sense to have this on both places and to use it as appropriate. Where as appropriate will only become apparent with time.

> > What do we do if a SkyService includes the 'CanQuery' (or whatever)
> > relationship? Do we search both coverage metadata for the SkyService *and*
> > the DataCollection it is related to, or specify that if both are present,
> > only one is searched?
> 
> The short answer is, I'm not sure yet what will make sense in general.  
> 
> There will be some queries where the registry user will have a specific 
> idea of what they are looking for.  For, example, the NVO DIS service 
> looks specifically for cone search and SIA services; thus, it need only 
> query against coverage associated with those services.  
> 
> In the more general case, it's not clear whether it makes sense to just 
> search services, data collections, or both.  (Note that Coverage appears 
> at the same level for both types--hopefully, that's helpful.)  It may 
> depend on whether providers are typically inclined to register data 
> collections themselves or just the services that access them.