More separation

[Tony Linde]

> Perhaps this is a separate deal from the 
> resource/service/interface discussion but often a question 

This is exactly the deal, Gretchen.

We're talking about registering an application made up of one or more
functions and then the AppService which makes that application available has
one or more interfaces (i.e. is available as cgi, web service etc.). Once
we've got an idea of the broad structure we can start defining the what
elements make up a Function, an Application, an AppService.

Cheers,
Tony. 

> -----Original Message-----
> From: Gretchen Greene [mailto:greene at stsci.edu] 
> Sent: 21 December 2004 20:17
> To: 'Ray Plante'; 'Tony Linde'
> Cc: registry at ivoa.net
> Subject: RE: More separation
> 
> Okay not to throw a wrench in here,  but another thing I get 
> questioned about regularly is how does one fine an analytical 
> resources/tool/etc.
> Like now we have at the  one ST registry site a pointer to 
> client resources (very limited set) separate.  This has been 
> discussed many times abstractly,  and since there is such a 
> limited set not too much of a pressing point.  
> 
> Are there plans to 'register' and characterize tools and if 
> so are they services,  interfaces (probably not), and where 
> does the line get drawn between apps/clients and such things?
> 
> Perhaps this is a separate deal from the 
> resource/service/interface discussion but often a question 
> we've received from registry users.
> 
> -Gretchen
> 
> -----Original Message-----
> From: owner-registry at eso.org [mailto:owner-registry at eso.org] 
> On Behalf Of Ray Plante
> Sent: Friday, December 17, 2004 5:27 PM
> To: Tony Linde
> Cc: registry at ivoa.net
> Subject: RE: More separation
> 
> 
> On Fri, 17 Dec 2004, Tony Linde wrote:
> > > sub-type: ConeSearch, SimpleImageAccess, SkyNode.  Thus, 
> if you have 
> > > a catalog that has both Cone Search and SkyNode 
> interfaces accessing 
> > > it, it is not possible to describe both those interfaces 
> in a single 
> > > record.
> > 
> > I would classify the ConeSearch, SimpleImageAccess & SkyNode as 
> > separate services. An interface is where a ConeSearch can 
> be invoked 
> > both through cgi and web service interfaces.
> 
> Okay, this is a pretty good cut.  The different interfaces 
> provide access to the same logical functionality.  The 
> service, then, is defined by its
> 
> behavior and some abstract description of its inputs and 
> outputs.  In specific terms, different services will be 
> described by different "capability" metadata.  This is all 
> consistant with the current XML schemas.  
> 
> > Is this a fair description of reality?
> 
> I think so.
> 
> cheers,
> Ray
> 
> 
>