Menu
▾
▴
#338 Fix 'an event assignment' to 'a set of event assignments'
closed
nobody
5
2017-12-06
2016-09-12
No
As pointed out by Stefan, the L3v1 spec states incorrectly:
"A software package should retest all event triggers after executing
an event assignment in order to account for the possibility that the
assignment causes another event trigger to transition from “false” to
“true”."
This is incorrect: it should state that the retesting should happen after all event assignments from a single event.
This change has been made (thanks Mike!) and now reads 'the assignments from a given event' instead of 'an event assignment'. I've also added it to http://sbml.org/Documents/Specifications/SBML_Level_3/Version_1/Core/Confirmed_issues_in_the_Level_3_Version_1_Core_Specification
I'm not sure that this change counts as a typo or not (and therefore whether it means the editors should vote on it), and in any event, there may be other proposed change that come from the discussion with Stefan; we shall see. Further updates at COMBINE.
COMBINE update: if the editors could read through the event semantics section with an eye towards anything that might be confusing in terms of simultenaity, please point out any such sections you find and any suggestions you might have. If you think it's OK, do still vote to approve or disapprove of the above change. Thanks!
Last edit: Lucian Smith 2016-09-22
Thanks to Stefan for pointing this out and to Lucian and Mike for making this change. IMHO, the new text describes the procedure now better.
works for me
Hearing no further objections (and no further suggestions for other places to clarify the issue), I'm now marking this issue as pending. These changes already appeared in RC1 of both l3v1r2 and l3v2, and were also added to http://sbml.org/Documents/Specifications/SBML_Level_3/Version_1/Core/Confirmed_issues_in_the_Level_3_Version_1_Core_Specification
With the release of L3v2, this issue is now resolved.