Skip to content

Commit f0dcdf9

Browse files
committed
Adjust wording for FMI 3.0
As noted by @UKiffmeier
1 parent 1f0a539 commit f0dcdf9

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/5___ssd.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -95,8 +95,8 @@ For components the set of connectors *MUST* match variables/ports of the underly
9595
For FMI 3.0 FMUs, the connector name has to match either the name of the corresponding variable element, or one of its <Alias> elements.
9696

9797
Names of variable elements of an FMU might follow the “Variable Naming Conventions” specification as defined by the FMI standard.
98-
Hence, several ScalarVariables might be grouped as a structure or an array.
99-
However, the name of a connector *MUST* match the name of a single <ScalarVariable>.
98+
Hence, several variables might be grouped as a structure or an array.
99+
However, the name of a connector *MUST* match the name of a single variable.
100100

101101
Note that there is no requirement that connectors have to be present for all variables/ports of an underlying component implementation.
102102
At least those connectors *MUST* be present which are referenced in connections inside the SSD.
@@ -410,7 +410,7 @@ For structural parameters it is assumed that the parameterization is applied in
410410
This means that variables eligible for parameterization are those with:
411411

412412
* either causality = "input" or a start value for FMI 1.0
413-
* variability != "constant" and initial = "exact" or "approx" for FMI 2.0
413+
* variability != "constant" and initial = "exact" or "approx" for FMI 2.0/3.0
414414

415415
All kinds of system connectors can be parameterized.
416416
In case the system level connectors are connected to FMU components, the parameterization *MUST* be compatible with the variable in the connected FMU.

0 commit comments

Comments
 (0)