RofR

Tony Linde Tony.Linde at leicester.ac.uk
Tue Apr 12 07:27:56 PDT 2005


>   - a RoR can be created that could be used by an intelligent 
> agent to discover which registries that it wanted to query

How can it decide which registries to query - knowing that a registry exists
and covers certain authorities is meaningless from a query point of view.
You still won't know what resources it contains if it is less than a full
list - if it is a full list you just query it anyway, you don't need any
other registry.

>   - a private "publishing" registry could be supported, by the "full" 
> registry claiming to be the "owner" and the rest of the world 
> would be none the wiser.

Which is why we don't need the managed/owned distinction anymore.

>   - public "publishing" registries (which seem to be desired 
> by the majority on this list) could be supported by the 
> publishing registry acknowledging ownership, so that people 
> know where to go to make updates to records, but not 
> declaring itself to be a "managing" registry for the 
> authorityID, which is a statment that it does not want to 
> service searches.

You've mixed up two concepts. Managing and searching are completely distinct
concepts, neither to do with the other.

We *do* need to distinguish which registries support searching.

And now that people are talking about non-full registries being searchable,
we also need some way of indicating what types of resources are stored by
the registry: currently we're talking about support for various schemas but
I guess a registry could specialise in resources on specific topics as well.

Cheers,
Tony. 

> -----Original Message-----
> From: owner-registry at eso.org [mailto:owner-registry at eso.org] 
> On Behalf Of Paul Harrison
> Sent: 12 April 2005 08:28
> To: Ray Plante
> Cc: registry at ivoa.net
> Subject: Re: RofR
> 
> 
> It seems to me that the most important point from this 
> discussion is that as long as that the concept of Owned and 
> Managed is expressed in the schema (which it is *not* at the 
> moment) then all of the models can be accommodated.
> 
>   - a RoR can be created that could be used by an intelligent 
> agent to discover which registries that it wanted to query
>   - a private "publishing" registry could be supported, by the "full" 
> registry claiming to be the "owner" and the rest of the world 
> would be none the wiser.
>   - public "publishing" registries (which seem to be desired 
> by the majority on this list) could be supported by the 
> publishing registry acknowledging ownership, so that people 
> know where to go to make updates to records, but not 
> declaring itself to be a "managing" registry for the 
> authorityID, which is a statment that it does not want to 
> service searches.
> 
> It is the statement of this last use case that makes the term 
> managed inappropriate to me.
> 
> 
> -- 
> Paul Harrison
> ESO Garching
> www.eso.org
> 



More information about the registry mailing list