<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>Hi Roy,</div><div><br></div><div>here are a few links to the IVOA wiki where you will find material for the case we have been raising. I’ll prepare a cleaner document in the coming days.</div><div><br></div><div><a href="http://wiki.ivoa.net/internal/IVOA/InterOpMay2017-TD/lesidaner_interop_voevent.pdf">http://wiki.ivoa.net/internal/IVOA/InterOpMay2017-TD/lesidaner_interop_voevent.pdf</a></div><div><br></div><div><a href="http://wiki.ivoa.net/twiki/bin/view/IVOA/InterOpMay2017-TD-001">http://wiki.ivoa.net/twiki/bin/view/IVOA/InterOpMay2017-TD-001</a></div><div><br></div><div><a href="http://wiki.ivoa.net/internal/IVOA/InterOpOct2017TDIG/lesidaner_interop_voevent.pdf">http://wiki.ivoa.net/internal/IVOA/InterOpOct2017TDIG/lesidaner_interop_voevent.pdf</a></div><div><br></div><div>Sincerely </div><div>Baptiste </div><div><br></div><div>Le 2 nov. 2017 à 16:59, Roy Williams <<a href="mailto:roy@roe.ac.uk">roy@roe.ac.uk</a>> a écrit :<br><br></div><blockquote type="cite"><div><span>Hi Baptiste</span><br><span>I find it difficult to understand what is being proposed from this list of changes, since I was not present at the discussions. Is there a presentation or document that explains what you are trying to achieve, and how your proposed changes achieve your goals? Have you considered using the VOEvent syntax itself without schema changes, with typed Groups? Can you provide an example event using your proposed new schema?</span><br><span>Thank you</span><br><span>Roy Williams</span><br><span></span><br><span>---</span><br><span>Royal Observatory Edinburgh</span><br><span><a href="mailto:roy@roe.ac.uk">roy@roe.ac.uk</a></span><br><span>07542 869986</span><br><span>________________________________</span><br><span>From: <a href="mailto:voevent-bounces@ivoa.net">voevent-bounces@ivoa.net</a> [<a href="mailto:voevent-bounces@ivoa.net">voevent-bounces@ivoa.net</a>] on behalf of Baptiste Cecconi [<a href="mailto:baptiste.cecconi@obspm.fr">baptiste.cecconi@obspm.fr</a>]</span><br><span>Sent: 02 November 2017 3:20 PM</span><br><span>To: <a href="mailto:voevent@ivoa.net">voevent@ivoa.net</a></span><br><span>Subject: Draft VOEvent 2.1</span><br><span></span><br><span>Dear colleagues,</span><br><span></span><br><span>during the discussions at IVOA last week, Pierre Le Sidaner and I have mentioned our need for updates in the VOEvent 2.0 schema, in order to fit our needs in Solar and Planetary sciences. We have prepared a draft VOEvent 2.1, trying to make sure it stays fully compliant with VOEvent built with version 2.0 of the schema. We would be grateful to have your view on this proposed draft version. The main changes are recalled below (but are available as comments in the XML schema file):</span><br><span></span><br><span>Revision 2.1 2017/11/02 BaptisteCecconi</span><br><span>- added "AuthorURI" in "Who"</span><br><span>- removed restricted list of "AstroCoordSystem": previously "idValues" type, now "xs:string"</span><br><span>- removed "idValues" type (and references)</span><br><span>- added annotation in "AstroCoords/Time" (according to STC-1.30)</span><br><span>- added "AstroCoords/PositionName" as "xs:string"</span><br><span>- added annotation to "AstroCoords/Position2D" (according to STC-1.30)</span><br><span>- removed restricted list of attribute "coord_system_id" in "AstroCoords": previous type=idValues (removed), new type=xs:string</span><br><span>- added "TimeInterval" of type "TimeInterval" in "Time"</span><br><span>- added "TimeOrigin" of type "xs:string" in "TimeInstant"</span><br><span>- added "TimeInterval" type with "StartTime" and "StopTime" elements</span><br><span>- changed minOccurs attribute in "Position2D/Error2Radius": now set to 0</span><br><span>- added "Error2" element in "Position2D" with type "error2" and minOccurs=0</span><br><span>- added "Error3" element in "Position3D" with type "error3" and minOccurs=0</span><br><span>- added "coord_value" type introducing "ucd" and "unit" attributes for C1, C2 and C3 elements</span><br><span>- added "error2" type, with "C1" and "C2" elements</span><br><span>- added "error3" type, with "C1", "C2" and "C3" elements</span><br><span>- added "TimeFrameType" (taken from to STC-1.30)</span><br><span>- added "SpaceFrameType" (taken from to STC-1.30)</span><br><span></span><br><span>The presentations of Pierre Le Sidaner at the last 2 interop meetings contain the rationale for the changes, but we can prepare a more detailed document, if we decide to proceed.</span><br><span></span><br><span>Sincerely</span><br><span>Baptiste Cecconi</span><br><span></span><br></div></blockquote></body></html>