CellML 2.0 Conformance Report

<model name="x1">. Valid: a Basic Latin letter followed by a digit (rule 1.3.1.1). This is the control file for this place: every other file for it differs in this one value.

<model name="">. Invalid: an identifier has at least one character, a Basic Latin letter (rule 1.3.1.1), and an empty name has none.

<model name="x-y">. Invalid: after the first letter, rule 1.3.1.1 allows only Basic Latin letters, digits and underscores, and this name has a hyphen-minus.

<model name="1x">. Invalid: an identifier must begin with a Basic Latin letter (rule 1.3.1.1), and this name begins with a digit.

<model name="_x">. Invalid: an identifier must begin with a Basic Latin letter (rule 1.3.1.1), and this name begins with an underscore.

<model name="xé">. Invalid: after the first letter, rule 1.3.1.1 allows only Basic Latin letters, digits and underscores, and this name has the letter é (e with an acute accent), which is not Basic Latin.

<model name="x">. Valid: one Basic Latin letter is a whole identifier (rule 1.3.1.1).

<model name="x y">. Invalid: after the first letter, rule 1.3.1.1 allows only Basic Latin letters, digits and underscores, and this name has a space.

<model name="x_1">. Valid: after the first letter, underscores are allowed (rule 1.3.1.1).

<model name="X1">. Valid: a Basic Latin letter may be upper or lower case (rule 1.3.1.1).

<units name="x1">. Valid: a Basic Latin letter followed by a digit (rule 1.3.1.1). This is the control file for this place: every other file for it differs in this one value.

<units name="">. Invalid: an identifier has at least one character, a Basic Latin letter (rule 1.3.1.1), and an empty name has none.

<units name="x-y">. Invalid: after the first letter, rule 1.3.1.1 allows only Basic Latin letters, digits and underscores, and this name has a hyphen-minus.

<units name="1x">. Invalid: an identifier must begin with a Basic Latin letter (rule 1.3.1.1), and this name begins with a digit.

<units name="_x">. Invalid: an identifier must begin with a Basic Latin letter (rule 1.3.1.1), and this name begins with an underscore.

<units name="xé">. Invalid: after the first letter, rule 1.3.1.1 allows only Basic Latin letters, digits and underscores, and this name has the letter é (e with an acute accent), which is not Basic Latin.

<units name="x">. Valid: one Basic Latin letter is a whole identifier (rule 1.3.1.1).

<units name="x y">. Invalid: after the first letter, rule 1.3.1.1 allows only Basic Latin letters, digits and underscores, and this name has a space.

<units name="x_1">. Valid: after the first letter, underscores are allowed (rule 1.3.1.1).

<units name="X1">. Valid: a Basic Latin letter may be upper or lower case (rule 1.3.1.1).

prefix="3". Valid: an integer string (rule 1.3.2), so the prefix term is 3 (rule 3.3.1.1.2). This is the control file for this place: every other file for it differs in this one value.

prefix="3.0". Invalid: it has a decimal point, so it is not an integer string (rule 1.3.2), and it is not a name in Table 3.2 either (rule 3.3.1.1.3).

prefix="1e3". Invalid: it has an exponent, so it is not an integer string (rule 1.3.2), and it is not a name in Table 3.2 either (rule 3.3.1.1.3).

prefix="". Invalid: an empty value has no digits (rule 1.3.2.3), so it is not an integer string (rule 1.3.2), and it is not a name in Table 3.2 either (rule 3.3.1.1.3).

prefix="400". Valid: an integer string, and the specification sets no range for the prefix term (rule 3.3.1.1.2).

prefix="+3". Valid: rule 1.3.2.2 lets an integer string begin with a single + sign.

prefix="Kilo". Invalid: Table 3.2 lists kilo in lower case, and a value that is not an integer string must be taken from its Name column as written (rule 3.3.1.1.3).

prefix="deca". Valid: deca is in the Name column of Table 3.2, with the value 1 (rule 3.3.1.1.3).

prefix="deka". Invalid: Table 3.2 spells this prefix deca, and a value that is not an integer string must be taken from its Name column (rule 3.3.1.1.3).

