Collected Errata to the SBML Level 2 Version 4 Specification
19 April 2010.
Release 1 of the SBML Level 2 Version 4 specification was made available on 22 December 2008. The following are the errors and other issues discovered in the Release 1 specification after it was issued. In the following table, the ID # of each issue refers to the reference number automatically assigned to the issue in the online SBML issue tracking system. The gaps in this numbering are not consequential for SBML and do not necessarily signify deleted or unresolved issues.
| ID# | Description | Page(s) and line number(s) | Date added |
|---|---|---|---|
| 2586155 | Reversed statements. The sentence describes the namespaces for model qualifiers and biological qualifiers, but plainly reverses the URIs and prefixes. | p. 95 lines 16–17 | 11 May '09 |
| 2789288 | The end of section 4.7.4 gives an explanation of whether the identifiers of 0-dimensional compartment can appear in mathematical expressions. The statement is that it "should" not appear in expressions. The word "should" should actually be "must": identifiers of 0-D compartments must not appear in mathematical expressions. | p. 46 line 24 | 11 May '09 |
| 2789287 | The value of 0-dimensional compartments cannot be changed (because they have no size), but the specification lacks explicit statements to this effect in Section 4.11 and in the list of validation rules in Appendix C. Such statements need to be added to the specification. | Section 4.11 and Appendix C | 11 May '09 |
| 2770254 | The paragraph on p. 71, lines 19–27, should not be there at all. It is a left-over from the Version 3 specification that should have been removed for Version 4. The paragraph should be ignored and deleted in future Releases of the L2V4 specification. | p. 71 lines 19–27 | 16 May '09 |
| 2803292 | The UML box for Event in Figure 22 does not define a data type for the attribute useValuesFromTriggerTime. It should say the type is boolean. The text makes this clear, but the UML is missing information.
| p. 78 Fig. 22 | 30 Jun. '09 |
| 2738202 | The example models provided in Sections 7.4 and 7.5 involve irreversible reactions, but the SBML code lacks the attribute setting reversible="false" on the <reaction> elements. Each <reaction> should have the attribute reversible="false".
| p. 109 lines 46 and 67, p. 111 lines 26 and 47 | 30 Jun. '09 |
| 2687674 | Throughout the specification, sometimes SBase is spelled SBase and sometimes it is spelled Sbase. The inconsistency is simply a typographical error perpetuated via a LaTeX macro used in the document. The preferred spelling is SBase. This is also the spelling used in the XML Schema for SBML. | p. 14 Fig. 8, and throughout the text (too many instances to list individually) | 30 Jun. '09 |
| 2790011 | The links to MIRIAM Resources are out of date. The obsolete links are those of the form http://www.ebi.ac.uk/compneur-srv/miriam-main/. To future-proof what is printed in the SBML specifications, SBML.org now maintains a perennial URL http://sbml.org/miriam that will always point to the correct URL even if the future MIRIAM Resources link changes.
| p. 94 line 39, p. 95 line 7 | 11 Jul. '09 |
| 2790007 | The links to the descriptions of the MIRIAM qualifiers are out of date. The obsolete links are of the form http://www.ebi.ac.uk/compneur-srv/miriam-main/mdb?section=qualifiers. To future-proof what is printed in the SBML specifications, SBML.org now maintains a perennial URL, http://sbml.org/miriam/qualifiers, that will always point to the correct URL even if the future MIRIAM Resources link changes.
| p. 92 line 24, p. 95 line 15 | 11 Jul. '09 |
| 2848164 | The 2nd and 3rd bullets in the bulleted list state that the units must agree, but in fact the rule for units in L2v4 is that they should agree. The word must must be changed to should. | p. 46 lines 13–18 | 9 Feb. '10 |
| 2811758 | In Section 6.3, the given RDF template contains a number of xmlns namespace declarations. What is not made clear is (1) a model doesn't need to list all of them every time, only those it actually uses, and (2) the namespace declarations can appear in any order, not only the one shown in the template.
| p. 93 lines 3–30 | 9 Feb. '10 |
| 2848167 | In Figure 5, the symbol NCNameChar should actually be NameChar, per the XML 1.0 third edition. There is no other change in the definition or implications; the wrong name appears here, but the correct definition for NameChar is given.
| p. 12 lines 30–31 | 9 Feb. '10 |
| 2832364 | A closing parenthesis is missing for the parenthetical statement. The closing parenthesis should come after the word "resources". | p. 18 line 39 | 10 Feb. '10 |
| 2964795 | The specification fails to stipulate whether the delay csymbol can be used within a FunctionDefinition object, yet it explicitly disallows time. In the interest of consistency and simplicity, the csymbol for delay is also disallowed.
| p. 34 line 14 | 19 Apr. '10 |