The l3v2 spec has this bit about min and max:
"However, while min and max are also defined as N-ary operators, MathML does not define their meaning when used with no arguments. This SBML specification also does not define the meaning of min and max with zero arguments, though a Level 3 package may add a definition. Apart from this, this usage is discouraged."
The intent of the last sentence was to indicate that people shouldn't use min or max with no arguments. However, Herbert read the sentence as indicating that min and max shouldn't be used at all! This should be clarified.
Fixed in SVN with http://sourceforge.net/p/sbml/code/25695. However, the SBML editors still need to chime in and say they approve of this change. The new text is the 'changed' bit of:
\vertwo{However, while \token{min} and \token{max} are also defined as N-ary operators, MathML does not define their meaning when used with no arguments. This SBML specification also does not define the meaning of \token{min} and \token{max} with zero arguments, though a Level~3 package may add a definition. \changed{In the absence of such a package, the use of \token{min} or \token{max} with zero arguments} is discouraged.}
I agree.
I agree
I agree
Accepted and will be part of the forthcoming release, and added to http://sbml.org/Documents/Specifications/SBML_Level_3/Version_2/Core/Confirmed_issues_in_the_Level_3_Version_2_Core_Specification .
I agree.
Released.