prefix="milli". Valid: milli is in the Name column of Table 3.2, with the value -3 (rule 3.3.1.1.3).

prefix="-3". Valid: rule 1.3.2.2 lets an integer string begin with a single hyphen-minus sign, so the prefix term is -3, the same as milli.

prefix="-". Invalid: it has a sign and no digits (rule 1.3.2.3), so it is not an integer string (rule 1.3.2), and it is not a name in Table 3.2 either (rule 3.3.1.1.3).

multiplier="2". Valid: a plain real number string. This is the control file for this place: every other file for it differs in this one value.

multiplier="1e999". Valid: rules 1.3.3 and 1.3.4 allow this syntax and the specification sets no range. 10 to the power 999 has no IEEE 754 double value, and the specification's maintainers confirmed in spec issue 366 that a number a computer cannot represent is still valid CellML: https://github.com/cellml/cellml-specification/issues/366

multiplier="". Invalid: an empty value has no digits at all, so it is not a real number string (rule 1.3.3.4).

multiplier="+2". Valid: rule 1.3.3.2 lets a basic real number string begin with a single + sign.

multiplier=".". Invalid: rule 1.3.3.4 requires one or more digits besides the sign and the decimal point, and this value has only a decimal point.

multiplier="-.". Invalid: rule 1.3.3.4 requires one or more digits besides the sign and the decimal point, and this value has only a sign and a decimal point.

multiplier="-". Invalid: rule 1.3.3.4 requires one or more digits besides the sign and the decimal point, and this value has only a sign.

exponent="2". Valid: a plain real number string. This is the control file for this place: every other file for it differs in this one value.

exponent="1e999". Valid: rules 1.3.3 and 1.3.4 allow this syntax and the specification sets no range. 10 to the power 999 has no IEEE 754 double value, and the specification's maintainers confirmed in spec issue 366 that a number a computer cannot represent is still valid CellML: https://github.com/cellml/cellml-specification/issues/366

exponent="". Invalid: an empty value has no digits at all, so it is not a real number string (rule 1.3.3.4).

exponent="+2". Valid: rule 1.3.3.2 lets a basic real number string begin with a single + sign.

exponent=".". Invalid: rule 1.3.3.4 requires one or more digits besides the sign and the decimal point, and this value has only a decimal point.

exponent="-.". Invalid: rule 1.3.3.4 requires one or more digits besides the sign and the decimal point, and this value has only a sign and a decimal point.

exponent="-". Invalid: rule 1.3.3.4 requires one or more digits besides the sign and the decimal point, and this value has only a sign.

<component name="x1">. Valid: a Basic Latin letter followed by a digit (rule 1.3.1.1). This is the control file for this place: every other file for it differs in this one value.

<component name="">. Invalid: an identifier has at least one character, a Basic Latin letter (rule 1.3.1.1), and an empty name has none.

<component name="x-y">. Invalid: after the first letter, rule 1.3.1.1 allows only Basic Latin letters, digits and underscores, and this name has a hyphen-minus.

<component name="1x">. Invalid: an identifier must begin with a Basic Latin letter (rule 1.3.1.1), and this name begins with a digit.

<component name="_x">. Invalid: an identifier must begin with a Basic Latin letter (rule 1.3.1.1), and this name begins with an underscore.

<component name="xé">. Invalid: after the first letter, rule 1.3.1.1 allows only Basic Latin letters, digits and underscores, and this name has the letter é (e with an acute accent), which is not Basic Latin.

<component name="x">. Valid: one Basic Latin letter is a whole identifier (rule 1.3.1.1).

<component name="x y">. Invalid: after the first letter, rule 1.3.1.1 allows only Basic Latin letters, digits and underscores, and this name has a space.

<component name="x_1">. Valid: after the first letter, underscores are allowed (rule 1.3.1.1).

<component name="X1">. Valid: a Basic Latin letter may be upper or lower case (rule 1.3.1.1).

<variable name="x1">. Valid: a Basic Latin letter followed by a digit (rule 1.3.1.1). This is the control file for this place: every other file for it differs in this one value.

