ael at star.le.ac.uk
Thu Dec 9 08:17:57 PST 2004
Thanks for posting that idea, Guy.
This fits in with something I'd been thinking about after the points Paul
raised at Harvard about describing applications. This is the separation of
services from their function. So, several service resources might
instantiate the same application and one service might provide access to
more than one application. The same applies to data services: one service
might provide access to multiple data collections and one collection might
be served up by more than one service.
I guess this is partly a data modeling exercise which would then feed into
our schema but I think we need to get our heads around the entities we need
to identify as separate resources first before we can start modeling them.
(Note: This has no effect on how the resources themselves will be registered
since the structural complexity can be hidden by the interface, much as it
is hidden from the user/admin in AstroGrid when they install a PAL interface
Anyone want to kick off with ideas for resource entities that we need to
identify and access?
> -----Original Message-----
> From: owner-registry at eso.org [mailto:owner-registry at eso.org]
> On Behalf Of Guy Rixon
> Sent: 09 December 2004 15:40
> To: registry at ivoa.net
> Subject: TabularDB resource type
> in AstroGrid we find ourselves in need of a way of
> registering details of tables independently of services.
> Current, prototype practice is rather loose (making it hard
> to write our portal software), so I've suggested a new
> resource-type schema that would tie down the details.
> Please see
> Your comments would be appeciated.
> Guy Rixon gtr at ast.cam.ac.uk
> Institute of Astronomy Tel: +44-1223-337542
> Madingley Road, Cambridge, UK, CB3 0HA Fax:
More information about the registry