2-stage identifier resolution

[Gretchen Greene]

Thanks for the clarification Roy,  this sounds very reasonable.
 
If you want a starting place i would direct you to the instance examples
here
 
http://www.ivoa.net/twiki/bin/view/IVOA/VOResourceV010#The_Schemas
 
One example that may be relevant is the collection.xml.  If you can't
find a good fit for VOEvent metadata elements then perhaps an extension
is the way to go.  I wrote an extension for an OpenSkynode that modeled
the registry standard SIAP/Cone schema for a similar situation with
skynode registration.  There is nothing prohibiting this,  but if you
have more specific requirements for the descriptions ironed out,  it's
timely with the next major upgrade of the Registry schema antipated a
couple months following the May IVOA interop.  This way it may be more
uniformly exchanged to the community.
 
Goodluck.
 
-Gretchen
 
-----Original Message-----
From: owner-registry at eso.org [mailto:owner-registry at eso.org] On Behalf
Of Roy Williams
Sent: Friday, April 21, 2006 11:25 AM
To: Gretchen Greene
Cc: registry at ivoa.net; 'Ray Plante'; Roy Williams; 'Norman Gray'
Subject: Re: 2-stage identifier resolution



On Apr 21, 2006, at 7:23 AM, Gretchen Greene wrote:


Does this mean each event is registered
or is there a resource with a collection of events?
I'm assuming since we've got to the detail of resolving uri's that it is
the former. 



My idea is that the VOEventRepository is registered with each IVOA
registry. There are currently four of these planned or operational
(Exeter, Los Alamos, Tucson, Pasadena). The VOEventRepository will thus
need a schema for its description (what types of events, who is in
charge, etc). I wish I knew how to start making such a schema. Should I
somehow "extend" the registry schema, or should I start with a blank
canvas?

The VOEventRepository itself will also need to respond to queries (an
interface). Queries like "Please resolve this event ID", and "Please run
this Xquery against your event database", and "Please subscribe me for
Swift events". This interface should be standard across the four
repositories. I wish I knew how to start making such an interface.
Should I somehow "extend" the registry interface, or should I start with
a blank canvas?


California Institute of Technology
626 395 3670


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ivoa.net/pipermail/registry/attachments/20060421/985c2fc8/attachment-0001.html>