<variable name="">. Invalid: an identifier has at least one character, a Basic Latin letter (rule 1.3.1.1), and an empty name has none.

<variable name="x-y">. Invalid: after the first letter, rule 1.3.1.1 allows only Basic Latin letters, digits and underscores, and this name has a hyphen-minus.

<variable name="1x">. Invalid: an identifier must begin with a Basic Latin letter (rule 1.3.1.1), and this name begins with a digit.

<variable name="_x">. Invalid: an identifier must begin with a Basic Latin letter (rule 1.3.1.1), and this name begins with an underscore.

<variable name="xé">. Invalid: after the first letter, rule 1.3.1.1 allows only Basic Latin letters, digits and underscores, and this name has the letter é (e with an acute accent), which is not Basic Latin.

<variable name="x">. Valid: one Basic Latin letter is a whole identifier (rule 1.3.1.1).

<variable name="x y">. Invalid: after the first letter, rule 1.3.1.1 allows only Basic Latin letters, digits and underscores, and this name has a space.

<variable name="x_1">. Valid: after the first letter, underscores are allowed (rule 1.3.1.1).

<variable name="X1">. Valid: a Basic Latin letter may be upper or lower case (rule 1.3.1.1).

initial_value="2". Valid: a plain real number string. This is the control file for this place: every other file for it differs in this one value.

initial_value="1e999". Valid: rules 1.3.3 and 1.3.4 allow this syntax and the specification sets no range. 10 to the power 999 has no IEEE 754 double value, and the specification's maintainers confirmed in spec issue 366 that a number a computer cannot represent is still valid CellML: https://github.com/cellml/cellml-specification/issues/366

initial_value="". Invalid: an empty value has no digits at all, so it is not a real number string (rule 1.3.3.4). It is not a variable reference either (rule 3.6.2).

initial_value="+2". Valid: rule 1.3.3.2 lets a basic real number string begin with a single + sign.

initial_value=".". Invalid: rule 1.3.3.4 requires one or more digits besides the sign and the decimal point, and this value has only a decimal point. It is not a variable reference either (rule 3.6.2).

initial_value="-.". Invalid: rule 1.3.3.4 requires one or more digits besides the sign and the decimal point, and this value has only a sign and a decimal point. It is not a variable reference either (rule 3.6.2).

initial_value="-". Invalid: rule 1.3.3.4 requires one or more digits besides the sign and the decimal point, and this value has only a sign. It is not a variable reference either (rule 3.6.2).

<cn>2</cn>. Valid: a plain real number string. This is the control file for this place: every other file for it differs in this one value.

<cn>1e999</cn>. Valid: rules 1.3.3 and 1.3.4 allow this syntax and the specification sets no range. 10 to the power 999 has no IEEE 754 double value, and the specification's maintainers confirmed in spec issue 366 that a number a computer cannot represent is still valid CellML: https://github.com/cellml/cellml-specification/issues/366

<cn></cn>. Invalid: an empty value has no digits at all, so it is not a real number string (rule 1.3.3.4).

<cn>+2</cn>. Valid: rule 1.3.3.2 lets a basic real number string begin with a single + sign.

<cn>.</cn>. Invalid: rule 1.3.3.4 requires one or more digits besides the sign and the decimal point, and this value has only a decimal point.

<cn>-.</cn>. Invalid: rule 1.3.3.4 requires one or more digits besides the sign and the decimal point, and this value has only a sign and a decimal point.

<cn>-</cn>. Invalid: rule 1.3.3.4 requires one or more digits besides the sign and the decimal point, and this value has only a sign.

<cn base="10">2</cn>. Valid: base 10, written out. This is the control file for this place: every other file for it differs in this one value.

<cn base="16">2</cn>. Invalid: rule 2.12.5 requires base 10, and this cn is base 16, even though 2 is a digit in both.

<cn base="8">2</cn>. Invalid: rule 2.12.5 requires base 10, and this cn is base 8, even though 2 is a digit in both.

