URLs?

[Ray Plante]

Hi Alasdair,

On Thu, 8 Dec 2005, Alasdair Allan wrote:
> Ray Plante wrote:
> > The previous proposal for the ID had another added benefit.  It
> > recommended that the part before the # refer to the event registry 
> > service
> > that is capable of resolving the identifier to the actual event 
> > message.
> 
> Err, no. This was never the case IMHO...

I just looked more closely at the version I read last week, and indeed  
what I said is not quite correct, but close.  More precisely:

   1.  Sect. 2.1 describes that [in principle] a VOEvent identifier 
       conforming to a legal IVOA ID can use the VO registry framework 
       to "resolve that identifier to the full VOEvent packet".

   2.  Sect. 3.1 gives an example of an ID of the form, 
       ivo://{authority-id}/{resource-key}#{local-id}, which is compliant 
       with the IVOA ID standard.  Everything prior to the #, presumably 
       then, would be in a VO Resource registry.  It does not indicate 
       what that registered resource actually is.  

Allow me to explicitly connect the dots between an event id and its 
packet by recommending that the resource ID point to a (as yet 
undefined) VOEvent service that can resolve the ID to a packet.  That 
would be useful.  

cheers,
Ray