Per Östlund

This broke some of the models since they use models from `Modelica.Media.Examples` which are not covered by the conversion script (I guess they're not really meant to be used by...

Seems ok to me too. We haven't implemented it in OpenModelica yet, but it looks fairly straight-forward and I don't really see any issues.

6.7 does not allow or disallow any operations on type compatible subexpressions, it only defines what type compatible means and gives some examples of contexts where expressions are required to...

All of the examples are rejected by OpenModelica too. Most of them fail because they use a component of type `SourcesOrSinks.Growth`, which is illegal since `SourcesOfSinks` is a partial package....

Why is there even specific grammar for some of the annotations in the specification, while others are defined as records? The actual grammar of Modelica for annotations is `annotation class-modification`,...

> The text supporting that is "In case of nested modifiers this implies it is applied individually to each element of each element of the enclosing array; see example" and...

It seems like the intent is that only components and connections are allowed to be deselected, but I'm not really seeing any rule that forbid other elements (like classes) from...

The next rule in 12.6 says: >Prefixes (constant, parameter, final, discrete, …) of the remaining record components are removed. Does this mean that there are actually cases where `final` components...

> > Given what I can find it seems like the only components that do not allow a modification in a record would be final or protected components, regardless of...

> > Both Dymola and OpenModelica seems to think that constants with bindings are not allowed to be modified either though, but I can't find any rules in the specification...