Authority resource class

[Tony Linde]

Hi Ray,

Problem with this is that an authority need not be owned by an organisation.
It could be a person, a project etc. or it could be no-one - it might simply
be the default for that registry. Adding Authority to all of these would
make it difficult to find. 

Also, we can mandate that every registry must replicate Authority and
Registry resources but not Organisation, Person, Project etc.

Cheers,
Tony. 

> -----Original Message-----
> From: owner-registry at eso.org [mailto:owner-registry at eso.org] 
> On Behalf Of Ray Plante
> Sent: 01 October 2003 08:56
> To: registry at ivoa.net
> Subject: Authority resource class
> 
> 
> Hi Tony,
> 
> I've been playing with the Authority resource class with our modified 
> structure, and I'm wondering if we need to register AuthorityIDs as 
> separate resources.
> 
> A possible alternative is to have the AuthorityIDs listed as 
> metadata of 
> the Organization that owns them.  
>   Advantages:  
>    +  simpler: when multiple authIDs folded into the Organization 
>       description, there's less information to provide when 
> registering a 
>       new authID.
>    +  use of xsi:nil="true" is not needed (otherwise, the Authority 
>       description must use the xsi:nil in the its 
> Identifer/ResourceKey). 
>       It allows us to be hard-nosed about requiring a 
> ResourceKey with an 
>       identifier in all cases (by removing nillable="true").  
> 
>   Disadvantages:
>    -  Must update the Organization description with each new authID 
>       "registered".  ??
> 
> thoughts?
> 
> cheers,
> Ray
> 
>