Difference: VoeventWorkshop (1 vs. 2)

Revision 22005-01-20 - SarahEmeryBunn

 
META TOPICPARENT name="IvoaVOEvent"

VOEvent Workshop

April 13 and 14, Pasadena, California

Location:

CACR, California Institute of Technology
Directions

Registration:

Please send email to Roy Williams (roy@caltech.edu).
Added:
>
>

Travel:

A block of rooms has been reserved for the nights of April 12 and 13 at the Caltech Athenaeum, at a room rate of $99/night. To make a reservation, please call the Athenaeum at 626-395-8200 by March 12, 2005, and reference the VOEvent Workshop.

 

Agenda:

  • Define scope and reach a consensus on the semantic content of a discovery/followup message for an immediate sky event. This will be based on the existing draft at the IVOA Twiki.
  • Consideration of serializing such a message into XML components, with re-use of existing schema where relevant.
  • Discussions of the language by which clients could subscribe to a VOEvent server, with fine control over which messages are to be received.
  • Discuassions of database and transport technologies for carrying VOEvent messages.
  • Consideration of how existing systems could have a VOEvent capability.added with maximal functionality and minimal effort.
  • Finding volunteers to set up prototype systems.




<--  
-->

Revision 12005-01-19 - RoyWilliams

 
META TOPICPARENT name="IvoaVOEvent"

VOEvent Workshop

April 13 and 14, Pasadena, California

Location:

CACR, California Institute of Technology
Directions

Registration:

Please send email to Roy Williams (roy@caltech.edu).

Agenda:

  • Define scope and reach a consensus on the semantic content of a discovery/followup message for an immediate sky event. This will be based on the existing draft at the IVOA Twiki.
  • Consideration of serializing such a message into XML components, with re-use of existing schema where relevant.
  • Discussions of the language by which clients could subscribe to a VOEvent server, with fine control over which messages are to be received.
  • Discuassions of database and transport technologies for carrying VOEvent messages.
  • Consideration of how existing systems could have a VOEvent capability.added with maximal functionality and minimal effort.
  • Finding volunteers to set up prototype systems.




<--  
-->
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback