[SCHEDULER-395]  VOEvent Followup Alert XML error
Type Bug
Priority Medium
Severity Major
Component VOEvent Alerter
Fixed In Version [3.33.3
Versions Affected [3.23.2
Severity Closed
Resolution Complete
Reported By Bob Denny
Resources Bob Denny
Start Date 2/11/2011

Description
The VOEvent messages produced by the Alerter have a bug in the XML. In <ObservationLocation><AstroCoordSystem> the attribute is idref and should be id. Strictly speaking it should be of the form:

<ObservationLocation>
<AstroCoordSystem id="UTC-FK5-TOPO" xlink:type="simple" xlink:href="ivo://STClib/CoordSys#UTC-FK5-TOPO/" />
<AstroCoords coord_system_id="UTC-FK5-TOPO">



Comments
2/11/2011 5:12:38 PM   Bob Denny
SVN Comment
Author rbdenny
Repository svn+ssh://rbdenny@a2_svn_dc3/home/rbdenny/svn/astro/scheduler
SVN Revision 170
Affected files /trunk/Help/RelNotes.htm (Modified)
Check-in comment Oops, forgot release notes. GEM:395
2/11/2011 5:04:52 PM   Bob Denny
SVN Comment
Author rbdenny
Repository svn+ssh://rbdenny@a2_svn_dc3/home/rbdenny/svn/astro/scheduler
SVN Revision 169
Affected files /trunk/VOEventParser/SimpleVOEvent.cs (Modified)
/trunk/VOSimpleGenTest/SimpleVOGenTest.cs (Modified)
Check-in comment Fix VOEvent alerter message format. GEM:395
2/11/2011 1:49:15 PM   Bob Denny
Problem traced to a hack in SimpleVOEvent. It dates way back and probably was a workaround for a problem in the old Liquid 7. It's gone, and now the element builds just right, complete with the xlink:href for the coordinate system type.
2/11/2011 9:49:18 AM   Bob Denny
This is going to include upgrading to the latest Liquid, and rebuilding everything, so if I need to alter the schema or something I can without pain. It needs to be on the latest Liquid anyway.