May 2020 IVOA Interop Meeting - VOEvent next steps

• When - Wednesday May 06 2020 06:00 UTC [calendar link]
• Where - Zoom session, details available soon.

The current version of the specification VOEvent 2.0

The document source in GitHub.

Session topics

• Changes to the standard
  • Any issues with the PDF generated from the LaTex in GitHub ?
  • Change request from Baptiste Cecconi behalf of the Solar System Interest Group
    • VOEvent-v2.1-proposal.pdf
    • GitHub pull request

• Science cases - how are people using VOEvent
  • Existing use cases
  • Future plans

• Service registration - do we need to register VOEvent brokers ?
  • Brokers broadcasting messages to the public network
  • Brokers sending to small groups of subscribers

• Message types - do we need a standard way of describing message types ?
  • FRB message template as an example

• Message validation - do we need to define a method for validating message contents ?
  • FRB template validation as an example

• Event databases - do we need to standardise the way that we store events in databases ?
  • 4PiSky database
  • FRB event database

• Next generation - do we need to look at new standards for new technologies ?

• • XMPP transport
  • Kafka transport
  • Avro data format
  • JSON data format

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

May 2020 IVOA Interop Meeting - VOEvent next steps

• When - Wednesday May 06 2020 06:00 UTC [calendar link]
• Where - Zoom session, details available soon.

The current version of the specification VOEvent 2.0

The document source in GitHub.

Session topics

• Changes to the standard
  • Any issues with the PDF generated from the LaTex in GitHub ?
  • Change request from Baptiste Cecconi behalf of the Solar System Interest Group

• Science cases - how are people using VOEvent
  • Existing use cases
  • Future plans

• Service registration - do we need to register VOEvent brokers ?
  • Brokers broadcasting messages to the public network
  • Brokers sending to small groups of subscribers

• Message types - do we need a standard way of describing message types ?
  • FRB message template as an example

• Message validation - do we need to define a method for validating message contents ?
  • FRB template validation as an example

• Event databases - do we need to standardise the way that we store events in databases ?
  • 4PiSky database
  • FRB event database

• Next generation - do we need to look at new standards for new technologies ? Is there a strong science case for standardising any of these at the moment ?
  • XMPP transport
  • Kafka transport
  • Avro data format
  • JSON data format

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

May 2020 IVOA Interop Meeting - VOEvent next steps

• When - Wednesday May 06 2020 06:00 UTC [calendar link]
• Where - Zoom session, details available soon.

The current version of the specification VOEvent 2.0

The document source in GitHub.

Session topics

• Changes to the standard
  • Any issues with the PDF generated from the LaTex in GitHub ?

• Science cases - how are people using VOEvent
  • Existing use cases
  • Future plans

• Service registration - do we need to register VOEvent brokers ?
  • Brokers broadcasting messages to the public network
  • Brokers sending to small groups of subscribers

• Message types - do we need a standard way of describing message types ?
  • FRB message template as an example

• Message validation - do we need to define a method for validating message contents ?
  • FRB template validation as an example

• Event databases - do we need to standardise the way that we store events in databases ?
  • 4PiSky database
  • FRB event database

• Next generation - do we need to look at new standards for new technologies ? Is there a strong science case for standardising any of these at the moment ?
  • XMPP transport
  • Kafka transport
  • Avro data format
  • JSON data format

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

May 2020 IVOA Interop Meeting - VOEvent next steps

• Where - Zoom session, details available soon.

The current version of the specification VOEvent 2.0

The document source in GitHub.

Session topics

• Changes to the standard
  • Any issues with the PDF generated from the LaTex in GitHub ?
  • Change request from Baptiste Cecconion behalf of the Solar System Interest Group

• Science cases - how are people using VOEvent
  • Existing use cases
  • Future plans

• Service registration - do we need to register VOEvent brokers ?
  • Brokers broadcasting messages to the public network
  • Brokers sending to small groups of subscribers

• Message types - do we need a standard way of describing message types ?
  • FRB message template as an example

• Message validation - do we need to define a method for validating message contents ?
  • FRB template validation as an example

• Event databases - do we need to standardise the way that we store events in databases ?
  • 4PiSky database
  • FRB event database

• Next generation - do we need to look at new standards for new technologies ? Is there a strong science case for standardising any of these at the moment ?
  • XMPP transport
  • Kafka transport
  • Avro data format
  • JSON data format

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

May 2020 IVOA Interop Meeting - VOEvent next steps

• When - Wednesday May 06 2020 06:00 UTC (ICS)
• Where - Zoom session, details available soon.

The current version of the specification VOEvent 2.0

The document source in GitHub.

Session topics

• Changes to the standard
  • Any issues with the PDF generated from the LaTex in GitHub ?
  • Change request from Baptiste Cecconion behalf of the Solar System Interest Group

• Science cases - how are people using VOEvent
  • Existing use cases
  • Future plans

• Service registration - do we need to register VOEvent brokers ?
  • Brokers broadcasting messages to the public network

• Message types - do we need a standard way of describing message types ?
  • FRB message template as an example

• Message validation - do we need to define a method for validating message contents ?
  • FRB template validation as an example

• Event databases - do we need to standardise the way that we store events in databases ?
  • 4PiSky database
  • FRB event database

• Next generation - do we need to look at new standards for new technologies ? Is there a strong science case for standardising any of these at the moment ?
  • XMPP transport
  • Kafka transport
  • Avro data format
  • JSON data format

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

May 2020 IVOA Interop Meeting - VOEvent next steps

• Where - Zoom session, details available soon.

The current version of the specification VOEvent 2.0

The document source in GitHub.

• Service registration - do we need to register VOEvent brokers ?
  • Brokers broadcasting messages to the public network
  • Brokers sending to subscribers

• Message types - do we need a standard way of describing message types ?
  • FRB message template as an example

• Message validation - do we need to define a method for validating message contents ?
  • FRB template validation as an example

• Event databases - do we need to standardise the way that we store events in databases ?
  • 4PiSky database
  • FRB event database

• Next generation - do we need to look at new standards for new technologies ? Is there a strong science case for standardising any of these at the moment ?
  • XMPP transport
  • Kafka transport
  • Avro data format
  • JSON data format

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

May 2020 IVOA Interop Meeting - VOEvent next steps

• When - Wednesday May 06 2020 06:00 UTC
• Where - Zoom session, details available soon.

The current version of the specification VOEvent 2.0

The document source in GitHub.

Proposed changes to the standard

• Any issues with the PDF generated from the LaTex in GitHub ?
• PR request from Baptiste ...

Topics to discuss

• Service registration - do we need to register VOEvent brokers ?
  • Brokers broadcasting messages to the public network
  • Brokers sending to subscribers

• Message types - do we need a standard way of describing message types ?
  • FRB message template as an example

• Message validation - do we need to define a method for validating message contents ?
  • FRB template validation as an example

• Event databases - do we need to standardise the way that we store events in databases ?
  • 4PiSky database
  • FRB event database

• Next generation - do we need to look at new standards for new technologies ? Is there a strong science case for standardising any of these at the moment ?
  • XMPP transport
  • Kafka transport
  • Avro data format
  • JSON data format

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->