<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font size="+1">"We strongly recommend receiving LIGO/Virgo
alerts in the VOEvent XML format."</font></p>
<p><font size="+1">And early efforts by this IVOA WG reached out to
most/all other astronomical transient alert communities. Many of
these continue to bear fruit in fulfilling the original IVOA /
NVO vision of a single event protocol to rule them all:</font></p>
<p><font size="+1">
<a class="moz-txt-link-freetext" href="http://online.kitp.ucsb.edu/online/grbtu_c06/bloom/oh/21.html">http://online.kitp.ucsb.edu/online/grbtu_c06/bloom/oh/21.html</a></font></p>
<p><font size="+1">On the other hand, two major groups are pursuing
divergent formats. JPL and the Minor Planet Center, via the IAU,
have created the Astrometric Data Exchange Standard (ADES),
another XML standard. And ZTF is prototyping AVRO/JSON alerts
with the notion that these will become the de facto LSST
standard. Indeed ZTF and LSST will also submit moving object
alerts / astrometry using ADES (if not the 1992 IAU 80-column
standard), and will each have to support two standards.<br>
</font></p>
<p><font size="+1">This WG has long had the notion of a network of
brokers bridging across to multiple communities with diverse
formats and transport standards. The only thing of note here is
that all three of these standards are IAU standards (</font><font
size="+1">IVOA is governed through IAU Comm B2):</font></p>
<p><font size="+1"> <a class="moz-txt-link-freetext" href="https://www.xkcd.com/927/">https://www.xkcd.com/927/</a><br>
</font></p>
<p><font size="+1">There had been some earlier discussion of the
JSON standard growing out of VOEvent, indeed becoming VOEvent
v3.0. To what extent has the VOEvent data model been preserved?
VOEvent v1 was successfully translated into JSON a dozen years
ago. The ADES data model is quite simple in structure and could
itself be represented in VOEvent. (This WG did engage with the
moving object domain at the time.) </font><font size="+1"><font
size="+1">XML and JSON are largely isomorphic.</font></font></p>
<p><font size="+1">Hot-wiring the Transient Universe VI will be held
at Northwestern University from August 19-22, 2019:</font></p>
<p><font size="+1"> <a class="moz-txt-link-freetext" href="http://hotwireduniverse.org">http://hotwireduniverse.org</a></font></p>
<p><font size="+1">The time is ripe to re-engage with the
interoperability issues in particular, and with operational
projects such as Gaia, as well as LSST, NEOCam, and other future
surveys.<br>
</font></p>
<p><font size="+1">Rob Seaman, Catalina Sky Survey</font></p>
<p><font size="+1">--<br>
</font></p>
<div class="moz-cite-prefix">On 12/14/18 3:25 AM, Roy Williams
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:A44BF53AA08AE04889395D4D1A5797B1A8AF02@MERCURY.roe.ac.uk">
<pre class="moz-quote-pre" wrap="">As many of you know, there is great excitement in the entire astronomical community about the start of O3, the next LIGO-Virgo observing run, in early 2019 [1]. For the first time, gravitational-wave alerts will be released rapidly, to the public, for electromagnetic followup.
Perhaps less well known is that the primary mechanism for that release [2] is through VOEvent, an IVOA protocol. Let us congratulate ourselves, this is a success story for the IVOA!
Roy Williams
[1] <a class="moz-txt-link-freetext" href="https://www.ligo.caltech.edu/page/observatory-status">https://www.ligo.caltech.edu/page/observatory-status</a>
[2] <a class="moz-txt-link-freetext" href="https://emfollow.docs.ligo.org/userguide/content.html">https://emfollow.docs.ligo.org/userguide/content.html</a>
---
Royal Observatory Edinburgh
<a class="moz-txt-link-abbreviated" href="mailto:roy@roe.ac.uk">roy@roe.ac.uk</a>
07542 869986
</pre>
</blockquote>
</body>
</html>