Registry Data Model?

[Tony Linde]

Dear Skeptical of Pasadena,

While I'd agree that the generic resource might be able to represent
miscellaneous whims, they won't be able to be used to do any work. Only if a
user actually eyeballed them and figured out what they were could they then
be used. A portal which is presenting a list of data collections to a user
would not pull out something just described as 'resource'. That's why we've
got the subsidiary schemas available now. The modeling will simply extend
that to allow us to represent what we know more accurately and in a way that
makes automated access easier.

Cheers,
Aunt Dottie.

> -----Original Message-----
> From: Matthew J. Graham [mailto:mjg at cacr.caltech.edu] 
> Sent: 09 December 2004 19:22
> To: Tony Linde
> Cc: registry at ivoa.net
> Subject: Registry Data Model?
> 
> Hi,
> 
> Do we really need to waste effort on defining a registry data 
> model? I always thought that the whole point was that a 
> registry could hold anything - a resource - and that it was 
> at the whim of the resource provider to provide the 
> appropriate metadata description for their resource type. 
> Obviously for common resources, there might be some 
> standardization - the metadata might be agreed upon by a 
> group of interested parties.
> 
> 	Skeptical of Pasadena
>