<degree><cn>2</cn></degree>. Valid: a plain real number string. This is the control file for this place: every other file for it differs in this one value.

<degree><cn>1e999</cn></degree>. Valid: rules 1.3.3 and 1.3.4 allow this syntax and the specification sets no range. 10 to the power 999 has no IEEE 754 double value, and the specification's maintainers confirmed in spec issue 366 that a number a computer cannot represent is still valid CellML: https://github.com/cellml/cellml-specification/issues/366

<degree><cn></cn></degree>. Invalid: an empty value has no digits at all, so it is not a real number string (rule 1.3.3.4).

<degree><cn>+2</cn></degree>. Valid: rule 1.3.3.2 lets a basic real number string begin with a single + sign.

<degree><cn>.</cn></degree>. Invalid: rule 1.3.3.4 requires one or more digits besides the sign and the decimal point, and this value has only a decimal point.

<degree><cn>-.</cn></degree>. Invalid: rule 1.3.3.4 requires one or more digits besides the sign and the decimal point, and this value has only a sign and a decimal point.

<degree><cn>-</cn></degree>. Invalid: rule 1.3.3.4 requires one or more digits besides the sign and the decimal point, and this value has only a sign.

<cn type="e-notation">2<sep/>3</cn>. Valid: 2 times 10 to the power 3. This is the control file for the exponent: every other file for it differs in the exponent only.

<cn type="e-notation">2<sep/>3.5</cn>. Invalid: the exponent of e-notation is an integer (MathML 2.0, 4.4.1.1), and 3.5 has a decimal point.

<cn type="e-notation">2<sep/></cn>. Invalid: the exponent of e-notation is an integer (MathML 2.0, 4.4.1.1), and an empty exponent has no digits.

<cn type="e-notation">2<sep/>+3</cn>. Valid: the exponent is an integer, which may begin with a single + sign (MathML 2.0; rule 1.3.2.2). The informative specification allows this sign too.

<cn type="e-notation">2<sep/>-3</cn>. Valid: the exponent is an integer, which may begin with a single hyphen-minus sign (MathML 2.0; rule 1.3.2.2).

<cn type="e-notation">2<sep/>3</cn>. Valid: 2 times 10 to the power 3. This is the control file for the significand: every other file for it differs in the significand only.

<cn type="e-notation">2.5<sep/>3</cn>. Valid: the significand is a real in decimal notation, which may have a decimal point (MathML 2.0, 4.4.1.1).

<cn type="e-notation"><sep/>3</cn>. Invalid: the significand is a real in decimal notation (MathML 2.0, 4.4.1.1), and an empty significand has no digits.

<cn type="e-notation">+2<sep/>3</cn>. Valid: the significand is a real in decimal notation, which may begin with a + sign (MathML 2.0, 4.4.1.1).

<cn type="e-notation">-2<sep/>3</cn>. Valid: the significand is a real in decimal notation, which may begin with a hyphen-minus sign (MathML 2.0, 4.4.1.1).

<cn type="e-notation">2e1<sep/>3</cn>. Invalid: the significand is a real in decimal notation (MathML 2.0, 4.4.1.1), so it cannot carry an exponent of its own; the exponent goes after the sep.

<cn type="real">2</cn>. Valid: real is one of the two allowed types, written out. This is the control file for this place: every other file for it differs in this one value.

<cn type="Real">2</cn>. Invalid: rule 2.12.5.1 allows only the types real and e-notation, and the type is written real, in lower case.

<cn type="double">2</cn>. Invalid: rule 2.12.5.1 allows only the types real and e-notation, and double is a MathML 3 type, not one of them.

<cn type="e-notation">2</cn>. Invalid: e-notation is an allowed type, but MathML 2.0 (section 4.4.1.1) writes it as a significand and an exponent on either side of a sep element, and this cn has no sep (rule 2.12.1).

<cn type="">2</cn>. Invalid: rule 2.12.5.1 allows only the types real and e-notation, and an empty type is neither.

<cn type="integer">2</cn>. Invalid: rule 2.12.5.1 allows only the types real and e-notation, and integer is a MathML type CellML 2.0 leaves out.