Francesco Casella

> Sidenote, risking off-topic: More annotations could be specified, but then I would broaden the scope: What could model developers want to tell people using their model, if it fails?...

> what you are suggesting is something that could be prepared as an open MA library with a value on its own – a _ModelicaFailures_ library that would complement ModelicaCompliance....

No deep reason, just lack of input from the end users :) What are exactly your requirements? Same as #3883?

See my [comment](https://github.com/modelica/ModelicaStandardLibrary/issues/3883#issuecomment-954006558) there

In fact, I now realize that the algorithm section with elsewhen and with when won't be exactly the same. Assuming both events are triggered simultaneously, the former only executes the...

> There is no indication that choicesAllMatching can be used for modifications that are not redeclarations of replaceable components or how the offered choices should be interpreted. That is exactly...

> > Note that `v` is used in the text, even though it is not part of the calling syntax. > > Yes, I noted that, but didn't find it...

> **Question:** What is the rationale behind requiring the `positiveVelocity` to be provided separately; why can't the function just look at the change in `x`? Because that would go against...

@AnHeuermann, you recently implemented the `spatialDistribution()` operator in OpenModelica, maybe you want to comment on that as well.

@eshmoylova you are absolutely right, that is of course a mistake, we should have either x or y throughout the text. In fact, this issue has been dangling there for...