Difference: InterOpMay2020VOEventNextSteps (1 vs. 7)

Revision 72020-05-06 - DaveMorris

 
META TOPICPARENT name="InterOpMay2020"

May 2020 IVOA Interop Meeting - VOEvent next steps

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
Added:
>
>
 
  • 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 ?
Changed:
<
<
Is there a strong science case for standardising any of these at the moment ?
>
>
  • Is there a science case for standardising any of these at the moment ?
 
    • XMPP transport
    • Kafka transport
    • Avro data format
    • JSON data format


<--  
-->
Added:
>
>
 
META FILEATTACHMENT attachment="VOEvent-v2.1-proposal.pdf" attr="" comment="Proposed changes to VOEvent for Solar System Sciences" date="1588718424" name="VOEvent-v2.1-proposal.pdf" path="VOEvent-v2.1-proposal.pdf" size="7989760" user="DaveMorris" version="1"
Added:
>
>
META FILEATTACHMENT attachment="20200506-voevent.pdf" attr="" comment="VOEvent next steps - May 2020" date="1588727687" name="20200506-voevent.pdf" path="20200506-voevent.pdf" size="228095" user="DaveMorris" version="1"
 

Revision 62020-05-05 - DaveMorris

 
META TOPICPARENT name="InterOpMay2020"

May 2020 IVOA Interop Meeting - VOEvent next steps

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
Added:
>
>
 
  • 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


<--  
-->
Added:
>
>
META FILEATTACHMENT attachment="VOEvent-v2.1-proposal.pdf" attr="" comment="Proposed changes to VOEvent for Solar System Sciences" date="1588718424" name="VOEvent-v2.1-proposal.pdf" path="VOEvent-v2.1-proposal.pdf" size="7989760" user="DaveMorris" version="1"
 

Revision 52020-05-05 - DaveMorris

 
META TOPICPARENT name="InterOpMay2020"

May 2020 IVOA Interop Meeting - VOEvent next steps

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 ?
Changed:
<
<
    • Change request from Baptiste Cecconion behalf of the Solar System Interest Group
>
>
    • 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


<--  
-->

Revision 42020-04-30 - DaveMorris

 
META TOPICPARENT name="InterOpMay2020"

May 2020 IVOA Interop Meeting - VOEvent next steps

Changed:
<
<
>
>
 
  • 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


<--  
-->

Revision 32020-04-30 - DaveMorris

 
META TOPICPARENT name="InterOpMay2020"

May 2020 IVOA Interop Meeting - VOEvent next steps

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
Changed:
<
<
    • Brokers sending to subscribers
>
>
    • 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


<--  
-->

Revision 22020-04-29 - DaveMorris

 
META TOPICPARENT name="InterOpMay2020"

May 2020 IVOA Interop Meeting - VOEvent next steps

Changed:
<
<
>
>
 
  • Where - Zoom session, details available soon.

The current version of the specification VOEvent 2.0

The document source in GitHub.

Changed:
<
<
Proposed changes to the standard
>
>

Session topics

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

Topics to discuss

>
>
  • Changes to the standard
Added:
>
>
    • Any issues with the PDF generated from the LaTex in GitHub ?
    • Change request from Baptiste Cecconion behalf of the Solar System Interest Group
 
Added:
>
>
  • 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 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
Deleted:
<
<

 
<--  
-->

Revision 12020-04-29 - DaveMorris

 
META TOPICPARENT name="InterOpMay2020"

May 2020 IVOA Interop Meeting - VOEvent next steps

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


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